pyscn
PYPI · PYSCN-MCP
Python code analysis for AI agents: complexity, dead code, clones, coupling, and a health score.
Available components
Last scanned (12 hours ago)
Scores higher than 88% of PyPI servers
Category Testing and QA
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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- 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 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 811 tokens (~101/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Provenance: unverified → fail ▼ security
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 0
- Provenance: fail → unverified ▼ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Package version: 1.33.0 → 1.33.1 functional
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
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 5 Nov 2026 · Analysed pypi/pyscn-mcp@1.33.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
analyze_code ~143
Comprehensive Python code quality analysis with complexity, dead code, clone detection, and coupling metrics
| Name | Type | Req | Description |
|---|---|---|---|
| analyses | array | – | Array of analyses to run. Options: complexity, dead_code, clone, cbo, lcom, deps, communities. Default: all analyses, including communities |
| output_mode | string | – | Response detail level. "summary" (default) returns health score and high-level metrics. "full" returns the complete report including community_analysis and its compact community_context_map when comm… |
| path | string | yes | Path to Python code (file or directory) to analyze |
| recursive | boolean | – | Recursively analyze directories (default: true) |
No output schema declared.
No examples provided.
check_cohesion ~80
Analyze class cohesion (LCOM4 - Lack of Cohesion of Methods) metrics
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Maximum findings in summary or detailed output; 0 means unlimited (default: 0) |
| output_mode | string | – | Response detail level (default: summary) |
| path | string | yes | Path to Python code to analyze |
No output schema declared.
No examples provided.
check_complexity ~127
Analyze cyclomatic complexity of Python execution scopes
| Name | Type | Req | Description |
|---|---|---|---|
| max_complexity | number | – | Maximum allowed complexity (default: 10; 0 uses the default) |
| max_results | integer | – | Maximum findings in summary or detailed output; 0 means unlimited (default: 0) |
| min_complexity | number | – | Minimum complexity to report (default: 1) |
| output_mode | string | – | Response detail level (default: summary) |
| path | string | yes | Path to Python code to analyze |
| show_details | boolean | – | Include detailed metrics (default: true) |
No output schema declared.
No examples provided.
check_coupling ~100
Analyze class coupling (CBO - Coupling Between Objects) metrics
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Maximum findings in summary or detailed output; 0 means unlimited (default: 0) |
| min_cbo | integer | – | Minimum CBO for high-coupling findings (default: 10) |
| output_mode | string | – | Response detail level (default: summary) |
| path | string | yes | Path to Python code to analyze |
No output schema declared.
No examples provided.
detect_clones ~140
Detect code clones using APTED tree edit distance and LSH acceleration
| Name | Type | Req | Description |
|---|---|---|---|
| group_clones | boolean | – | Group related clones together (default: true) |
| max_results | integer | – | Maximum findings in summary or detailed output; 0 means unlimited (default: 0) |
| min_lines | number | – | Minimum SLOC to consider as clone (default: 8) |
| output_mode | string | – | Response detail level (default: summary) |
| path | string | yes | Path to Python code to analyze |
| similarity_threshold | number | – | Minimum similarity threshold 0.0-1.0 (default: 0.8) |
No output schema declared.
No examples provided.
detect_di_antipatterns ~88
Detect Dependency Injection anti-patterns in Python code (constructor over-injection, hidden dependencies, concrete dependencies, service locator)
| Name | Type | Req | Description |
|---|---|---|---|
| constructor_param_threshold | number | – | Maximum allowed constructor parameters (default: 5) |
| min_severity | string | – | Minimum severity: info, warning, error (default: warning) |
| path | string | yes | Path to Python code to analyze |
No output schema declared.
No examples provided.
find_dead_code ~95
Find unreachable code using Control Flow Graph (CFG) analysis
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Maximum findings in summary or detailed output; 0 means unlimited (default: 0) |
| min_severity | string | – | Minimum severity: info, warning, error (default: warning) |
| output_mode | string | – | Response detail level (default: summary) |
| path | string | yes | Path to Python code to analyze |
No output schema declared.
No examples provided.
get_health_score ~38
Get overall code health score (0-100) with grade and category scores
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to Python code to analyze |
No output schema declared.
No examples provided.
How do I install the pyscn MCP server?
pyscn runs locally as a PyPI package, launched with uvx pyscn-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · pyscn-mcp
claude mcp add ludo-technologies-pyscn -- uvx pyscn-mcp
What is the pyscn MCP server?
pyscn is an MCP server listed in the public MCP registry as io.github.ludo-technologies/pyscn. Python code analysis for AI agents: complexity, dead code, clones, coupling, and a health score. This page covers its PyPI package (pyscn-mcp).
Is the pyscn MCP server safe to use?
pyscn scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 pyscn MCP server expose?
pyscn exposes 8 tools: analyze_code, check_cohesion, check_complexity, check_coupling, detect_clones, and 3 more. Their descriptions and schemas cost roughly 811 tokens of context every time the server is loaded.
Is the pyscn MCP server still maintained?
pyscn is still listed as active in the MCP registry. We last reached this channel on 5 November 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 pyscn MCP server under?
pyscn declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the pyscn MCP server?
VerifyMCP ran 16 checks on pyscn, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.