bench
Benchmark response latency for all configured MCP servers
LABSCO SUMMARY
It examines the machine it is installed on rather than a target you name: no tool here takes an argument.
That makes it a sweep and not a probe — you cannot point it at a named server, and doctor is the single call that covers connectivity, configuration security and latency at once. The security audit is the part that is hard to get elsewhere, because it reads the configuration files themselves for secrets written inline and for tokens passed as command arguments, where a process listing exposes them. The handshake in scan is a real JSON-RPC exchange rather than a reachability check, so a server that starts but never completes the handshake shows up as broken rather than fine.
What it is
A diagnostic for your own MCP installation: it discovers the server configurations present on the machine and reports connectivity, configuration security and response latency for them.
What you get
- scan discovers the MCP server configs and tests each connection with a JSON-RPC handshake, which separates a server that is misconfigured from one that is merely absent.
- security audits those same configs for hardcoded secrets, tokens passed in args and shell injection patterns — properties of how a server was wired up rather than of the server itself.
- bench measures response latency across the configured servers, so a slow session can be traced to a specific one.
- doctor runs the connection scan, the security audit and the latency benchmark together in a single call.
Requirements
MCP server configurations already present on the machine the server runs on. No account, no key, and no arguments — every tool operates on whatever it discovers.
Setup effort
One command — npx @wigu/mcp-doctor
USE CASES
01
Finding out why a client shows no tools
Discover which server configs are actually present and handshake each one, so a broken entry separates from a missing entry.
02
Auditing the credentials sitting in your MCP configs
Read the configuration files for secrets written inline and tokens handed over as command arguments, where anything reading the process list can see them.
03
Tracking down which server is slowing a session
Time the responses across everything configured, then confirm the slow one is connecting properly rather than retrying.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
doctor
Run all checks at once: scan connections, audit security, and benchmark latency for all configured MCP servers
scan
Discover all MCP server configs and test their connections via JSON-RPC handshake
security
Audit all MCP server configs for security issues like hardcoded secrets, tokens in args, and shell injection patterns
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-doctor": {
"command": "npx",
"args": [
"@wigu/mcp-doctor"
]
}
}
}npx
TERMINAL
npx @wigu/mcp-doctor
