mcpspan

io.github.mcpspan由 GitHub 帳號 mcpspan 發布v0.14.0更新於 Nov 6, 2026

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

已驗證Streamable HTTP可網頁執行開發者工具安全與監控資料與分析

概覽

AI 產生的概覽

讓助理查詢 mcpspan 中你自己 MCP 伺服器的分析資料:失敗的工具、錯誤率、用戶端、版本與工作階段。

可以做什麼
  • 列出帳號回報的伺服器,並查看某個伺服器的呼叫量、失敗數、錯誤率、回應時間與用戶端組成
  • 依呼叫量、錯誤、回應時間或名稱排序伺服器的工具,並深入查看單一工具的失敗原因、被拒參數、回應大小、定義變更與重複呼叫
  • 查看最近的失敗呼叫、代理要求但伺服器沒有的工具,以及連線過的用戶端
  • 並排比較各版本,查看代理看到卻從未呼叫的工具,並逐一呼叫檢視工作階段
  • 查看代理卡在哪裡、如何恢復以及接下來嘗試了什麼
適用情境
當你執行接入 mcpspan 的 MCP 伺服器,想用自然語言問代理某個工具為何失敗、新版本與前一版相比如何、哪個用戶端或工具出了問題,而不必手動翻看儀表板時適用。
執行需求
兩種方式:連線 mcpspan API 的 /mcp 遠端位址並以 OAuth 登入;或以 npx 啟動本機程序(需 Node 20 或更新版本),透過 MCPSPAN_READ_TOKEN 提供讀取權杖。自架安裝需設定 MCPSPAN_URL,命令列方式需 mcpspan 0.9.0 或更新版本,位址方式需 0.13.0 或更新版本。另需一個有資料的 mcpspan 帳號。
安裝前請注意
MCPSPAN_READ_TOKEN 中的讀取權杖是只顯示一次的憑證,外洩後應在設定中撤銷;若代理透過網際網路存取自架安裝,請在前面加上 HTTPS,因為權杖會隨每次請求傳送。OAuth 授權依應用程式授予,可在已連線應用程式中隨時中斷。所有工具皆為唯讀,不會變更任何內容,也不會把資料送到你的 mcpspan 以外的地方。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 mcpspan,將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.mcpspan%2Fmcpspan/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "mcpspan": {
      "type": "http",
      "url": "https://api.mcpspan.com/mcp"
    }
  }
}

README

mcpspan-mcp

Ask your AI agent about your MCP servers. Claude Code, Cursor or any other MCP client answers from your mcpspan numbers:

  • Which tools failed most this week, and why?
  • How does 1.4.1 compare with 1.4.0?
  • What do agents ask for that my server does not have?
  • Does Cursor fail more often than Claude?
  • Which tools are agents shown but never call?

It sees what you see in the dashboard and changes nothing. It sends nothing anywhere but your mcpspan.

There are two ways to add it: by address, which needs nothing installed, or as a command your agent starts.

Try it on the demo

No account needed: the live demo answers any token. In Claude Code:

sh
claude mcp add --transport http mcpspan-demo https://demo-api.mcpspan.com/mcp \  --header "Authorization: Bearer demo"

Then ask about the demo's server, Flights: what went wrong in the last day?

By address

The MCP server runs inside mcpspan itself, at /mcp on its API. Add that address to your agent, and the first time it connects it opens mcpspan in your browser: sign in, check which app is asking, and allow it. Nothing to copy.

mcpspan Cloud

The address is https://api.mcpspan.com/mcp.

AgentHow
claude.ai, Claude Desktop, the Claude appsSettings → Connectors → Browse connectors, find mcpspan, and Connect. Or Add custom connector, with the address.
ChatGPTIn its connector settings (developer mode), a new connector with the address, signing in with OAuth.
Claude Codeclaude mcp add --transport http mcpspan https://api.mcpspan.com/mcp, then /mcp in Claude Code to sign in.
CursorIn mcp.json: {"mcpServers": {"mcpspan": {"url": "https://api.mcpspan.com/mcp"}}}
VS CodeIn .vscode/mcp.json: {"servers": {"mcpspan": {"type": "http", "url": "https://api.mcpspan.com/mcp"}}}
OthersWhatever they call a remote, HTTP or Streamable HTTP server, with the address.

The apps you allowed are listed in Settings → Connected apps, where one click disconnects an app and ends its access at once.

An agent that cannot sign in with OAuth can send a read token instead (see Get a token), as a header:

sh
claude mcp add --transport http mcpspan https://api.mcpspan.com/mcp \  --header "Authorization: Bearer mcpspan_read_..."

Self-hosted

The address is your API's, the one your MCP servers report to, with /mcp: http://localhost:6271/mcp on the machine itself. Agents on that machine, such as Claude Code or Cursor, connect as above.

