mcpcost

io.github.jmshinhwa/green-claim-lint-empco

@readystack/green-claim-lint-empco

Is the io.github.jmshinhwa/green-claim-lint-empco MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-30.

Reads your HTML and Markdown product copy and flags the environmental claims Directive (EU) 2024/825

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

3tools
356tokens in Claude Opus 5.5
0.2 %of Claude's 200k window
0.1×the median server
96 msto initialize
4 msto list tools
Run it
npx -y @readystack/green-claim-lint-empco@1.0.4 (stdio, probed in a container with the network off)
Host
npmjs.com
Reports itself as
@readystack/green-claim-lint-empco 1.0.0
Capabilities
tools
Instructions
none
Of a 1M window
<0.1 % of a 1M context window
Count
356 tokens in Claude Opus 5.5, exact, measured 2026-10-16. With the Claude Code prefix mcp__…__ on each tool name: 401. The o200k_base estimate is 202. Counted again when the tool definitions change. Method.
Repository
https://github.com/jmshinhwa/readystack-themes
Registry
active, updated 2026-09-23 · 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.76×.

Tool≈ Claude tokenso200k estimateShare of this server
check_dir1347638 %
check_text1297336 %
check_file935326 %

Compare this server with others.

More servers

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

Servers that mention claim.

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