io.github.theUpsider/lsp-mcp
NPM · @THEUPSIDER/LSP-MCP · SCANNED SEP 20
Universal LSP MCP server
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 55 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability53
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 625 tokens (~36/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.theUpsider/lsp-mcp server?
io.github.theUpsider/lsp-mcp runs locally as an npm package, launched with npx -y @theupsider/lsp-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @theupsider/lsp-mcp
claude mcp add theupsider-lsp-mcp -- npx -y @theupsider/lsp-mcp
{
"mcpServers": {
"theupsider-lsp-mcp": {
"command": "npx",
"args": [
"-y",
"@theupsider/lsp-mcp"
]
}
}
} {
"servers": {
"theupsider-lsp-mcp": {
"command": "npx",
"args": [
"-y",
"@theupsider/lsp-mcp"
]
}
}
} codex mcp add theupsider-lsp-mcp -- npx -y @theupsider/lsp-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theupsider-lsp-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@theupsider/lsp-mcp"
],
"enabled": true
}
}
} openclaw mcp add theupsider-lsp-mcp --command npx --arg -y --arg @theupsider/lsp-mcp
mcp_servers:
theupsider-lsp-mcp:
command: "npx"
args: ["-y", "@theupsider/lsp-mcp"] {
"McpServers": {
"theupsider-lsp-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@theupsider/lsp-mcp"
]
}
}
} assistant mcp add theupsider-lsp-mcp -t stdio -c npx -a -y @theupsider/lsp-mcp
{
"mcpServers": {
"theupsider-lsp-mcp": {
"command": "npx",
"args": [
"-y",
"@theupsider/lsp-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −2
- Stability: pass → 0.80 functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@theupsider/lsp-mcp@0.1.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
lsp_apply_workspace_edit ~23
Apply raw workspace edit
| Name | Type | Req | Description |
|---|---|---|---|
| edit | object | yes | – |
No output schema declared.
No examples provided.
lsp_code_action ~49
List or apply code actions
| Name | Type | Req | Description |
|---|---|---|---|
| apply | – | – | – |
| character | integer | yes | – |
| file | string | yes | – |
| line | integer | yes | – |
| range | object | – | – |
No output schema declared.
No examples provided.
lsp_completion ~34
Get completions
| Name | Type | Req | Description |
|---|---|---|---|
| character | integer | yes | – |
| file | string | yes | – |
| line | integer | yes | – |
No output schema declared.
No examples provided.
lsp_definition ~33
Find definitions
| Name | Type | Req | Description |
|---|---|---|---|
| character | integer | yes | – |
| file | string | yes | – |
| line | integer | yes | – |
No output schema declared.
No examples provided.
lsp_diagnostics ~87
Get errors and warnings. Pass a file path to trigger analysis of that file and its language server, then return diagnostics for that file (scope: file) or all files seen so far (scope: workspace). Omit file for workspace scope to query whatever has been opened previously.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | – |
| language | string | – | – |
| scope | string | – | – |
No output schema declared.
No examples provided.
lsp_document_symbols ~21
List document symbols
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | – |
No output schema declared.
No examples provided.
lsp_formatting ~27
Format document
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | – |
| options | object | – | – |
No output schema declared.
No examples provided.
lsp_health ~15
Show LSP server health
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lsp_hover ~34
Show hover information
| Name | Type | Req | Description |
|---|---|---|---|
| character | integer | yes | – |
| file | string | yes | – |
| line | integer | yes | – |
No output schema declared.
No examples provided.
lsp_implementation ~34
Find implementations
| Name | Type | Req | Description |
|---|---|---|---|
| character | integer | yes | – |
| file | string | yes | – |
| line | integer | yes | – |
No output schema declared.
No examples provided.
lsp_init ~57
Initialize LSP for a project root. Pass languages to pre-warm specific servers; omit to auto-detect from project files (lazy startup per file if none found).
| Name | Type | Req | Description |
|---|---|---|---|
| languages | array | – | – |
| root | string | yes | – |
No output schema declared.
No examples provided.
lsp_range_formatting ~36
Format selected range
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | – |
| options | object | – | – |
| range | object | yes | – |
No output schema declared.
No examples provided.
lsp_references ~42
Find references
| Name | Type | Req | Description |
|---|---|---|---|
| character | integer | yes | – |
| file | string | yes | – |
| includeDeclaration | boolean | – | – |
| line | integer | yes | – |
No output schema declared.
No examples provided.
lsp_rename ~42
Rename symbol
| Name | Type | Req | Description |
|---|---|---|---|
| character | integer | yes | – |
| file | string | yes | – |
| line | integer | yes | – |
| newName | string | yes | – |
No output schema declared.
No examples provided.
lsp_signature_help ~35
Show signature help
| Name | Type | Req | Description |
|---|---|---|---|
| character | integer | yes | – |
| file | string | yes | – |
| line | integer | yes | – |
No output schema declared.
No examples provided.
lsp_type_definition ~35
Find type definitions
| Name | Type | Req | Description |
|---|---|---|---|
| character | integer | yes | – |
| file | string | yes | – |
| line | integer | yes | – |
No output schema declared.
No examples provided.
lsp_workspace_symbols ~21
Search workspace symbols
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | – |
No output schema declared.
No examples provided.
What is the io.github.theUpsider/lsp-mcp server?
io.github.theUpsider/lsp-mcp is listed in the public MCP registry as io.github.theUpsider/lsp-mcp. Universal LSP MCP server. This page covers its npm package (@theupsider/lsp-mcp).
Is the io.github.theUpsider/lsp-mcp server safe to use?
io.github.theUpsider/lsp-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.theUpsider/lsp-mcp server expose?
io.github.theUpsider/lsp-mcp exposes 17 tools: lsp_init, lsp_hover, lsp_definition, lsp_references, lsp_document_symbols, and 12 more. Their descriptions and schemas cost roughly 625 tokens of context every time the server is loaded.
Is the io.github.theUpsider/lsp-mcp server still maintained?
io.github.theUpsider/lsp-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.theUpsider/lsp-mcp server under?
io.github.theUpsider/lsp-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.