io.github.jmshinhwa/datenschutz-auskunft-lint
@readystack/datenschutz-auskunft-lint
Is the io.github.jmshinhwa/datenschutz-auskunft-lint MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-30.
15 Prüfungen für Auskunftsschreiben nach Art. 15 DSGVO – samt Monatsfrist ab Eingangsdatum
alive probed 2026-11-15 · unchanged since 2026-10-30
- Run it
- npx -y @readystack/datenschutz-auskunft-lint@1.0.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- @readystack/datenschutz-auskunft-lint 1.0.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 380 tokens in Claude Opus 5.5, exact, measured 2026-10-16. With the Claude Code prefix mcp__…__ on each tool name: 434. The o200k_base estimate is 211. 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.80×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| check_dir | 142 | 79 | 37 % |
| check_text | 137 | 76 | 36 % |
| check_file | 101 | 56 | 27 % |
Compare this server with others, or with the servers that share its tool set.
Same tool set as 3 other servers
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/cron-schedule-lint · alive
- io.github.jmshinhwa/crypto-export-notice-lint · alive
- io.github.jmshinhwa/currency-minor-unit-lint · alive
- io.github.jmshinhwa/data-act-switching-lint · alive
- io.github.jmshinhwa/denchoho-sakuin-check-2026 · alive
- io.github.jmshinhwa/devicetree-config-language-pack · alive
- io.github.jmshinhwa/dienstanweisung-bewachung-lint · alive
- io.github.jmshinhwa/dividenden-quellensteuer-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.