mcpcost

io.github.jmshinhwa/cloud-manifest-audit-kit

@readystack/cloud-manifest-audit-kit

Is the io.github.jmshinhwa/cloud-manifest-audit-kit MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-30.

For platform engineers on AKS: 28 rules naming every removed apiVersion, literal credential and :lat

alive probed 2026-11-15 · unchanged since 2026-10-30

3tools
374tokens in Claude Opus 5.5
0.2 %of Claude's 200k window
0.1×the median server
75 msto initialize
2 msto list tools
Run it
npx -y @readystack/cloud-manifest-audit-kit@0.1.1 (stdio, probed in a container with the network off)
Host
npmjs.com
Reports itself as
@readystack/cloud-manifest-audit-kit 1.0.0
Capabilities
tools
Instructions
none
Of a 1M window
<0.1 % of a 1M context window
Count
374 tokens in Claude Opus 5.5, exact, measured 2026-10-16. With the Claude Code prefix mcp__…__ on each tool name: 428. The o200k_base estimate is 211. Counted again when the tool definitions change. Method.
Repository
https://github.com/jmshinhwa/readystack-themes
Registry
active, updated 2026-09-18 · registry entry

Most expensive tools

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

Tool≈ Claude tokenso200k estimateShare of this server
check_dir1478339 %
check_text1317435 %
check_file965426 %

Compare this server with others, or with the servers that share its tool set.

Same tool set as 2 other servers

These registry entries have the same tool names and the same schema sizes.

More servers

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

Servers that mention manifest.

Badge for the README

mcpcost: alive

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

Atom feed

A mail when this server changes

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

For the publisher