io.github.4DA-Systems/4da-mcp-server vs Mimir — Persistent Memory Engine
Mimir — Persistent Memory Engine is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
io.github.4DA-Systems/4da-mcp-server is an MCP server published by 4DA-Systems. Marketplaces we read that list it: 1 (Official MCP Registry). Mimir — Persistent Memory Engine is an MCP server published by tcconnally. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-22. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 6.2.4 Downloads/month (npm): 2 373 Downloads/week (npm): 1 229 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Removed on 2026-10-20 Version: 2.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.4DA-Systems/4da-mcp-server | Mimir — Persistent Memory Engineno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-10-12 | Not published |
| Where it runs (differs) | On your machine (@4da/mcp-server) | Not stated |
| Transport (differs) | stdio | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/4da-systems/4da-mcp-server | Not stated |
| Changes in the last 7 days | 2 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Mimir — Persistent Memory Engine
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Mem0-compatible persistent memory for AI agents: write facts once, recall them semantically.
-
memra com.usememra/memra
Persistent memory for AI agents. EU-hosted, privacy-first, hybrid recall, contradiction detection.
-
memory com.humaux/memory
Persistent long-term memory for AI agents: semantic search, knowledge graph, and task canvas.
-
memdata io.github.thelabvenice/memdata
Persistent memory for AI agents. Store context, retrieve it semantically.
-
mem0 io.github.mem0ai/mem0
Persistent memory for AI agents: add, search, update, and delete long-term memories.
-
memnode dev.memnode/memnode
Persistent, inspectable memory for AI agents with lineage, correction, and a hosted MCP endpoint.
What each says it does
io.github.4DA-Systems/4da-mcp-server
Upgrade intelligence for AI agents: what an upgrade changes, where it touches your code, CVE scans.
Mimir — Persistent Memory Engine
Persistent memory for AI agents. 36+ MCP tools: encryption, decay, hybrid search, knowledge graph.
How to run each
io.github.4DA-Systems/4da-mcp-server As a local MCP server: npm package
claude mcp add --transport stdio 4da-mcp-server -- npx -y @4da/mcp-server
Mimir — Persistent Memory Engine
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: io.github.4DA-Systems/4da-mcp-server · What it can do: Mimir — Persistent Memory Engine · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.