mcpspan
Every tool call, resource read, and prompt get an agent makes on your MCP server lands in mcpspan, with the client that asked, the response time, and the reason for any failure. One line added at startup sends them, with SDKs for eight languages or a proxy that wraps any server without touching its code. The overview charts calls, error rate, and median and 95th-percentile response time per tool, and failures are told apart as crashed handlers, reported errors, refused arguments, and tools an agent asked for that the server does not have. Sessions replay each connection step by step, mark repeated calls, and show what the agent did after every failure: retried, tried something else, or gave up. Release reports set each server version against the one before it, and client versions show whether a client's newest release gets its arguments refused more often. A tool-definition view shows what the tool list costs in tokens each session and which tools agents never call. Alerts go to Slack, Discord, or any webhook, and read tokens let an MCP client such as Claude Code answer questions about the numbers. Anything you can see exports as CSV or NDJSON, calls forward to OpenTelemetry, and README badges show usage. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Deploy