Memory (Reference) vs openFDA Scraper: adverse events, drug recalls, labels, 510(k)
Memory (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). openFDA Scraper: adverse events, drug recalls, labels, 510(k) is an MCP server published by bepolabs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-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 |  Memory (Reference) |  openFDA Scraper: adverse events, drug recalls, labels, 510(k) |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:db0c2db07a44 Forks (GitHub): 11 961 Pulls (Docker Hub): 580 504 Stars (Docker Hub): 26 Stars (GitHub): 91 970 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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) | openFDA Scraper: adverse events, drug recalls, labels, 510(k) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 970 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 580 504 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 961 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/memory) | Remote server (mcp.apify.com) |
| 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 | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 h ago, requires authentication |
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.
openFDA Scraper: adverse events, drug recalls, labels, 510(k)
Adverse events, drug recalls, labels, 510(k), as one MCP tool through Apify
How to run each
Memory (Reference) As a local MCP server: Docker image
claude mcp add --transport stdio memory -- docker run -i --rm mcp/memoryopenFDA Scraper: adverse events, drug recalls, labels, 510(k)
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only openFDA Scraper: adverse events, drug recalls, labels, 510(k) has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of openFDA Scraper: adverse events, drug recalls, labels, 510(k) 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: openFDA Scraper: adverse events, drug recalls, labels, 510(k) · 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.