Mnemoverse Memory vs io.github.cdeust/hypermnesia-mcp
Mnemoverse Memory is a plugin bundle for AI coding tools published by Mnemoverse. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.cdeust/hypermnesia-mcp is an MCP server published by cdeust. Marketplaces we read that list it: 3 (Official MCP Registry, PyPI (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-11-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.cdeust/hypermnesia-mcp | |
|---|---|---|
| Community marketplace hashgraph-online/awesome-codex-plugins | Listed Version: 1.0.4 Forks (GitHub): 491 Stars (GitHub): 1 576 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 4.24.0 Downloads/month (PyPI): 1 993 Downloads/week (PyPI): 135 Forks (GitHub): 16 Stars (GitHub): 77 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 4.24.0 Downloads/month (PyPI): 1 993 Downloads/week (PyPI): 135 Forks (GitHub): 16 Stars (GitHub): 77 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 | Mnemoverse Memory | io.github.cdeust/hypermnesia-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 1 576 (better) | 77 (worse) |
| Forks (GitHub) (differs) | 491 (better) | 16 (worse) |
| Last release (differs) | Not published | 2026-11-11 |
| Where it runs (differs) | Remote server (mcp.mnemoverse.com/mcp) | On your machine (hypermnesia-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 0 |
| Hooks it runs (differs) | Not published | 12 |
| Parts of the bundle (differs) | 8 | 26 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/hashgraph-online/awesome-codex-plugins | github.com/cdeust/cortex |
| Changes in the last 7 days (differs) | 2 | 3 |
| First seen (differs) | 2026-11-14 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 7 h ago, requires authentication | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Mnemoverse Memory
Hosted AI agent memory that learns from outcomes, over remote MCP with OAuth sign-in: tell it a recalled memory helped or misled and it re-ranks what comes back next, with shared rooms for multi-agent work.
io.github.cdeust/hypermnesia-mcp
Persistent memory for AI agents — 36 cited neuroscience mechanisms, local-first, hybrid retrieval.
How to run each
Mnemoverse Memory As a Codex plugin
codex plugin marketplace add hashgraph-online/awesome-codex-pluginsio.github.cdeust/hypermnesia-mcp As a local MCP server: PyPI package
claude mcp add --transport stdio hypermnesia-mcp -- uvx hypermnesia-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Mnemoverse Memory has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Mnemoverse Memory publish no settings it asks for, so we do not compare settings.
What it can do: Mnemoverse Memory · What it can do: io.github.cdeust/hypermnesia-mcp · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.