Check and improve the contract quality of any MCP server — for humans, agents, and platforms.
Most MCP servers are built with only one audience in mind (usually human developers reading a README). But a successful MCP server needs to satisfy three audiences simultaneously:
MCP Doctor checks all six dimensions of "contract quality" and gives you actionable recommendations.
pip install mcp-doctor
mcp-doctor check /path/to/your-mcp-server
| Dimension | Question |
|---|---|
| Task Clarity | Is the server's purpose immediately clear? |
| Trust & Safety | Are side effects, permissions, and safety boundaries declared? |
| Interface Quality | Are tools well-named, well-described, and well-typed? |
| Token Efficiency | Will tool responses fit an agent's context budget? |
| Install Friction | How fast can someone go from discovery to first use? |
| Cross-platform Readiness | Is metadata complete for Registry, Smithery, PulseMCP, Glama? |
# Terminal output (default, rule-based)
mcp-doctor check /path/to/server
# JSON output (for CI/CD)
mcp-doctor check /path/to/server --format json
# Markdown output (for README badges or reports)
mcp-doctor check /path/to/server --format markdown
# AI-enhanced evaluation (requires OPENAI_API_KEY)
mcp-doctor check /path/to/server --mode ai
# AI mode with a specific model
mcp-doctor check /path/to/server --mode ai --model gpt-4o
MCP Doctor is also an MCP server, so AI agents can use it to check other servers:
{
"mcpServers": {
"mcp-doctor": {
"command": "python",
"args": ["-m", "mcp_doctor.mcp_server"]
}
}
}
Tools:
check_server(path, format, mode, model) — Run all 6 checks. Use mode="ai" for LLM-enhanced review.list_dimensions() — List what MCP Doctor evaluatesOne-liner (paste this to your AI agent):
Install mcp-doctor (
pip install mcp-doctor) and add it to your MCP config with commandpython -m mcp_doctor.mcp_server. Then use thecheck_servertool to check any MCP server's quality.
Step by step:
pip install mcp-doctor{
"mcpServers": {
"mcp-doctor": {
"command": "python",
"args": ["-m", "mcp_doctor.mcp_server"]
}
}
}
check_server tool with a path to any MCP server repomcp-doctor check /path/to/server --format jsonAgent workflow: check server -> review scores -> identify lowest dimensions -> follow recommendations
Each dimension is scored 0-100 and graded A/B/C/D:
MCP Doctor is based on the Contract Quality Framework — the principle that a successful MCP product's promises (what it does, what it costs, what risks it carries) should be equally parseable by platforms, humans, and agents.
The framework draws from:
| Mode | Flag | Deterministic | Network | API Key |
|---|---|---|---|---|
| Rule-based (default) | --mode rule | Yes | No | No |
| AI-enhanced | --mode ai | No | Yes (LLM API) | OPENAI_API_KEY |
Rule-based mode is fully offline and deterministic. No network calls, no LLM, no API keys needed.
AI mode sends a metadata summary (server name, tool definitions, README preview, rule-based scores) to an OpenAI-compatible API for qualitative review. No source code is sent. Reports include model name and version for reproducibility.
AI mode supports any OpenAI-compatible provider:
OPENAI_API_KEY — API key (required for AI mode)OPENAI_BASE_URL — Custom endpoint (for Ollama, vLLM, LM Studio, Azure, etc.)MCP_DOCTOR_MODEL — Model name (default: gpt-4o-mini)Install AI support: pip install mcp-doctor[ai]
MCP Doctor is read-only. It never modifies, deletes, or creates files.
| What it accesses | Why |
|---|---|
server.json | Parse MCP metadata |
README.md | Check documentation quality |
LICENSE | Verify license presence |
*.py, *.json in src/ | Detect tool definitions |
All MCP tools have readOnlyHint: true and destructiveHint: false annotations.
Found a bug? Have a suggestion? We'd love to hear from you:
gh CLI):
gh issue create --repo Jiansen/mcp-doctor --title "Bug: ..." --body "..."
If you're an agent, include the JSON output of check_server in your report for context.
git clone https://github.com/Jiansen/mcp-doctor.git
cd mcp-doctor
pip install -e ".[dev,ai]"
ruff check src/ tests/
pytest tests/ -v
If MCP Doctor helped you improve your server, consider giving it a star on GitHub — it helps others discover the tool.
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx mcp-doctorMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-jiansen-mcp-doctor": {
"command": "uvx",
"args": [
"mcp-doctor"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencemcp-doctorpypiMCP Doctor works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.