MCP Checkup MCP Server

MCP server that analyzes your MCP setup: token costs, bloated schemas, duplicate tools, and optimization tips

Local serverstdio

What is the MCP Checkup MCP server?

MCP server that analyzes your MCP setup: token costs, bloated schemas, duplicate tools, and optimization tips. The mcp checkup mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

Your MCP servers are eating your context window. Find out how much.

  • Adding GitHub MCP increased one user's token usage from 34K to 80K (source)
  • One developer found 67,000 tokens consumed by just 4 servers before any conversation (source)
  • Context7 (240K weekly downloads) has tool descriptions costing 3x more tokens than necessary (source)

Adding it to your client

mcp-checkup on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Its toolset

Everything the assistant can do here goes through one of these:

  • analyze_servers — Scan your MCP config and measure the token cost of every installed server. Auto-detects config files
  • analyze_tools — Deep-dive into a specific server — per-tool token costs, grades, bloated descriptions, and optimization suggestions
  • find_duplicates — Find duplicate tool names across your installed servers. Redundant tools waste context for no benefit
  • count_tokens — Count tokens in any text. Useful for estimating context usage
  • generate_report — Full markdown health report: server grades (A-F), token costs, duplicates, and actionable recommendations
  • Cursor — The Cursor tool exposed by this server

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp checkup mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Checkup's toolset — analyze_servers, analyze_tools, find_duplicates and 3 more — is a fair guide to whether it matches your workflow. It is maintained by yifanyifan897645; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
analyze_serversScan your MCP config and measure the token cost of every installed server. Auto-detects config files.
analyze_toolsDeep-dive into a specific server — per-tool token costs, grades, bloated descriptions, and optimization suggestions.
find_duplicatesFind duplicate tool names across your installed servers. Redundant tools waste context for no benefit.
count_tokensCount tokens in any text. Useful for estimating context usage.
generate_reportFull markdown health report: server grades (A-F), token costs, duplicates, and actionable recommendations.
CursorThe Cursor tool exposed by this server.

How to install the MCP Checkup MCP server

{
  "mcpServers": {
    "checkup": {
      "command": "npx",
      "args": ["-y", "mcp-checkup"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use MCP Checkup to analyze servers.
  • Use MCP Checkup to analyze tools.
  • Use MCP Checkup to find duplicates.

Frequently asked questions

It connects MCP Checkup to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (analyze_servers, analyze_tools, find_duplicates, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Checkup directly.