Fetch (Reference) vs Scriptura
Fetch (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 2 (Docker MCP Catalog, PyPI (MCP servers)). Scriptura is an MCP server published by scriptura.si. 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
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:1a7a0996a565 Forks (GitHub): 11 923 Pulls (Docker Hub): 1 976 289 Stars (Docker Hub): 58 Stars (GitHub): 91 847 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 923 Stars (GitHub): 91 847 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 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
| Fact | Fetch (Reference) | Scriptura |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 91 847 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 1 976 289 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 923 | No figure on GitHub |
| Last release (differs) | 2026-11-05 (better) | 2026-10-25 (worse) |
| Where it runs (differs) | On your machine (mcp/fetch) | Remote server (scriptura.si/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/modelcontextprotocol/servers | Not stated |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-25 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 42 h ago returned HTTP 200 |
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)
Fetches a URL from the internet and extracts its contents as markdown.
Scriptura
953 classic works in the original beside English: Greek, Latin, philosophy, literature, scripture
How to run each
Fetch (Reference) As a local MCP server: Docker image
claude mcp add --transport stdio fetch -- docker run -i --rm mcp/fetch
Scriptura As a remote MCP server
claude mcp add --transport http scriptura https://scriptura.si/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Scriptura has a remote endpoint we check. How we check endpoints
Tools each declares
Only Fetch (Reference) has
fetch
Only Scriptura has
get_passagelist_editionsread_workroomsearch_shelfwho_read_verse
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Scriptura as of 2026-11-06). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Fetch (Reference) · What it can do: Scriptura · 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.