Ext Ops Panel
Open dashboard
Comparison

Synapse Layer — Zero-Knowledge Memory vs io.github.cdeust/hypermnesia-mcp

Synapse Layer — Zero-Knowledge Memory is an MCP server published by SynapseLayer. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.cdeust/hypermnesia-mcp is an MCP server published by cdeust. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. 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

Where each is published
MarketplaceSynapse Layer — Zero-Knowledge Memoryio.github.cdeust/hypermnesia-mcp
Official MCP Registry Listed, marked deprecated
Version: 1.0.7
Downloads/month (PyPI): 236
Downloads/week (PyPI): 28
Forks (GitHub): 5
Stars (GitHub): 13
Not marked · First seen
Listed
Version: 4.23.5
Downloads/month (PyPI): 1 993
Downloads/week (PyPI): 133
Forks (GitHub): 14
Stars (GitHub): 75
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

Synapse Layer — Zero-Knowledge Memory vs io.github.cdeust/hypermnesia-mcp
FactSynapse Layer — Zero-Knowledge Memoryio.github.cdeust/hypermnesia-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)13 (worse)75 (better)
Forks (GitHub) (differs)5 (worse)14 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (synapse-layer)On your machine (hypermnesia-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 13, secrets among them: 0
Hooks it runs (differs)Not published12
Parts of the bundle (differs)Not a bundle26
Licence (differs)Not statedMIT
Repository (differs)github.com/synapselayer/synapse-layergithub.com/cdeust/cortex
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11

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

Synapse Layer — Zero-Knowledge Memory

In its own words, on Official MCP Registry:

Zero-Knowledge Context™ & Neural Handover™ for AI Agents. The Trust Layer for AI Memory.

io.github.cdeust/hypermnesia-mcp

In its own words, on Official MCP Registry:

Persistent memory for AI agents — 36 cited neuroscience mechanisms, local-first, hybrid retrieval.

How to run each

Synapse Layer — Zero-Knowledge Memory As a local MCP server: PyPI package

Claude Code
claude mcp add --env "SYNAPSE_ENCRYPTION_KEY=<YOUR_SYNAPSE_ENCRYPTION_KEY>" --transport stdio synapse-secure-memory -- uvx synapse-layer

Requires: SYNAPSE_ENCRYPTION_KEY (secret)

io.github.cdeust/hypermnesia-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio hypermnesia-mcp -- uvx hypermnesia-mcp

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

Only Synapse Layer — Zero-Knowledge Memory asks for

  • LOG_LEVEL
  • SYNAPSE_AGENT_ID
  • SYNAPSE_ENCRYPTION_KEY (secret)
  • SYNAPSE_PRIVACY_EPSILON

Only io.github.cdeust/hypermnesia-mcp asks for

  • CORTEX_MEMORY_AP_ENABLED
  • CORTEX_RUNTIME
  • DATABASE_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Synapse Layer — Zero-Knowledge Memory · What it can do: io.github.cdeust/hypermnesia-mcp · 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.

Where the data comes from: how the catalog is built