Memory (Reference) vs Entity Enricher
Memory (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Entity Enricher is an MCP server published by entityenricher.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  Memory (Reference) |  Entity Enricher |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:db0c2db07a44 Forks (GitHub): 11 807 Pulls (Docker Hub): 558 609 Stars (Docker Hub): 26 Stars (GitHub): 91 346 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | Memory (Reference) | Entity Enricher |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 346 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 558 609 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 807 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/memory) | Remote server (entityenricher.ai/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 9 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/tot-concept/mcp-server-entity-enricher |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago, requires a key |
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)
Knowledge graph-based persistent memory system.
Entity Enricher
Multi-LLM entity enrichment: schemas, single/batch enrichment, fusion, model benchmarks.
How to run each
Memory (Reference) As a local MCP server: Docker image
claude mcp add --transport stdio memory -- docker run -i --rm mcp/memoryEntity Enricher As a remote MCP server
claude mcp add --transport http enricher https://entityenricher.ai/api/mcp/ --header "X-API-Key: <YOUR_X_API_KEY>"Requires: X-API-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Entity Enricher has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Entity Enricher publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Memory (Reference) · What it can do: Entity Enricher · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.