io.github.jmshinhwa/romu-hozon-kikan-lint-jp
@readystack/romu-hozon-kikan-lint-jp
Is the io.github.jmshinhwa/romu-hozon-kikan-lint-jp MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-30.
法定帳簿の保存期間を文書保存期間表で検査 — 労基法109条・安衛則51条・石綿則41条・雇用保険法施行規則143条・健保則34条(20 rules)
alive probed 2026-11-15 · unchanged since 2026-10-30
- Run it
- npx -y @readystack/romu-hozon-kikan-lint-jp@1.0.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- @readystack/romu-hozon-kikan-lint-jp 1.0.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 332 tokens in Claude Opus 5.5, exact, measured 2026-10-16. With the Claude Code prefix mcp__…__ on each tool name: 395. The o200k_base estimate is 193. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/jmshinhwa/readystack-themes
- Registry
- active, updated 2026-09-26 · 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.72×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| check_dir | 126 | 73 | 38 % |
| check_text | 120 | 70 | 36 % |
| check_file | 86 | 50 | 26 % |
Compare this server with others, or with the servers that share its tool set.
Same tool set as 1 other server
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.
- io.github.jmshinhwa/rechnung-pflichtangaben-lint-de · alive
- io.github.jmshinhwa/reisekosten-pruefer-2026 · alive
- io.github.jmshinhwa/renpy-release-gate · alive
- io.github.jmshinhwa/robots-txt-ai-crawler-audit · alive
- io.github.jmshinhwa/runtime-eol-deploy-block-audit · alive
- io.github.jmshinhwa/saft-pt-atcud-lint · alive
- io.github.jmshinhwa/security-headers-csp-lint · alive
- io.github.jmshinhwa/security-txt-cra-lint · alive
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.