analyze_serversLABSCO SUMMARY
Find out what your tool list costs before the conversation starts.
Every tool definition rides along in context on each turn, and nothing in a normal client shows you the bill. This turns that into a number per server, then ranks them so you know which one to drop.
What it is
An MCP server that audits your own MCP setup. It finds your config files, measures the token cost of every installed server and tool, and grades what it finds.
What you get
- Every installed server found from your config and priced in tokens
- Per-tool token costs for one server, with the bloated descriptions called out
- Duplicate tool names found across servers
- A token count for any block of text
- A markdown health report with A-to-F grades and recommendations
Requirements
npx mcp-checkup, with no account and no key. It reads the MCP config files it auto-detects on your machine.
Setup effort
One command — npx mcp-checkup
USE CASES
01
Working out why your context fills up so fast
Scan the config and get a token cost for each installed server, ranked.
02
Deciding which server to remove
Break one server down tool by tool and see which descriptions cost the most.
03
Spotting two servers doing the same job
List tool names that appear in more than one installed server.
04
Handing a summary to the rest of the team
Produce a markdown report with per-server grades and the reasoning behind them.
05
Sizing a prompt before you paste it
Count the tokens in any text.
5 tools
Listed in project docs. Your client may show a different list.
analyze_toolsfind_duplicatescount_tokensgenerate_reportBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
npx on PATH
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx mcp-checkupMCP Clients
Claude Desktop, Claude Code, Cursor
JSON
{
"mcpServers": {
"mcp-checkup": {
"command": "npx",
"args": [
"-y",
"mcp-checkup"
]
}
}
}
