io.github.jmshinhwa/mcp-config-audit
@readystack/mcp-config-audit
Audit one mcp.json for what an agent config gives away — inline API keys, unpinned npx launches, pla
alive probed 2026-10-14
3tools
332tokens in Claude Opus 5.5
371tokens in Claude Code
0.2 %of a 200k context window
190o200k_base estimate
99 msto initialize
2 msto list tools
- Run it
- npx -y @readystack/mcp-config-audit@1.0.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- @readystack/mcp-config-audit 1.0.0
- Capabilities
- tools
- Instructions
- none
- Claude count
- Claude Opus 5.5, measured 2026-10-14. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/jmshinhwa/readystack-themes
- Registry
- active, updated 2026-09-19 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
| Tool | Tokens (o200k) | Share of this server |
|---|---|---|
| check_dir | 76 | 40 % |
| check_text | 67 | 35 % |
| check_file | 47 | 25 % |
Same tool set as 0 other servers
These registry entries have the same tool names and the same schema sizes.
Badge and feed
[](https://mcpcost.ulehla.dev/s/io.github.jmshinhwa/mcp-config-audit)
An entry for every probe that changed the result, the tool count or the token cost: Atom feed. Add it to a feed reader or a Slack RSS app to hear when the server stops answering or its tool set grows.