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.

MCPComp Diagnostics

NPM · MCPCOMP · SCANNED SEP 24

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

Available components

npm · mcpcomp 80
0 this week 80 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 Security99
  • 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
  • 18 of 63 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 293 tokens (~97/item across 3 items; 2 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
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.

npm · mcpcomp

# add to Claude Code
claude mcp add dev-mcpcomp-diagnostics -- npx -y mcpcomp
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-mcpcomp-diagnostics": {
      "command": "npx",
      "args": [
        "-y",
        "mcpcomp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-mcpcomp-diagnostics": {
      "command": "npx",
      "args": [
        "-y",
        "mcpcomp"
      ]
    }
  }
}
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-mcpcomp-diagnostics --command npx --arg -y --arg mcpcomp
# ~/.hermes/config.yaml
mcp_servers:
  dev-mcpcomp-diagnostics:
    command: "npx"
    args: ["-y", "mcpcomp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-mcpcomp-diagnostics": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcpcomp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dev-mcpcomp-diagnostics -t stdio -c npx -a -y mcpcomp
// mcp.json
{
  "mcpServers": {
    "dev-mcpcomp-diagnostics": {
      "command": "npx",
      "args": [
        "-y",
        "mcpcomp"
      ]
    }
  }
}
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.

  • 23 Sept 26 +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.

  • 21 Sept 26 +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.

  • 20 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 19 Sept 26 0
    • Stability: 0.97 → pass security
  • 18 Sept 26 +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.

  • 16 Sept 26 +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.

  • 14 Sept 26 +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.

  • 12 Sept 26 +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.

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 24 Sept 2026 · Analysed npm/mcpcomp@0.6.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 63 packages
Packages resolved 63
Stale 17
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~238 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
diagnose_auth_failure ~144

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.

NameTypeReqDescription
clientstring–the failing MCP client, to expand its known patterns
serverUrlstringyesMCP HTTP endpoint to probe, e.g. https://mcp.linear.app/mcp
timeoutMsinteger–per-request timeout in ms, default 8000, max 60000

No output schema declared.

No examples provided.

scan_auth ~94

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.

NameTypeReqDescription
serverUrlstringyesMCP HTTP endpoint to probe, e.g. https://mcp.linear.app/mcp
timeoutMsinteger–per-request timeout in ms, default 8000, max 60000

No output schema declared.

No examples provided.

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.