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.

mcpspan

NPM · MCPSPAN-MCP · 2 COMPONENTS

Ask your agent about your MCP servers: failing tools, releases, clients, sessions.

+3 this week 84 Trust /100

Last scanned (23 hours ago)

Scores higher than 81% of npm servers

Category Developer Tools

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 Security100
  • 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
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to mcpspan/mcpspan). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1886 tokens (~171/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
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.

  • 3 Nov 26 +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.

  • 1 Nov 26 +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.

  • 30 Oct 26 +1

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

  • 28 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 +1
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.12.0 → 0.13.0 functional
  • 26 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.07 ▲ functional
    • Package version: 0.11.0 → 0.12.0 functional
  • 25 Oct 26 +26
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 1.00 ▲ functional
  • 24 Oct 26 53

    First indexed and scored.

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 4 Nov 2026 · Analysed npm/mcpspan-mcp@0.13.0

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 npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo mcpspan/mcpspan
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/mcpspan/mcpspan/.github/workflows/release.yml@refs/tags/core/v0.13.0
Rekor log index 3519064420
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:885cbb6df0e93c853579dd9dedf8fc34659616370df764bc8bf25117a7ff34c94b93889eb3f74a683885dc9ca0a64957e447654147f4c96ad44ddfb77

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~1,839 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
compare_versions ~178

The server's versions in the window, newest first, each with when it was first seen, its calls, error rate and response times: how a release compares with the one before.

NameTypeReqDescription
clientstring–Only calls from this client type, as list_clients names them, such as claude-code or cursor.
daysinteger–How many days back to look, ending now. 7 when left out. Ignored when from is given.
fromstring–Start of the window, as an ISO 8601 date or time. Overrides days.
serverstring–The MCP server to ask about, by name or id. Leave out when the account has only one.
tostring–End of the window, as an ISO 8601 date or time. Now when left out.

No output schema declared.

No examples provided.

get_overview ~173

Calls, failures, error rate, response times (median and 95th percentile) and the share of each client, for one server over a window.

NameTypeReqDescription
clientstring–Only calls from this client type, as list_clients names them, such as claude-code or cursor.
daysinteger–How many days back to look, ending now. 7 when left out. Ignored when from is given.
fromstring–Start of the window, as an ISO 8601 date or time. Overrides days.
serverstring–The MCP server to ask about, by name or id. Leave out when the account has only one.
tostring–End of the window, as an ISO 8601 date or time. Now when left out.

No output schema declared.

No examples provided.

get_session ~153

One session's calls in the order the agent made them, with each call's outcome and error.

NameTypeReqDescription
daysinteger–How many days back to look, ending now. 7 when left out. Ignored when from is given.
fromstring–Start of the window, as an ISO 8601 date or time. Overrides days.
serverstring–The MCP server to ask about, by name or id. Leave out when the account has only one.
sessionstringyesThe session id, as list_sessions or list_errors gives it.
tostring–End of the window, as an ISO 8601 date or time. Now when left out.

No output schema declared.

No examples provided.

get_tool ~188

Everything recorded about one tool: why its calls failed and the commonest error messages, which arguments the server refused, its parameters, how large its answers are, when its definition changed, how often agents repeated a call, and which call came right before the ones that repeated or failed.

NameTypeReqDescription
daysinteger–How many days back to look, ending now. 7 when left out. Ignored when from is given.
fromstring–Start of the window, as an ISO 8601 date or time. Overrides days.
serverstring–The MCP server to ask about, by name or id. Leave out when the account has only one.
tostring–End of the window, as an ISO 8601 date or time. Now when left out.
toolstringyesThe tool's name, as list_tools gives it.

No output schema declared.

No examples provided.

get_tool_listing ~188

Every tool as agents were shown it when they listed the tools: in how many sessions, how many of those called it, and how large its definition is. Finds tools agents see but never use, and definitions that cost context.

NameTypeReqDescription
clientstring–Only calls from this client type, as list_clients names them, such as claude-code or cursor.
daysinteger–How many days back to look, ending now. 7 when left out. Ignored when from is given.
fromstring–Start of the window, as an ISO 8601 date or time. Overrides days.
serverstring–The MCP server to ask about, by name or id. Leave out when the account has only one.
tostring–End of the window, as an ISO 8601 date or time. Now when left out.

No output schema declared.

No examples provided.

list_clients ~147

The clients that called the server (Claude, Claude Code, Cursor, VS Code, ChatGPT and others), each with its calls, error rate and response times.

NameTypeReqDescription
daysinteger–How many days back to look, ending now. 7 when left out. Ignored when from is given.
fromstring–Start of the window, as an ISO 8601 date or time. Overrides days.
serverstring–The MCP server to ask about, by name or id. Leave out when the account has only one.
tostring–End of the window, as an ISO 8601 date or time. Now when left out.

No output schema declared.

No examples provided.

list_errors ~222

The most recent failed calls, newest first: which tool, which client, when, what kind of failure (a handler that threw, a tool that answered with an error, refused arguments, an unknown tool) and the error message when the server records them.

NameTypeReqDescription
clientstring–Only calls from this client type, as list_clients names them, such as claude-code or cursor.
daysinteger–How many days back to look, ending now. 7 when left out. Ignored when from is given.
fromstring–Start of the window, as an ISO 8601 date or time. Overrides days.
limitinteger–How many to return. 20 when left out.
serverstring–The MCP server to ask about, by name or id. Leave out when the account has only one.
tostring–End of the window, as an ISO 8601 date or time. Now when left out.
toolstring–Only failures of this tool.

No output schema declared.

No examples provided.

list_servers ~25

The MCP servers this mcpspan account reports on, with their names and ids.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_sessions ~215

Recent sessions (one connection each), newest first, with their calls, failures, tools used and calls an agent repeated with the same arguments.

NameTypeReqDescription
clientstring–Only calls from this client type, as list_clients names them, such as claude-code or cursor.
daysinteger–How many days back to look, ending now. 7 when left out. Ignored when from is given.
fromstring–Start of the window, as an ISO 8601 date or time. Overrides days.
limitinteger–How many to return. 20 when left out.
serverstring–The MCP server to ask about, by name or id. Leave out when the account has only one.
tostring–End of the window, as an ISO 8601 date or time. Now when left out.
toolstring–Only sessions that called this tool.
withstring–Only sessions with failures, or with repeated calls.

No output schema declared.

No examples provided.

list_tools ~202

A server's tools ranked by calls, errors, response time or name, each with its calls, errors, error rate and response times.

NameTypeReqDescription
clientstring–Only calls from this client type, as list_clients names them, such as claude-code or cursor.
daysinteger–How many days back to look, ending now. 7 when left out. Ignored when from is given.
fromstring–Start of the window, as an ISO 8601 date or time. Overrides days.
limitinteger–How many to return. 20 when left out.
serverstring–The MCP server to ask about, by name or id. Leave out when the account has only one.
sortstring–How to rank them. calls when left out.
tostring–End of the window, as an ISO 8601 date or time. Now when left out.

No output schema declared.

No examples provided.

list_unknown_tools ~148

Tools that agents asked for but the server does not have: how often, which clients, the closest tool the server does have, and what the agent did next.

NameTypeReqDescription
daysinteger–How many days back to look, ending now. 7 when left out. Ignored when from is given.
fromstring–Start of the window, as an ISO 8601 date or time. Overrides days.
serverstring–The MCP server to ask about, by name or id. Leave out when the account has only one.
tostring–End of the window, as an ISO 8601 date or time. Now when left out.

No output schema declared.

No examples provided.

Install

How do I install the mcpspan MCP server?

mcpspan runs locally as an npm package, launched with npx -y mcpspan-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcpspan-mcp

# add to Claude Code
claude mcp add mcpspan-mcpspan -- npx -y mcpspan-mcp
Common questions

What is the mcpspan MCP server?

mcpspan is an MCP server listed in the public MCP registry as io.github.mcpspan/mcpspan. Ask your agent about your MCP servers: failing tools, releases, clients, sessions. This page covers its npm package (mcpspan-mcp).

Is the mcpspan MCP server safe to use?

mcpspan scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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 mcpspan MCP server expose?

mcpspan exposes 11 tools: list_servers, get_overview, list_tools, get_tool, list_errors, and 6 more. Their descriptions and schemas cost roughly 1,839 tokens of context every time the server is loaded.

Is the mcpspan MCP server still maintained?

mcpspan 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 mcpspan MCP server under?

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