Ext Ops Panel
Open dashboard
Comparison

Fetch (Reference) vs PDF Text Extractor (Apify Actor)

Fetch (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). PDF Text Extractor (Apify Actor) is an MCP server published by truhojunbot-tech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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)PDF Text Extractor (Apify Actor)
Docker MCP Catalog Listed
Version: sha256:1a7a0996a565
Forks (GitHub): 11 780
Pulls (Docker Hub): 1 910 043
Stars (Docker Hub): 58
Stars (GitHub): 91 180
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

Fetch (Reference) vs PDF Text Extractor (Apify Actor)
FactFetch (Reference)PDF Text Extractor (Apify Actor)
Marketplaces that list it11
Stars (GitHub) (differs)91 180No figure on GitHub
Pulls (Docker Hub) (differs)1 910 043No figure on Docker Hub
Forks (GitHub) (differs)11 780No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/fetch)Remote server (mcp.apify.com)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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.

PDF Text Extractor (Apify Actor)

In its own words, on Official MCP Registry:

Extract text, tables and RAG chunks from public PDF URLs; pay-per-event via your Apify account.

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

PDF Text Extractor (Apify Actor)

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.

Tools each declares

The marketplaces of PDF Text Extractor (Apify Actor) 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: Fetch (Reference) · What it can do: PDF Text Extractor (Apify Actor) · 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