io.github.alptekin/evolutiondb-memory
EvolutionDB Long-Term Memory
Is the EvolutionDB Long-Term Memory MCP server down? Yes. It has given no valid answer since 2026-10-18: not found.
Persistent long-term memory for Claude Desktop / Claude Code, backed by EvolutionDB.
not found down since 2026-10-18 · probed 2026-11-14 · unchanged since 2026-11-01
error: No solution found when resolving dependencies cause: Because mcp-server-evolutiondb was not found in the package registry and you require mcp-server-ev
- Run it
- uvx mcp-server-evolutiondb@1.17.0 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/alptekin/evolutiondb
- Registry
- active, updated 2026-06-22 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- Deputy io.github.alimohammadiamirhossein/deputy · alive
- Almega io.github.almega-ai/almega-mcp · needs mcp<2
- Joplin MCP Server io.github.alondmnt/joplin-mcp · alive
- RogueGPT io.github.aloth/roguegpt · needs args
- AI Workbench MCP io.github.alptugharun/ai-workbench-mcp · alive
- io.github.altrsoftware/altr-mcp-server · alive
- Luma Events io.github.alx1p/luma-mcp · alive
- Atlassian Attachments io.github.alyiox/mcp-atlassian-attachments · alive
Servers that mention memory or long.
- 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
- ai.dataecho/mcp · 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
- No valid answer since 2026-10-18, 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.