Mcp Checkup
Exposes five tools that analyze your MCP configuration to surface hidden token costs. Points at your Claude Desktop or Cursor config files, counts tokens consumed by each server and tool schema, assigns letter grades based on context window impact, and flags duplicate tool names across servers. Useful when you notice sluggish responses or hit context limits and want to see which MCP servers are burning tokens before you type anything. The analyze_tools command breaks down per-tool costs with optimization suggestions, while generate_report produces a markdown health check with actionable recommendations for trimming bloat.
- tools
- 5
- transport
- STDIO
- last updated
- Mar 30, 2026
Tools
5 toolsPublic tool metadata for what this MCP can expose to an agent.
analyze_serversScan your MCP config and measure the token cost of every installed server. Auto-detects config files.
Scan your MCP config and measure the token cost of every installed server. Auto-detects config files.
No parameter schema in public metadata yet.
analyze_toolsDeep-dive into a specific server — per-tool token costs, grades, bloated descriptions, and optimization suggestions.
Deep-dive into a specific server — per-tool token costs, grades, bloated descriptions, and optimization suggestions.
No parameter schema in public metadata yet.
find_duplicatesFind duplicate tool names across your installed servers. Redundant tools waste context for no benefit.
Find duplicate tool names across your installed servers. Redundant tools waste context for no benefit.
No parameter schema in public metadata yet.
count_tokensCount tokens in any text. Useful for estimating context usage.
Count tokens in any text. Useful for estimating context usage.
No parameter schema in public metadata yet.
generate_reportFull markdown health report: server grades (A-F), token costs, duplicates, and actionable recommendations.
Full markdown health report: server grades (A-F), token costs, duplicates, and actionable recommendations.
No parameter schema in public metadata yet.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageReadme
mcp-checkup
Your MCP servers are eating your context window. Find out how much.
mcp-checkup is an MCP server that analyzes your MCP setup — measuring the token cost of every installed server and tool, finding duplicates, grading efficiency, and generating optimization reports.
Quick Start
npx mcp-checkup
Then ask your AI assistant:
"Run an MCP health check on my setup"
"How many tokens are my MCP servers using?"
"Generate an MCP health report"
Why?
Every MCP tool costs 550–1,400 tokens just for its schema. A server with 50 tools can eat 30,000+ tokens before you type anything. Most developers have no idea how much context window their MCP servers are consuming.
Details
- Repository
- github.com/yifanyifan897645/mcp-checkup
- Package
mcp-checkup- Transport
- STDIO
- Registry
- MCP registry, active