# io.github.Anselmoo/mcp-server-analyzer (pypi · mcp-server-analyzer)

MCP server for Python, JavaScript, and TypeScript code analysis with Ruff, ty, Vulture, and Biome

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- oci · `ghcr.io/anselmoo/mcp-server-analyzer:0.4.1`: 51/100, [markdown](https://verifymcp.io/servers/anselmoo-mcp-server-analyzer/ghcr-io-anselmoo-mcp-server-analyzer-0-4-1.md), [page](https://verifymcp.io/servers/anselmoo-mcp-server-analyzer/ghcr-io-anselmoo-mcp-server-analyzer-0-4-1)
- pypi · `mcp-server-analyzer`: 79/100 (this document), [markdown](https://verifymcp.io/servers/anselmoo-mcp-server-analyzer/mcp-server-analyzer.md), [page](https://verifymcp.io/servers/anselmoo-mcp-server-analyzer/mcp-server-analyzer)

## Channel facts

- Registry: `pypi`
- Package: `mcp-server-analyzer`
- Version: `0.4.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 94/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs a script at install time (build_backend) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does.
  - 1 of 19 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 20 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 497 tokens (~49/item across 10 items; 8 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add anselmoo-mcp-server-analyzer -- uvx mcp-server-analyzer
```

### Cursor

```json
{
  "mcpServers": {
    "anselmoo-mcp-server-analyzer": {
      "command": "uvx",
      "args": [
        "mcp-server-analyzer"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "anselmoo-mcp-server-analyzer": {
      "command": "uvx",
      "args": [
        "mcp-server-analyzer"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add anselmoo-mcp-server-analyzer -- uvx mcp-server-analyzer
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "anselmoo-mcp-server-analyzer": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-server-analyzer"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add anselmoo-mcp-server-analyzer --command uvx --arg mcp-server-analyzer
```

### Hermes

```yaml
mcp_servers:
  anselmoo-mcp-server-analyzer:
    command: "uvx"
    args: ["mcp-server-analyzer"]
```

### Netclaw

```json
{
  "McpServers": {
    "anselmoo-mcp-server-analyzer": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-server-analyzer"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add anselmoo-mcp-server-analyzer -t stdio -c uvx -a mcp-server-analyzer
```

### Other

```json
{
  "mcpServers": {
    "anselmoo-mcp-server-analyzer": {
      "command": "uvx",
      "args": [
        "mcp-server-analyzer"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 79, +1)

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

### 2026-09-17 (score 78, +1)

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

### 2026-09-15 (score 77, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 61, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-13 (score 76, +1)

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

### 2026-09-11 (score 75, +1)

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

### 2026-09-10 (score 74, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-03 (score 71)

First indexed and scored.

## MCP tools (8)

### `ruff-check` (~48 tokens)

Ruff Check

Lint Python code using RUFF to identify style violations and potential errors.

Input parameters:

- `code` (string, required): Python code to analyze
- `config_path`: Optional path to RUFF configuration file

Output parameters:

- `fixable_issues` (integer): Number of auto-fixable issues
- `issues` (array): List of linting issues found
- `total_issues` (integer): Total number of issues

### `ruff-format` (~43 tokens)

Ruff Format

Format Python code using RUFF's fast formatter.

Input parameters:

- `code` (string, required): Python code to format
- `config_path`: Optional path to RUFF configuration file

Output parameters:

- `changed` (boolean): Whether the code was modified during formatting
- `formatted_code` (string): The formatted Python code

### `ruff-check-ci` (~66 tokens)

Ruff Check Ci

Run RUFF linter with CI/CD-specific output formats.

Input parameters:

- `code` (string, required): Python code to lint
- `config_path`: Optional path to RUFF configuration file
- `output_format` (string): Output format (json, gitlab, github, sarif)

Output parameters:

- `format` (string): Output format used (json, gitlab, github, sarif)
- `output` (string): Raw RUFF output in the requested format
- `success` (boolean): Whether the check completed without errors

### `ty-check` (~42 tokens)

Ty Check

Type-check Python code using ty.

Input parameters:

- `code` (string, required): Python code to analyze
- `project_path`: Optional project directory used for ty config and import resolution

Output parameters:

- `diagnostics` (array): List of type diagnostics found
- `error_count` (integer): Number of error diagnostics
- `total_diagnostics` (integer): Total number of diagnostics
- `warning_count` (integer): Number of warning diagnostics

### `vulture-scan` (~51 tokens)

Vulture Scan

Detect dead/unused code using VULTURE.

Input parameters:

- `code` (string, required): Python code to analyze
- `min_confidence` (integer): Minimum confidence level (0-100) for reporting items

Output parameters:

- `high_confidence_items` (integer): Number of items with confidence >= 80
- `total_items` (integer): Total number of unused items
- `unused_items` (array): List of unused code items found

### `biome-check` (~66 tokens)

Biome Check

Lint JavaScript/TypeScript code using Biome.

Input parameters:

- `code` (string, required): JS/TS/JSX/TSX code to analyze
- `filename` (string): Virtual filename used to select parser and rule set (e.g., "app.ts", "index.jsx")

Output parameters:

- `errors` (integer): Number of error-severity diagnostics
- `issues` (array): List of diagnostics found
- `total_issues` (integer): Total number of diagnostics
- `warnings` (integer): Number of warning-severity diagnostics

### `biome-format` (~62 tokens)

Biome Format

Format JavaScript/TypeScript code using Biome.

Input parameters:

- `code` (string, required): JS/TS/JSX/TSX code to format
- `filename` (string): Virtual filename used to select parser (e.g., "app.ts", "index.jsx")

Output parameters:

- `changed` (boolean): Whether the code was modified during formatting
- `formatted_code` (string): The formatted JS/TS code

### `analyze-code` (~90 tokens)

Analyze Code

Comprehensive analysis combining Ruff linting, ty type checking, and Vulture dead code detection.

Input parameters:

- `code` (string, required): 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

Output parameters:

- `ruff_result` (object): RUFF linting results
- `summary` (object): Summary statistics of the analysis
- `ty_result` (object): ty type-checking results
- `vulture_result` (object): VULTURE dead code detection results

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/anselmoo-mcp-server-analyzer/mcp-server-analyzer#diagnostics

## Score history

- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 78
- 2026-09-17: 78
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 61
- 2026-09-13: 76
- 2026-09-12: 75
- 2026-09-11: 75
- 2026-09-10: 74
- 2026-09-09: 71
- 2026-09-08: 71
- 2026-09-07: 71
- 2026-09-06: 71
- 2026-09-05: 71
- 2026-09-04: 71
- 2026-09-03: 71

## Common questions

### 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 79 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.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 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.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.

## Links

- PyPI project: https://pypi.org/project/mcp-server-analyzer/
- Socket report: https://socket.dev/pypi/package/mcp-server-analyzer
- Repository: https://github.com/Anselmoo/mcp-server-analyzer
- Changelog RSS feed: https://verifymcp.io/servers/anselmoo-mcp-server-analyzer/mcp-server-analyzer.xml
- Changelog JSON feed: https://verifymcp.io/servers/anselmoo-mcp-server-analyzer/mcp-server-analyzer.json
- HTML version of this page: https://verifymcp.io/servers/anselmoo-mcp-server-analyzer/mcp-server-analyzer