io.github.jmshinhwa/security-txt-cra-lint
@readystack/security-txt-cra-lint
13 rules that decide whether a vulnerability report ever reaches you
alive probed 2026-10-15
3tools
362tokens in Claude Opus 5.5
407tokens in Claude Code
0.2 %of a 200k context window
208o200k_base estimate
115 msto initialize
38 msto list tools
- Run it
- npx -y @readystack/security-txt-cra-lint@1.0.7 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- @readystack/security-txt-cra-lint 1.0.0
- Capabilities
- tools
- Instructions
- none
- Claude count
- Claude Opus 5.5, measured 2026-10-15. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/jmshinhwa/readystack-themes
- Registry
- active, updated 2026-09-26 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
| Tool | Tokens (o200k) | Share of this server |
|---|---|---|
| check_dir | 78 | 38 % |
| check_text | 75 | 36 % |
| check_file | 55 | 26 % |
Same tool set as 1 other server
These registry entries have the same tool names and the same schema sizes.
- io.github.jmshinhwa/eu-health-claim-lint npmjs.com
- io.github.jmshinhwa/firmware-release-gate npmjs.com
Badge and feed
[](https://mcpcost.ulehla.dev/s/io.github.jmshinhwa/security-txt-cra-lint)
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.