Ext Ops Panel
Open dashboard
Comparison

Fetch (Reference) vs PageIndex MCP

Fetch (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). PageIndex MCP is an MCP server published by VectifyAI. 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)PageIndex MCP
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.8.2
Downloads/month (npm): 293
Downloads/week (npm): 62
Forks (GitHub): 52
Stars (GitHub): 400
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 PageIndex MCP
FactFetch (Reference)PageIndex MCP
Marketplaces that list it11
Stars (GitHub) (differs)91 180 (better)400 (worse)
Pulls (Docker Hub) (differs)1 910 043No figure on Docker Hub
Forks (GitHub) (differs)11 780 (better)52 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/fetch)On your machine (@pageindex/mcp)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/vectifyai/pageindex-mcp
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.

PageIndex MCP

In its own words, on Official MCP Registry:

Reasoning-based RAG system for chatting with long PDFs. Supports local and online files.

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

PageIndex MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio pageindex-mcp -- npx -y @pageindex/mcp

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

Tools each declares

The marketplaces of PageIndex MCP 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: PageIndex MCP · 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