mcp-doctor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scanB | Discover all MCP server configs and test their connections via JSON-RPC handshake |
| securityA | Audit all MCP server configs for security issues like hardcoded secrets, tokens in args, and shell injection patterns |
| benchA | Benchmark response latency for all configured MCP servers |
| doctorA | Run all checks at once: scan connections, audit security, and benchmark latency for all configured MCP servers |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: bench focuses on latency, scan on discovery and connection testing, security on vulnerability audit, and doctor runs all checks combined. No overlap or ambiguity.
All tool names are single, lowercase words (bench, doctor, scan, security), following a consistent and predictable naming pattern. No mixing of conventions.
With 4 tools, the set is well-scoped for a diagnostic server. Each tool addresses a core need (benchmarking, scanning, security, all-in-one) without being sparse or excessive.
The tool surface covers the essential diagnostic operations: connection testing, latency benchmarking, security auditing, and a combined run. No obvious gaps for the stated purpose.