io.github.jmshinhwa/firestore-rules-guard
@readystack/firestore-rules-guard
Audits firestore.rules and storage.rules for public access, expired test-mode dates and missing owne
alive probed 2026-10-17
3tools
326tokens in Claude Opus 5.5
0.2 %of Claude's 200k window
0.1×the median server
38 msto initialize
2 msto list tools
- Run it
- npx -y @readystack/firestore-rules-guard@1.0.4 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- @readystack/firestore-rules-guard 1.0.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 326 tokens in Claude Opus 5.5, exact, measured 2026-10-17. With the Claude Code prefix mcp__…__ on each tool name: 368. The o200k_base estimate is 178. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/jmshinhwa/readystack-themes
- Registry
- active, updated 2026-09-23 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.83×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| check_dir | 125 | 68 | 38 % |
| check_text | 119 | 65 | 37 % |
| check_file | 82 | 45 | 25 % |
Same tool set as 2 other servers
These registry entries have the same tool names and the same schema sizes.
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
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
- The server answers initialize and tools/list. Nothing to fix.