io.github.CloudCorpRecords/mcpvet

mcpvet

Is the io.github.CloudCorpRecords/mcpvet MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-26.

Vetting for MCP servers and skills: capabilities, configs, mismatches, typosquats, probe parity.

alive probed 2026-11-14 · unchanged since 2026-10-26

3tools

946tokens in Claude Opus 5.5

0.5 %of Claude's 200k window

0.4×the median server

345 msto initialize

7 msto list tools

Run it: npx -y @reneturcios/mcpvet@0.2.1 (stdio, probed in a container with the network off)
Host: npmjs.com
Reports itself as: mcpvet 0.2.1
Capabilities: tools
Instructions: none
Of a 1M window: <0.1 % of a 1M context window
Count: 946 tokens in Claude Opus 5.5, exact, measured 2026-10-26. With the Claude Code prefix mcp__…__ on each tool name: 976. The o200k_base estimate is 542. Counted again when the tool definitions change. Method.
Repository: https://github.com/CloudCorpRecords/mcpvet
Registry: active, updated 2026-10-26 · registry entry
Changes: 2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.75×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
probe_server	410	235	43 %
vet_path	286	164	30 %
vet_package	250	143	26 %

Other registry entries on npmjs.com, the ones next to this name; all of them.

Servers that mention mcpvet or capabilities or mismatches.

We add a row when the result changes. A server with no change keeps its last row.

Probed	Result	Init	Tools	Claude	o200k
2026-10-26 07:00	alive	305 ms	3	946	542
2026-10-24 06:30	alive	345 ms	2		307

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.