An app that connects from elsewhere, such as claude.ai or ChatGPT, needs that address on HTTPS and reachable from the internet, and the API told where people open your dashboard, since that is where it sends them to allow it: set MCPSPAN_DASHBOARD_URL in .env, for instance https://mcpspan.example.com.

Needs mcpspan 0.13.0 or newer.

As a command

The same tools, started by your agent with npx, reading with a read token. For agents that only start commands, or to keep it on your machine.

Get a token

In mcpspan, open Settings → Read tokens and make one. It is shown once, already filled into the lines below, ready to copy.

mcpspan Cloud

Claude Code:

sh
claude mcp add mcpspan -e MCPSPAN_READ_TOKEN=mcpspan_read_... -- npx -y mcpspan-mcp

Cursor, Claude Desktop, Windsurf and others, in their MCP settings:

json
{  "mcpServers": {    "mcpspan": {      "command": "npx",      "args": ["-y", "mcpspan-mcp"],      "env": { "MCPSPAN_READ_TOKEN": "mcpspan_read_..." }    }  }}

Self-hosted

The same, with the address your MCP servers report to:

sh
claude mcp add mcpspan \  -e MCPSPAN_READ_TOKEN=mcpspan_read_... \  -e MCPSPAN_URL=http://localhost:6271 \  -- npx -y mcpspan-mcp
json
{  "mcpServers": {    "mcpspan": {      "command": "npx",      "args": ["-y", "mcpspan-mcp"],      "env": {        "MCPSPAN_READ_TOKEN": "mcpspan_read_...",        "MCPSPAN_URL": "http://localhost:6271"      }    }  }}

Needs mcpspan 0.9.0 or newer. If the agent reaches your installation over the internet, put HTTPS in front of it: the token travels with every question.

Settings

Variable
MCPSPAN_READ_TOKENThe read token. Required.
MCPSPAN_URLYour installation's API, for self-hosted mcpspan. https://api.mcpspan.com when left out.

Needs Node 20 or newer.

Tools

Every tool only reads. Each takes the server by name or id (left out when the account has one) and a window: days back from now (7 when left out), or from and to.

ToolAnswers
list_serversThe servers the account reports on.
get_overviewCalls, failures, error rate, response times and clients.
list_toolsTools ranked by calls, errors, response time or name.
get_toolOne tool: why it failed, refused arguments, answer sizes, definition changes, repeats, and the call before each failure.
list_errorsThe latest failed calls, with the kind of failure and the message.
list_unknown_toolsTools agents asked for that the server lacks, the closest one it has, and what the agent did next.
list_clientsEach client's calls, error rate and response times.
compare_versionsThe server's releases side by side.
get_tool_listingWhat agents were shown: tools never used, and what their definitions cost.
list_sessionsRecent sessions, with failures and repeated calls.
get_sessionOne session's calls, in order.
get_where_agents_get_lostWhat came of each session, the tools agents got stuck at and what they did next; for one tool, by client.

A token can be revoked at any time under Settings → Read tokens, and an app disconnected under Settings → Connected apps; either loses access at once.

Licence

MIT

來源:packages/mcpspan-mcp/README.md,提交 4b5213f

工具

12

list_servers

List servers

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

無需輸入參數。

get_overview

Overview

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

輸入參數todaysfromclientserver

list_tools

List tools

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

輸入參數todaysfromsortlimitclientserver

get_tool

Tool details

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.

輸入參數todaysfromtool必填server

list_errors

List failed calls

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.

輸入參數todaysfromtoollimitclientserver

list_unknown_tools

List unknown tools

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.

輸入參數todaysfromserver

list_clients

List clients

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

輸入參數todaysfromserver

compare_versions

Compare versions

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.

輸入參數todaysfromclientserver

get_tool_listing

What agents are shown

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.

輸入參數todaysfromclientserver

list_sessions

List sessions

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

輸入參數todaysfromtoolwithlimitclientserver

get_where_agents_get_lost

Where agents get lost

Where agents got stuck and what they did about it. A time stuck is a failed tool call and the retries of the same tool straight after it; each ends recovered (the tool then worked, with meanRetries retries on average), wentElsewhere (the agent called something else, insteadMostOften), endedOnIt (the session stopped there, nothing for 30 minutes) or undecided (too recent to tell); looped counts those where a retry repeated the same arguments. Without a tool: every session by the worst that happened in it (clean, recovered, wentElsewhere, looped, endedOnFailure, undecided) and the tools agents got stuck at, worst first. With a tool: that tool's times stuck, as a whole and by client.

輸入參數todaysfromtoolclientserver

get_session

Session

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

輸入參數todaysfromserversession必填

版本歷史

4
  1. v0.14.0最新Nov 6, 2026
  2. v0.13.0Oct 29, 2026
  3. v0.12.0Oct 26, 2026
  4. v0.11.0Oct 25, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分