MCP.Market

Checkup MCP server

by yifanyifan897645·io.github.yifanyifan897645/mcp-checkup·v0.1.0·1 stars

Analyze your MCP setup: token costs, grades, duplicates, and optimization tips

B82/100grade B
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
New

1 stars56 downloads/wk

Reviews

Write one

Nobody has reviewed Checkup yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Checkup tools (5)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • analyze_servers

    Scan your MCP config and measure the token cost of every installed server. Returns tool count, total tokens, and a grade (A-F) per server.

  • analyze_tools

    Get detailed token cost breakdown for each tool in a specific MCP server. Shows per-tool grades, bloated descriptions, and optimization suggestions.

  • count_tokens

    Count the number of tokens in a piece of text. Useful for estimating context window usage.

  • find_duplicates

    Scan all MCP servers for duplicate or overlapping tool names. Helps identify redundant servers eating your context window.

  • generate_report

    Generate a comprehensive markdown health report for your MCP setup. Includes grades, token costs, duplicates, and optimization recommendations.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan9 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 167 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Checkup compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
56
more than 46% of 12,191 servers with a package

What its tools let an agent do: 4 read · 1 create

Install Checkup in Claude Code, Cursor or VS Code

Runs npx -y mcp-checkup on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-checkup -- npx -y mcp-checkup
Add to Cursor

What the publisher says

From the Checkup repository's README, as published. We do not edit it. Read it on GitHub

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.

Real examples from the community:

  • 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)

Tools

analyze_servers

Scan your MCP config and measure the token cost of every installed server. Auto-detects config files.

"Which of my MCP servers costs the most tokens?"

analyze_tools

Deep-dive into a specific server — per-tool token costs, grades, bloated descriptions, and optimization suggestions.

"Break down the token cost of my GitHub MCP server"

find_duplicates

Find duplicate tool names across your installed servers. Redundant tools waste context for no benefit.

"Do any of my MCP servers have overlapping tools?"

count_tokens

Count tokens in any text. Useful for estimating context usage.

"How many tokens is this prompt?"

generate_report

Full markdown health report: server grades (A-F), token costs, duplicates, and actionable recommendations.

"Generate a full MCP health report"

Grading System

Per-Tool Grades

Per-Server Grades

Installation

Claude Desktop / Claude Code

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

Cursor

Add to .cursor/mcp.json with the same format.

Auto-Detection

mcp-checkup automatically finds your MCP config in these locations:

  • .mcp.json (current directory)
  • Claude Desktop config (Windows/macOS/Linux)
  • .cursor/mcp.json

Or pass a custom path to any tool.

How It Compares

Use mcp-checkup first to find the problem, then decide how to fix it.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Checkup: common questions

Is Checkup MCP server safe?
Mostly: it is graded B (82/100). Read the Checkup safety report
How do I install Checkup?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Checkup need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Checkup maintained?
The last commit was 205 days ago (2026-04-13). The latest release is v0.1.0.
What can I use instead of Checkup?
Servers from other publishers that do the same job: Entroly MCP server and Token Optimizer MCP server.
How does Checkup compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Checkup

Same job from other publishers: the closest match first, then the best rated.

  • Entroly
    Context Assurance for AI agents: context engineering, AI cost optimization, verification.
    B
  • Token Optimizer
    Context-window optimization: caching, compression & smart file tools that cut tokens 60-90%.
    C

More from yifanyifan897645 →