Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

pyscn

PYPI · PYSCN-MCP · SCANNED SEP 21

Python code analysis for AI agents: complexity, dead code, clones, coupling, and a health score.

Available components

0 this week 66 Trust /100
Trust breakdown (7 categories)

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 Security38
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Install-script risk not yet assessed.Unverified
  • 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 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 810 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 Management97
  • Stability observed for 29 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
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
Install

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

# add to Claude Code
claude mcp add ludo-technologies-pyscn -- uvx pyscn-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "ludo-technologies-pyscn": {
      "command": "uvx",
      "args": [
        "pyscn-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ludo-technologies-pyscn": {
      "command": "uvx",
      "args": [
        "pyscn-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ludo-technologies-pyscn -- uvx pyscn-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ludo-technologies-pyscn": {
      "type": "local",
      "command": [
        "uvx",
        "pyscn-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ludo-technologies-pyscn --command uvx --arg pyscn-mcp
# ~/.hermes/config.yaml
mcp_servers:
  ludo-technologies-pyscn:
    command: "uvx"
    args: ["pyscn-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ludo-technologies-pyscn": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "pyscn-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ludo-technologies-pyscn -t stdio -c uvx -a pyscn-mcp
// mcp.json
{
  "mcpServers": {
    "ludo-technologies-pyscn": {
      "command": "uvx",
      "args": [
        "pyscn-mcp"
      ]
    }
  }
}
Changelog

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.

  • 21 Sept 26 +30
    • Malware scan: pass → unverified security
    • Injection markers: unverified → pass security
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.97 functional
  • 20 Sept 26 −29
    • Stability: 0.90 → unverified security
    • Tool safety: pass → unverified security
    • Malware scan: unverified → pass security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • Package version: 1.32.0 → 1.32.1 functional
  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
    • Package version: 1.31.3 → 1.32.0 functional
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +29
    • Malware scan: pass → unverified security
    • Injection markers: unverified → pass security
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.90 functional
    • Package version: 1.31.2 → 1.31.3 functional
  • 11 Sept 26 −46
    • Stability: pass → unverified security
    • Tool safety: pass → unverified security
    • Malware scan: pass → unverified security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • Stability: pass → 0.87 functional
    • Package version: 1.31.2 → 1.31.3 functional
Diagnostics

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 21 Sept 2026 · Analysed pypi/pyscn-mcp@1.32.1

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 →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~810 tokens

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 →

Tool Tokens
analyze_code ~143

Comprehensive Python code quality analysis with complexity, dead code, clone detection, and coupling metrics

NameTypeReqDescription
analysesarrayArray of analyses to run. Options: complexity, dead_code, clone, cbo, lcom, deps, communities. Default: all analyses, including communities
output_modestringResponse 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…
pathstringyesPath to Python code (file or directory) to analyze
recursivebooleanRecursively analyze directories (default: true)

No output schema declared.

No examples provided.

check_cohesion ~80

Analyze class cohesion (LCOM4 - Lack of Cohesion of Methods) metrics

NameTypeReqDescription
max_resultsintegerMaximum findings in summary or detailed output; 0 means unlimited (default: 0)
output_modestringResponse detail level (default: summary)
pathstringyesPath to Python code to analyze

No output schema declared.

No examples provided.

check_complexity ~127

Analyze cyclomatic complexity of Python execution scopes

NameTypeReqDescription
max_complexitynumberMaximum allowed complexity (default: 10; 0 uses the default)
max_resultsintegerMaximum findings in summary or detailed output; 0 means unlimited (default: 0)
min_complexitynumberMinimum complexity to report (default: 1)
output_modestringResponse detail level (default: summary)
pathstringyesPath to Python code to analyze
show_detailsbooleanInclude detailed metrics (default: true)

No output schema declared.

No examples provided.

check_coupling ~100

Analyze class coupling (CBO - Coupling Between Objects) metrics

NameTypeReqDescription
max_resultsintegerMaximum findings in summary or detailed output; 0 means unlimited (default: 0)
min_cbointegerMinimum CBO for high-coupling findings (default: 10)
output_modestringResponse detail level (default: summary)
pathstringyesPath to Python code to analyze

No output schema declared.

No examples provided.

detect_clones ~139

Detect code clones using APTED tree edit distance and LSH acceleration

NameTypeReqDescription
group_clonesbooleanGroup related clones together (default: true)
max_resultsintegerMaximum findings in summary or detailed output; 0 means unlimited (default: 0)
min_linesnumberMinimum lines to consider as clone (default: 5)
output_modestringResponse detail level (default: summary)
pathstringyesPath to Python code to analyze
similarity_thresholdnumberMinimum 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)

NameTypeReqDescription
constructor_param_thresholdnumberMaximum allowed constructor parameters (default: 5)
min_severitystringMinimum severity: info, warning, error (default: warning)
pathstringyesPath 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

NameTypeReqDescription
max_resultsintegerMaximum findings in summary or detailed output; 0 means unlimited (default: 0)
min_severitystringMinimum severity: info, warning, error (default: warning)
output_modestringResponse detail level (default: summary)
pathstringyesPath 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

NameTypeReqDescription
pathstringyesPath to Python code to analyze

No output schema declared.

No examples provided.

Common questions

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 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 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 810 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 21 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 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.