Atlas / MCP servers / lsd-so / LSD

LSDCAUTION

mcp/lsd-so/lsd

LSD Model Context Protocol

Verdict
CAUTION
Grade
B
Trust score
82 /100
Exposed tools
4 3r · 1w · 0d
Transport
—
License
—
Stars
66
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

Immediately gather an aggregation of high quality info directly from a website just by giving LSD the link via Claude MCP.

You will see Claude connect to the internet and:

  • Write LSD SQL
  • Self-correct LSD SQL
  • Run LSD SQL that's connected to cloud browsers

Demo

Here's a demo of what that looks like in action:

We treated Claude to psychedelic therapy on LSD and now it can just do things. Here's a longer video on YouTube

Contents

  • Quickstart
  • Dependencies
  • Giving Claude LSD
  • Claude on LSD
  • Failed to start MCP server
  • First time running an MCP server
  • Missing executable
  • Incomplete path
  • What is MCP?
  • What is LSD?
  • Contact
  • Smithery
  • Installing via Smithery

Quickstart

Dependencies

To run the MCP server, you'll need both Python and uv installed. To use the MCP server, you'll need to download either the Claude desktop app or another MCP client.

To use LSD, you'll need to sign up and create an API key so your queries are privately associated to only your account. You can do so for free with a Google account.

Giving Claude LSD

  1. Clone this repository onto your computer
$ git clone https://github.com/lsd-so/lsd-mcp.git
$ cd lsd-mcp
  1. Update the values in the .env file with LSD_USER containing the email you have an account on LSD with and LSD_API_KEY containing the API key you obtained from the p
Read from source at commit 1ac55f08f1d3OBSERVED · 2026-10-07
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.

claude-code
claude mcp add lsd-mcp --env LSD_API_KEY=${LSD_API_KEY} -- uvx lsd-mcp
claude-desktop
{
  "mcpServers": {
    "lsd-mcp": {
      "command": "uvx",
      "args": [
        "lsd-mcp"
      ],
      "env": {
        "LSD_API_KEY": "${LSD_API_KEY}"
      }
    }
  }
}
03

Exposed tools (4)

3 read · 1 write · 0 destructive.

ToolRiskDescription
run_lsdwriteRuns LSD SQL using user credentials in .env
search_tripsreadReturns a list of objects with LSD trips available to the user and what each of them do.
use_tripreadInvokes a trip on LSD based on its identifier using the [ACCORDING TO] keywords.
view_lsdread
04

Trust audit

CAUTIONgrade B · trust 82/100 Install with care. The audit found things worth knowing before you trust its output.

LayerWhat it checksResult
L0Provenance & inventoryFAIL
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
found

Findings (8)

HIGHHard-coded secrets · inv.env_committed · CWE-798, CWE-321
.env
.env
Why it matters. a real .env in the package
Fix. ship .env.example with placeholders only
LOWInventory / provenance · inv.hidden_file · CWE-1104
.env
.env
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWInventory / provenance · inv.no_license · CWE-1104
Why it matters. no LICENSE file and no repo licence
Fix. add a licence
INFOInventory / provenance · inv.oversize · CWE-1104
media/5x speed.gif
media/5x speed.gif
Why it matters. 14108408 bytes not read
INFOInventory / provenance · inv.oversize · CWE-1104
media/5x speed.mov
media/5x speed.mov
Why it matters. 11057308 bytes not read
INFOInventory / provenance · inv.oversize · CWE-1104
media/5x_speed.gif
media/5x_speed.gif
Why it matters. 14108408 bytes not read
INFOInventory / provenance · inv.oversize · CWE-1104
media/github_trending.gif
media/github_trending.gif
Why it matters. 51601444 bytes not read
INFOInventory / provenance · inv.oversize · CWE-1104
media/prompt.gif
media/prompt.gif
Why it matters. 18816062 bytes not read

Gates applied: no_behavioural_pass, no_license.

Audited 2026-10-07 · audit v0.4.1 · source sha 1ac55f08f1d3full audit observations/trust-audit/mcp-server/lsd-so__lsd.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-071ac55f08f1d3CAUTIONB82first audit
06

Questions

What is the LSD MCP server?

LSD Model Context Protocol

What tools does LSD expose?

4 in total: 3 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is LSD safe to connect to an agent?

With care. The audit graded it B (82/100) and found 8 things worth knowing before you trust this server, listed below with the exact line each was found on.

What credentials does LSD need?

It reads LSD_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.

How current is this page?

The grade is for one exact copy of the source (1ac55f08f1d3), read on 2026-10-07. The repository is watched and re-audited when it changes.

Advertisement