openFDA Scraper: adverse events, drug recalls, labels, 510(k) vs io.github.mims-harvard/tooluniverse
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). io.github.mims-harvard/tooluniverse is an MCP server published by mims-harvard. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-11-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 |  openFDA Scraper: adverse events, drug recalls, labels, 510(k) |  io.github.mims-harvard/tooluniverse |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.5.10 Downloads/month (PyPI): 40 535 Downloads/week (PyPI): 14 741 Forks (GitHub): 277 Stars (GitHub): 1 789 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 | openFDA Scraper: adverse events, drug recalls, labels, 510(k) | io.github.mims-harvard/tooluniverse |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 1 789 |
| Forks (GitHub) (differs) | No figure on GitHub | 277 |
| Last release (differs) | Not published | 2026-11-14 |
| Where it runs (differs) | Remote server (mcp.apify.com) | On your machine (tooluniverse) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 17, secrets among them: 16 |
| Hooks it runs (differs) | Not published | 2 |
| Parts of the bundle (differs) | Not a bundle | 174 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | Not stated | github.com/mims-harvard/tooluniverse |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-11-12 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 h ago, requires authentication | no remote endpoint we check |
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
openFDA Scraper: adverse events, drug recalls, labels, 510(k)
Adverse events, drug recalls, labels, 510(k), as one MCP tool through Apify
io.github.mims-harvard/tooluniverse
2,700+ scientific tools for AI scientists: life science, research, literature, and more.
How to run each
openFDA 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
io.github.mims-harvard/tooluniverse As a local MCP server: PyPI package
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "AZURE_OPENAI_API_KEY=<YOUR_AZURE_OPENAI_API_KEY>" --env "BIOGRID_API_KEY=<YOUR_BIOGRID_API_KEY>" --env "BRENDA_PASSWORD=<YOUR_BRENDA_PASSWORD>" --env "DISGENET_API_KEY=<YOUR_DISGENET_API_KEY>" --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "HF_TOKEN=<YOUR_HF_TOKEN>" --env "NCBI_API_KEY=<YOUR_NCBI_API_KEY>" --env "NVIDIA_API_KEY=<YOUR_NVIDIA_API_KEY>" --env "OMIM_API_KEY=<YOUR_OMIM_API_KEY>" --env "ONCOKB_API_TOKEN=<YOUR_ONCOKB_API_TOKEN>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "OPENROUTER_API_KEY=<YOUR_OPENROUTER_API_KEY>" --env "SEMANTIC_SCHOLAR_API_KEY=<YOUR_SEMANTIC_SCHOLAR_API_KEY>" --env "UMLS_API_KEY=<YOUR_UMLS_API_KEY>" --env "USPTO_API_KEY=<YOUR_USPTO_API_KEY>" --transport stdio tooluniverse -- uvx tooluniverse tooluniverse-smcp-stdio --compact-modeRequires: ANTHROPIC_API_KEY (secret), AZURE_OPENAI_API_KEY (secret), BIOGRID_API_KEY (secret), BRENDA_PASSWORD (secret), DISGENET_API_KEY (secret), GEMINI_API_KEY (secret), HF_TOKEN (secret), NCBI_API_KEY (secret), NVIDIA_API_KEY (secret), OMIM_API_KEY (secret), ONCOKB_API_TOKEN (secret), OPENAI_API_KEY (secret), OPENROUTER_API_KEY (secret), SEMANTIC_SCHOLAR_API_KEY (secret), UMLS_API_KEY (secret), USPTO_API_KEY (secret)
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
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of openFDA Scraper: adverse events, drug recalls, labels, 510(k) publish no settings it asks for, so we do not compare settings.
What it can do: openFDA Scraper: adverse events, drug recalls, labels, 510(k) · What it can do: io.github.mims-harvard/tooluniverse · 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.