io.github.ZIZKA-AI-SL/zizkadb-mcp
ZizkaDB
Is the ZizkaDB MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-01.
Causal memory and tamper-evident audit log for AI agents: log, why, search, time travel.
alive probed 2026-11-01
13tools
3.6ktokens in Claude Opus 5.5
1.8 %of Claude's 200k window
1.4×the median server
1.2 sto initialize
8 msto list tools
- Run it
- uvx zizkadb-mcp@0.1.12 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- ZizkaDB 1.30.0
- Capabilities
- experimental, prompts, resources, tools
- Instructions
- none
- Of a 1M window
- 0.4 % of a 1M context window
- Count
- 3.6k tokens in Claude Opus 5.5, exact, measured 2026-11-01. With the Claude Code prefix mcp__…__ on each tool name: 3.8k. The o200k_base estimate is 2.1k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/ZIZKA-AI-SL/ZizkaDB
- Website
- https://db.zizka.ai
- Registry
- active, updated 2026-10-31 · 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.70×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| log_event | 520 | 305 | 15 % |
| get_context | 480 | 282 | 13 % |
| search_memory | 399 | 234 | 11 % |
| time_travel | 310 | 182 | 9 % |
| forget | 293 | 172 | 8 % |
Compare this server with others.
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.