Ext Ops Panel
Open dashboard
Comparison

Fetch (Reference) vs pdfmux

Fetch (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). pdfmux is an MCP server published by NameetP. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-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

Where each is published
MarketplaceFetch (Reference)pdfmux
Docker MCP Catalog Listed
Version: sha256:1a7a0996a565
Forks (GitHub): 11 787
Pulls (Docker Hub): 1 912 772
Stars (Docker Hub): 58
Stars (GitHub): 91 222
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.8.7
Downloads/month (PyPI): 1 021
Downloads/week (PyPI): 194
Forks (GitHub): 14
Stars (GitHub): 83
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 pdfmux
FactFetch (Reference)pdfmux
Marketplaces that list it11
Stars (GitHub) (differs)91 222 (better)83 (worse)
Pulls (Docker Hub) (differs)1 912 772No figure on Docker Hub
Forks (GitHub) (differs)11 787 (better)14 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/fetch)On your machine (pdfmux)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/nameetp/pdfmux
Changes in the last 7 days00
First seen2026-10-112026-10-11

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.

pdfmux

In its own words, on Official MCP Registry:

PDF-to-Markdown extraction that audits its own output and flags any extractor's silent drops.

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

pdfmux As a local MCP server: PyPI package

Claude Code
claude mcp add --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --transport stdio pdfmux -- uvx serve pdfmux

Requires: GEMINI_API_KEY (secret)

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

Tools each declares

The marketplaces of pdfmux 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: pdfmux · 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.

Where the data comes from: how the catalog is built