Memory (Reference) vs DataPulse
Memory (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). DataPulse is an MCP server published by r3dz4r. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-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 |  Memory (Reference) |  DataPulse |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:db0c2db07a44 Forks (GitHub): 11 790 Pulls (Docker Hub): 555 825 Stars (Docker Hub): 26 Stars (GitHub): 91 268 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.55.19 Forks (GitHub): 0 Stars (GitHub): 2 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) | DataPulse |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 268 (better) | 2 (worse) |
| Pulls (Docker Hub) (differs) | 555 825 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 790 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (mcp/memory) | Remote server (mcp.data-pulse.my/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/r3dz4r/datapulse-my |
| Changes in the last 7 days (differs) | 0 | 15 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 h ago |
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.
DataPulse
Read-only discovery for 440 Malaysian public datasets with freshness, licence, and provenance.
How to run each
Memory (Reference) As a local MCP server: Docker image
claude mcp add --transport stdio memory -- docker run -i --rm mcp/memoryDataPulse As a remote MCP server
claude mcp add --transport http datapulse-my https://mcp.data-pulse.my/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only DataPulse has a remote endpoint we check. How we check endpoints
Tools each declares
Only Memory (Reference) has
add_observationscreate_entitiescreate_relationsdelete_entitiesdelete_observationsdelete_relationsopen_nodesread_graphsearch_nodes
Only DataPulse has
check_reconciliationfind_anomaliesfind_by_licencefind_deterioratingfind_recoveringfind_schema_driftfind_stalefind_unreliableget_data_passportget_datasetget_evidenceget_freshness_summary
Show the remaining 7
get_provenancesearch_datasetstrust_verdictusage_summaryverify_attestationverify_datasetverify_evidence
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (DataPulse as of 2026-10-15). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Memory (Reference) · What it can do: DataPulse · 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.