io.github.jmshinhwa/vvt-pruefer-art-30-dsgvo
@readystack/vvt-pruefer-art-30-dsgvo
Prüft Ihr Verzeichnis von Verarbeitungstätigkeiten in Markdown mit 12 Regeln gegen Art. 30 Abs. 1 DS
alive probed 2026-10-19
3tools
≈ 205tokens, estimate
≈ 0.1 %of Claude's 200k window
0.1×the median server
112 msto initialize
3 msto list tools
- Run it
- npx -y @readystack/vvt-pruefer-art-30-dsgvo@1.0.3 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- @readystack/vvt-pruefer-art-30-dsgvo 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-25 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| check_dir | 77 | 38 % |
| check_text | 74 | 36 % |
| check_file | 54 | 26 % |
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 Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.