io.github.daedalus/mcp-pyright
PYPI · MCP-PYRIGHT · SCANNED SEP 20
MCP server that exposes Pyright language server functionality
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 17 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 (MIT).Pass
- Actively maintained (last published 172 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 528 tokens (~66/item across 8 items; 7 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.daedalus/mcp-pyright server?
io.github.daedalus/mcp-pyright runs locally as a PyPI package, launched with uvx mcp-pyright. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-pyright
claude mcp add daedalus-mcp-pyright -- uvx mcp-pyright
{
"mcpServers": {
"daedalus-mcp-pyright": {
"command": "uvx",
"args": [
"mcp-pyright"
]
}
}
} {
"servers": {
"daedalus-mcp-pyright": {
"command": "uvx",
"args": [
"mcp-pyright"
]
}
}
} codex mcp add daedalus-mcp-pyright -- uvx mcp-pyright
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"daedalus-mcp-pyright": {
"type": "local",
"command": [
"uvx",
"mcp-pyright"
],
"enabled": true
}
}
} openclaw mcp add daedalus-mcp-pyright --command uvx --arg mcp-pyright
mcp_servers:
daedalus-mcp-pyright:
command: "uvx"
args: ["mcp-pyright"] {
"McpServers": {
"daedalus-mcp-pyright": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcp-pyright"
]
}
}
} assistant mcp add daedalus-mcp-pyright -t stdio -c uvx -a mcp-pyright
{
"mcpServers": {
"daedalus-mcp-pyright": {
"command": "uvx",
"args": [
"mcp-pyright"
]
}
}
} 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.
- 20 Sept 26 −2
- Stability: pass → 0.80 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 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.
- 16 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.
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 −2
- Stability: pass → 0.80 functional
- 12 Sept 26 0
- Stability: 0.97 → pass security
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 pypi/mcp-pyright@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 17 packages
| Packages resolved | 17 |
|---|---|
| Stale | 1 |
| 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 →
check_types Check Types ~102
Check types in a Python file or string of code. Performs type checking using Pyright and returns diagnostics.
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | Python code as string (mutually exclusive with file_path). |
| file_path | – | – | Path to Python file (mutually exclusive with code). |
| python_path | – | – | Optional path to Python interpreter. |
| type_checker_mode | string | – | Type checking mode - "basic", "strict", or "overload" (default: "basic"). |
Structured output declared, but exposes no named fields.
No examples provided.
find_references Find References ~71
Find all references to a symbol at a specific position. Returns all reference locations for the symbol at the given position.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code as string. |
| position | integer | yes | Character position (0-indexed) in the code. |
| python_path | – | – | Optional path to Python interpreter. |
Structured output declared, but exposes no named fields.
No examples provided.
format_code Format Code ~45
Format Python code. Formats the given Python code using pyright's formatter.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code as string. |
| python_path | – | – | Optional path to Python interpreter. |
Structured output declared, but exposes no named fields.
No examples provided.
get_completions Get Completions ~68
Get code completions at a specific position. Returns available completions at the given cursor position.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code as string. |
| position | integer | yes | Character position (0-indexed) in the code. |
| python_path | – | – | Optional path to Python interpreter. |
Structured output declared, but exposes no named fields.
No examples provided.
get_definition Get Definition ~69
Get definition location at a specific position. Returns the location of the definition for the symbol at the given position.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code as string. |
| position | integer | yes | Character position (0-indexed) in the code. |
| python_path | – | – | Optional path to Python interpreter. |
Structured output declared, but exposes no named fields.
No examples provided.
get_document_symbols Get Document Symbols ~51
Get all symbols in a Python document. Returns document symbols including functions, classes, variables, etc.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code as string. |
| python_path | – | – | Optional path to Python interpreter. |
Structured output declared, but exposes no named fields.
No examples provided.
get_hover Get Hover ~68
Get hover information at a specific position. Returns type information and documentation for the symbol at the given position.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code as string. |
| position | integer | yes | Character position (0-indexed) in the code. |
| python_path | – | – | Optional path to Python interpreter. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.daedalus/mcp-pyright server?
io.github.daedalus/mcp-pyright is listed in the public MCP registry as io.github.daedalus/mcp-pyright. MCP server that exposes Pyright language server functionality. This page covers its PyPI package (mcp-pyright).
Is the io.github.daedalus/mcp-pyright server safe to use?
io.github.daedalus/mcp-pyright scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.daedalus/mcp-pyright server expose?
io.github.daedalus/mcp-pyright exposes 7 tools: check_types, get_hover, get_completions, get_definition, find_references, and 2 more. Their descriptions and schemas cost roughly 474 tokens of context every time the server is loaded.
Is the io.github.daedalus/mcp-pyright server still maintained?
io.github.daedalus/mcp-pyright 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.daedalus/mcp-pyright server under?
io.github.daedalus/mcp-pyright declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.