Ext Ops Panel
Open dashboard
Comparison

Fetch (Reference) vs biomedmcp

Fetch (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 2 (Docker MCP Catalog, PyPI (MCP servers)). biomedmcp is an MCP server published by unibio-intelligence. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
MarketplaceFetch (Reference)biomedmcp
Docker MCP Catalog Listed
Version: sha256:1a7a0996a565
Forks (GitHub): 11 931
Pulls (Docker Hub): 1 977 455
Stars (Docker Hub): 58
Stars (GitHub): 91 873
Not marked · First seen
Not listed
PyPI (MCP servers) Listed
Version: 2026.11.4
Downloads/month (PyPI): 506 506
Downloads/week (PyPI): 288 522
Forks (GitHub): 11 931
Stars (GitHub): 91 873
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.6
Forks (GitHub): 0
Stars (GitHub): 1
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

Fetch (Reference) vs biomedmcp
FactFetch (Reference)biomedmcp
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)91 873 (better)1 (worse)
Pulls (Docker Hub) (differs)1 977 455No figure on Docker Hub
Forks (GitHub) (differs)11 931 (better)0 (worse)
Last release (differs)2026-11-05 (worse)2026-11-08 (better)
Where it runs (differs)On your machine (mcp/fetch)Remote server (biomedmcp.unibiointelligence.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/unibio-intelligence/biomedmcp
Changes in the last 7 days (differs)14
First seen (differs)2026-10-112026-11-05
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 34 h ago returned HTTP 405

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

Fetch (Reference)

In its own words, on Docker MCP Catalog:

Fetches a URL from the internet and extracts its contents as markdown.

biomedmcp

In its own words, on Official MCP Registry:

Integrated public biomedical research with cited, bounded evidence.

How to run each

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

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

biomedmcp As a remote MCP server

Claude Code
claude mcp add --transport http biomedmcp https://biomedmcp.unibiointelligence.com/mcp

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

Only biomedmcp has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of biomedmcp publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Fetch (Reference) · What it can do: biomedmcp · Compare two other plugins

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

Where the data comes from: how the catalog is built