Ext Ops Panel
Open dashboard
Comparison

speedread vs io.github.ref-tools/ref-tools-mcp

speedread is an MCP server published by brennengreen. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.ref-tools/ref-tools-mcp is an MCP server published by ref-tools. 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
Marketplacespeedreadio.github.ref-tools/ref-tools-mcp
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 3.0.1
Downloads/month (npm): 3 965
Downloads/week (npm): 1 033
Forks (GitHub): 71
Stars (GitHub): 1 180
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

speedread vs io.github.ref-tools/ref-tools-mcp
Factspeedreadio.github.ref-tools/ref-tools-mcp
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)1 180 (better)
Forks (GitHub) (differs)0 (worse)71 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (https://github.com/brennengreen/speedread/releases/download/v0.1.0/speedread-aarch64-apple-darwin.mcpb)Remote server or your machine
Transport (differs)stdiostdio, Streamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/brennengreen/speedreadgithub.com/ref-tools/ref-tools-mcp
Changes in the last 7 days (differs)01
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

speedread

In its own words, on Official MCP Registry:

Token-efficient code reading for coding agents: symbol-aware, budgeted, diff-aware reads.

io.github.ref-tools/ref-tools-mcp

In its own words, on Official MCP Registry:

Token efficient search for coding agents over public and private documentation.

How to run each

speedread

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.ref-tools/ref-tools-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "REF_API_KEY=<YOUR_REF_API_KEY>" --transport stdio ref-tools-mcp -- npx -y ref-tools-mcp

Requires: REF_API_KEY (secret)

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of speedread publish no settings it asks for, so we do not compare settings.

What it can do: speedread · What it can do: io.github.ref-tools/ref-tools-mcp · Compare two other plugins

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