LspSAFE
An Model Context Protocol (MCP) server that provides LLMs/AI Agents with the capabilities of a language server protocol (LSP) server. This gives the AI the ability to get language aware context from the codebase.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
An Model Context Protocol (MCP) server that provides LLMs/AI Agents with the capabilities of a language server protocol (LSP) server. This gives the AI the ability to get language aware context from the codebase.
- LSP MCP
- Example
- Warning
- Features
- Quick Start
- Claude Desktop
- Using Docker (Recommended)
- Using npx
- Cursor
- MCP CLI Client
- The ABCs (Introduction)
- What is an MCP?
- What is an LSP?
- Development
- Dependencies
- Decisions
- Roadmap
- References
Example
Input:
Use lsp to give me insights into the following typescript code:
let foo = "bar";
function x() {
let foo = 123;
console.log(foo);
}
x();
console.log(foo);Output:
I'll use LSP (Language Server Protocol) to analyze your TypeScript code. Let me break down what's happening: Here's what the code does and the insights from LSP analysis: 1. Variable Shadowing: There are two variables named foo: A global foo (string type) initialized with the value "bar" A local foo (number type) inside the function x() initialized with the value 123 2. Execution Flow: First, the global foo is declared and assigned the value "bar" When function x() is called, the local foo variable is declared and assigned 123 The console.log(foo) inside the function outputs 123 (the local variable) After the function finishes, console.log(foo) outputs "bar" (the global variable) 3. Scope Isolation: The LSP confirms that TypeScript correctly identifies the different types: The global foo is a string type The local foo inside the function is a number type Changes to the local foo don't affect the global foo This is a classic ex
e16698f7da25OBSERVED · 2026-10-06Connect
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.
claude mcp add lsp-mcp -- npx -y [email protected]
{
"mcpServers": {
"lsp-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (1)
0 read · 1 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
lsp | write | The LSP to use to execute this method. Options are: |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (2)
"llm": "uvx --python 3.12 --from git+https://github.com/adhikasp/mcp-client-cli.git llm --text-only"
@apidevtools/json-schema-ref-parser, @modelcontextprotocol/sdk, commander, strip-json-comments, vscode-languageserver-protocol, zod, @types/node, @typescript-eslint/eslint-plugin
Gates applied: no_behavioural_pass.
e16698f7da25full audit observations/trust-audit/mcp-server/jonrad__lsp-1.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-06 | e16698f7da25 | SAFE | B | 89 | first audit |
Questions
What is the Lsp MCP server?
An Model Context Protocol (MCP) server that provides LLMs/AI Agents with the capabilities of a language server protocol (LSP) server. This gives the AI the ability to get language aware context from the codebase.
What tools does Lsp expose?
1 in total: 0 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Lsp safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Lsp need?
No credential environment variables were found in its source, so it appears to need none.
How does Lsp run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as lsp-mcp at 1.0.0.
How current is this page?
The grade is for one exact copy of the source (e16698f7da25), read on 2026-10-06. The repository is watched and re-audited when it changes.