Ext Ops Panel
Open dashboard
Comparison

Memory (Reference) vs inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail

Memory (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail is an MCP server published by DanceNitra. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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
MarketplaceMemory (Reference)inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail
Docker MCP Catalog Listed
Version: sha256:db0c2db07a44
Forks (GitHub): 11 780
Pulls (Docker Hub): 554 486
Stars (Docker Hub): 26
Stars (GitHub): 91 180
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.18.0
Downloads/month (PyPI): 14 264
Downloads/week (PyPI): 2 009
Forks (GitHub): 1
Stars (GitHub): 8
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

Memory (Reference) vs inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail
FactMemory (Reference)inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)91 180 (better)8 (worse)
Pulls (Docker Hub) (differs)554 486No figure on Docker Hub
Forks (GitHub) (differs)11 780 (better)1 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (mcp/memory)On your machine (inspeximus)
Transportstdiostdio
Tools it declares (differs)9Not published
Environment variables it asks for (differs)Not published4, secrets among them: 0
Hooks it runs (differs)Not published5
Parts of the bundle (differs)Not a bundle6
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/dancenitra/inspeximus
Changes in the last 7 days (differs)03
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

Memory (Reference)

In its own words, on Docker MCP Catalog:

Knowledge graph-based persistent memory system.

inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail

In its own words, on Official MCP Registry:

Self-correcting agent memory: recall, supersede, revert, forget, GDPR erasure, audit receipts.

How to run each

Memory (Reference) As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio memory -- docker run -i --rm mcp/memory

inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio inspeximus -- uvx --from "inspeximus[mcp]" inspeximus mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Memory (Reference) publish no settings it asks for, so we do not compare settings.

What it can do: Memory (Reference) · What it can do: inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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