# MCPComp Diagnostics (npm · mcpcomp)

Grade an MCP server's auth against the spec and diagnose which layer a failure is in.

- Trust score: 80/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- npm · `mcpcomp`: 80/100 (this document), [markdown](https://verifymcp.io/servers/dev-mcpcomp-diagnostics/mcpcomp.md), [page](https://verifymcp.io/servers/dev-mcpcomp-diagnostics/mcpcomp)

## Channel facts

- Registry: `npm`
- Package: `mcpcomp`
- Version: `0.6.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-24.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 18 of 63 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 34 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 293 tokens (~97/item across 3 items; 2 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 MCPComp Diagnostics MCP server?

MCPComp Diagnostics runs locally as an npm package, launched with npx -y mcpcomp. 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 dev-mcpcomp-diagnostics -- npx -y mcpcomp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-mcpcomp-diagnostics": {
      "command": "npx",
      "args": [
        "-y",
        "mcpcomp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-mcpcomp-diagnostics": {
      "command": "npx",
      "args": [
        "-y",
        "mcpcomp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-mcpcomp-diagnostics -- npx -y mcpcomp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-mcpcomp-diagnostics": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcpcomp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-mcpcomp-diagnostics --command npx --arg -y --arg mcpcomp
```

### Hermes

```yaml
mcp_servers:
  dev-mcpcomp-diagnostics:
    command: "npx"
    args: ["-y", "mcpcomp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-mcpcomp-diagnostics": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcpcomp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-mcpcomp-diagnostics -t stdio -c npx -a -y mcpcomp
```

### Other

```json
{
  "mcpServers": {
    "dev-mcpcomp-diagnostics": {
      "command": "npx",
      "args": [
        "-y",
        "mcpcomp"
      ]
    }
  }
}
```

## 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-23 (score 80, +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.

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

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

### 2026-09-20 (score 78, −3)

- [functional] Stability: pass → 0.80

### 2026-09-19 (score 81, 0)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 81, +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.

### 2026-09-16 (score 80, +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.

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

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

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

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

## MCP tools (2)

### `scan_auth` (~94 tokens)

Scan MCP authentication

Credential-less audit of an MCP server's authorization setup against the MCP authorization spec. Grades requirement violations (each citing the normative requirement), reports advisories, and lists the fix for every finding.

Input parameters:

- `serverUrl` (string, required): MCP HTTP endpoint to probe, e.g. https://mcp.linear.app/mcp
- `timeoutMs` (integer): per-request timeout in ms, default 8000, max 60000

### `diagnose_auth_failure` (~144 tokens)

Diagnose an MCP auth failure

Classify which layer a failing MCP connection's problem lives in — network, MCP server configuration, identity provider, or (when everything visible from outside passes) the client's own auth state. Use when a client cannot connect to an MCP server and the question is whose fault it is. Pass the failing client's name to expand its known client-side failure patterns.

Input parameters:

- `client` (string): the failing MCP client, to expand its known patterns
- `serverUrl` (string, required): MCP HTTP endpoint to probe, e.g. https://mcp.linear.app/mcp
- `timeoutMs` (integer): per-request timeout in ms, default 8000, max 60000

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-mcpcomp-diagnostics/mcpcomp#diagnostics

## Score history

- 2026-09-24: 80
- 2026-09-23: 80
- 2026-09-22: 79
- 2026-09-21: 79
- 2026-09-20: 78
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 77
- 2026-09-10: 77
- 2026-09-09: 77
- 2026-09-08: 76
- 2026-09-07: 76
- 2026-09-06: 75
- 2026-09-05: 75
- 2026-09-04: 74
- 2026-09-03: 74
- 2026-09-02: 73
- 2026-09-01: 73
- 2026-08-31: 72
- 2026-08-30: 72
- 2026-08-29: 71
- 2026-08-28: 71
- 2026-08-27: 67
- 2026-08-26: 67

## Common questions

### What is the MCPComp Diagnostics MCP server?

MCPComp Diagnostics is an MCP server listed in the public MCP registry as dev.mcpcomp/diagnostics. Grade an MCP server's auth against the spec and diagnose which layer a failure is in. This page covers its npm package (mcpcomp).

### Is the MCPComp Diagnostics MCP server safe to use?

MCPComp Diagnostics scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 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 MCPComp Diagnostics MCP server expose?

MCPComp Diagnostics exposes 2 tools: scan_auth, diagnose_auth_failure. Their descriptions and schemas cost roughly 238 tokens of context every time the server is loaded.

### Is the MCPComp Diagnostics MCP server still maintained?

MCPComp Diagnostics is still listed as active in the MCP registry. We last reached this channel on 24 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 MCPComp Diagnostics MCP server under?

MCPComp Diagnostics declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/mcpcomp
- Socket report: https://socket.dev/npm/package/mcpcomp
- Website: https://www.mcpcomp.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-mcpcomp-diagnostics/mcpcomp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-mcpcomp-diagnostics/mcpcomp.json
- HTML version of this page: https://verifymcp.io/servers/dev-mcpcomp-diagnostics/mcpcomp