mcpcost

io.github.jmshinhwa/accessibility-statement-lint

@readystack/accessibility-statement-lint

Checks the accessibility statement you already published against the EU model statement and its two

alive probed 2026-10-19

3tools
≈ 199tokens, estimate
≈ <0.1 %of Claude's 200k window
0.1×the median server
125 msto initialize
4 msto list tools
Run it
npx -y @readystack/accessibility-statement-lint@1.0.2 (stdio, probed in a container with the network off)
Host
npmjs.com
Reports itself as
@readystack/accessibility-statement-lint 1.0.0
Capabilities
tools
Instructions
none
Of a 1M window
≈ <0.1 % of a 1M context window, estimate
Claude count
The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
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

Estimates with the o200k_base tokenizer.

Toolo200k estimateShare of this server
check_dir7940 %
check_text7035 %
check_file5025 %

Same tool set as 2 other servers

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

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