dev.memnode/memnode vs MemoraEU
dev.memnode/memnode is an MCP server published by memnode.dev. Marketplaces we read that list it: 1 (Official MCP Registry). MemoraEU is an MCP server published by pquattro. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  MemoraEU | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 No figure published Not marked · First seen |
Listed Version: 0.1.6 Downloads/month (PyPI): 108 Downloads/week (PyPI): 48 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 | dev.memnode/memnode | MemoraEU |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.memnode.dev/mcp) | On your machine (memoraeu-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 4 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/pquattro/memoraeu |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 7 h ago | 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
dev.memnode/memnode
Persistent, inspectable memory for AI agents with lineage, correction, and a hosted MCP endpoint.
MemoraEU
Zero-knowledge persistent memory layer for AI agents. Encrypted client-side, hosted in France.
How to run each
dev.memnode/memnode As a remote MCP server
claude mcp add --transport http memnode https://api.memnode.dev/mcpMemoraEU As a local MCP server: PyPI package
claude mcp add --env "MEMORAEU_API_KEY=<YOUR_MEMORAEU_API_KEY>" --env "MEMORAEU_SALT=<YOUR_MEMORAEU_SALT>" --env "MEMORAEU_SECRET=<YOUR_MEMORAEU_SECRET>" --transport stdio memoraeu -- uvx memoraeu-mcpRequires: MEMORAEU_API_KEY (secret), MEMORAEU_SALT (secret), MEMORAEU_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only dev.memnode/memnode 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 dev.memnode/memnode publish no settings it asks for, so we do not compare settings.
What it can do: dev.memnode/memnode · What it can do: MemoraEU · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.