io.github.mikhailbovt/contextdb-memory
ContextDB Memory
Is the ContextDB Memory MCP server down? Yes. It has given no valid answer since 2026-10-31: not found.
Local-first durable AI memory with policy-bound recall and a typed project graph.
not found down since 2026-10-31 · probed 2026-11-14 · unchanged since 2026-11-07
download answered HTTP 404
- Bundle
- https://github.com/mikhailbovt/ContextDB-Codex/releases/download/v0.6.0-alpha.3/contextdb-memory-0.6.0-alpha.3-windows-x86_64.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/mikhailbovt/ContextDB-Codex
- Registry
- active, updated 2026-08-25 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- nMEMORY io.github.menot-you/n-memory · crashed on start
- Lanes io.github.mfmatozza/lanes · needs env
- PLwC Personal io.github.mhoedt-ai/plwc-gateway · crashed on start
- gadak io.github.midagedev/gadak · crashed on start
- Favro io.github.mmedum/favro-mcp · needs network
- io.github.mmedum/gitlab-mcp · alive
- io.github.mmedum/google-calendar-mcp · alive
- io.github.mmedum/google-chat-mcp · alive
Servers that mention contextdb or memory.
- ContextDB Customer Memory io.github.atomsai/contextdb-memory · needs auth
- AgentPlaybooks ai.agentplaybooks/agentplaybooks · needs auth
- Ambix ai.ambix/ambix · needs auth
- Atlaso Memory ai.atlaso/mcp · needs auth
- ai.butlerbrain/mcp · needs auth
- Contexel ai.contexel/contexel · needs auth
- Daystruct ai.daystruct.api/daystruct · alive
- DoneThat ai.donethat/donethat · needs auth
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
- No valid answer since 2026-10-31, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.