io.github.Anselmoo/mcp-server-analyzer
PYPI · MCP-SERVER-ANALYZER · 2 COMPONENTS
MCP server for Python, JavaScript, and TypeScript code analysis with Ruff, ty, Vulture, and Biome
Available components
Last scanned (15 hours ago)
Scores higher than 84% of PyPI servers
Category Developer Tools
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 19 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Anselmoo/mcp-server-analyzer). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 65 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
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 497 tokens (~49/item across 10 items; 8 tools + 2 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
- 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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.
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 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 4 Nov 2026 · Analysed pypi/mcp-server-analyzer@0.4.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Anselmoo/mcp-server-analyzer |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Anselmoo/mcp-server-analyzer/.github/workflows/ci-cd.yml@refs/tags/v0.4.1 |
| Rekor log index | 2655348621 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:8c33d708659b508c6613e96f6a2b54b91e8a12f6267f9a09e309acd9304db7ab |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | uv_build |
Background: Why install scripts are a supply-chain risk →
Dependencies 19 packages
| Packages resolved | 19 |
|---|---|
| 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 →
analyze-code Analyze Code ~90
Comprehensive analysis combining Ruff linting, ty type checking, and Vulture dead code detection.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code to analyze |
| min_confidence | integer | – | Minimum confidence level for VULTURE (default: 80) |
| project_path | – | – | Optional project directory used by ty for config and import resolution |
| ruff_config_path | – | – | Optional path to RUFF configuration file |
| Name | Type | Req | Description |
|---|---|---|---|
| ruff_result | object | yes | RUFF linting results |
| summary | object | yes | Summary statistics of the analysis |
| ty_result | object | yes | ty type-checking results |
| vulture_result | object | yes | VULTURE dead code detection results |
No examples provided.
biome-check Biome Check ~66
Lint JavaScript/TypeScript code using Biome.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | JS/TS/JSX/TSX code to analyze |
| filename | string | – | Virtual filename used to select parser and rule set (e.g., "app.ts", "index.jsx") |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | integer | yes | Number of error-severity diagnostics |
| issues | array | yes | List of diagnostics found |
| total_issues | integer | yes | Total number of diagnostics |
| warnings | integer | yes | Number of warning-severity diagnostics |
No examples provided.
biome-format Biome Format ~62
Format JavaScript/TypeScript code using Biome.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | JS/TS/JSX/TSX code to format |
| filename | string | – | Virtual filename used to select parser (e.g., "app.ts", "index.jsx") |
| Name | Type | Req | Description |
|---|---|---|---|
| changed | boolean | yes | Whether the code was modified during formatting |
| formatted_code | string | yes | The formatted JS/TS code |
No examples provided.
ruff-check Ruff Check ~48
Lint Python code using RUFF to identify style violations and potential errors.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code to analyze |
| config_path | – | – | Optional path to RUFF configuration file |
| Name | Type | Req | Description |
|---|---|---|---|
| fixable_issues | integer | yes | Number of auto-fixable issues |
| issues | array | yes | List of linting issues found |
| total_issues | integer | yes | Total number of issues |
No examples provided.
ruff-check-ci Ruff Check Ci ~66
Run RUFF linter with CI/CD-specific output formats.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code to lint |
| config_path | – | – | Optional path to RUFF configuration file |
| output_format | string | – | Output format (json, gitlab, github, sarif) |
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | Output format used (json, gitlab, github, sarif) |
| output | string | yes | Raw RUFF output in the requested format |
| success | boolean | yes | Whether the check completed without errors |
No examples provided.
ruff-format Ruff Format ~43
Format Python code using RUFF's fast formatter.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code to format |
| config_path | – | – | Optional path to RUFF configuration file |
| Name | Type | Req | Description |
|---|---|---|---|
| changed | boolean | yes | Whether the code was modified during formatting |
| formatted_code | string | yes | The formatted Python code |
No examples provided.
ty-check Ty Check ~42
Type-check Python code using ty.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code to analyze |
| project_path | – | – | Optional project directory used for ty config and import resolution |
| Name | Type | Req | Description |
|---|---|---|---|
| diagnostics | array | yes | List of type diagnostics found |
| error_count | integer | yes | Number of error diagnostics |
| total_diagnostics | integer | yes | Total number of diagnostics |
| warning_count | integer | yes | Number of warning diagnostics |
No examples provided.
vulture-scan Vulture Scan ~51
Detect dead/unused code using VULTURE.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code to analyze |
| min_confidence | integer | – | Minimum confidence level (0-100) for reporting items |
| Name | Type | Req | Description |
|---|---|---|---|
| high_confidence_items | integer | yes | Number of items with confidence >= 80 |
| total_items | integer | yes | Total number of unused items |
| unused_items | array | yes | List of unused code items found |
No examples provided.
How do I install the io.github.Anselmoo/mcp-server-analyzer server?
io.github.Anselmoo/mcp-server-analyzer runs locally as a PyPI package, launched with uvx mcp-server-analyzer. 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-server-analyzer
claude mcp add anselmoo-mcp-server-analyzer -- uvx mcp-server-analyzer
What is the io.github.Anselmoo/mcp-server-analyzer server?
io.github.Anselmoo/mcp-server-analyzer is listed in the public MCP registry as io.github.Anselmoo/mcp-server-analyzer. MCP server for Python, JavaScript, and TypeScript code analysis with Ruff, ty, Vulture, and Biome. This page covers its PyPI package (mcp-server-analyzer).
Is the io.github.Anselmoo/mcp-server-analyzer server safe to use?
io.github.Anselmoo/mcp-server-analyzer scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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.Anselmoo/mcp-server-analyzer server expose?
io.github.Anselmoo/mcp-server-analyzer exposes 8 tools: ruff-check, ruff-format, ruff-check-ci, ty-check, vulture-scan, and 3 more. Their descriptions and schemas cost roughly 468 tokens of context every time the server is loaded.
Is the io.github.Anselmoo/mcp-server-analyzer server still maintained?
io.github.Anselmoo/mcp-server-analyzer is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.Anselmoo/mcp-server-analyzer server under?
io.github.Anselmoo/mcp-server-analyzer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.