Ext Ops Panel
Open dashboard
Comparison

doiget vs io.github.cyanheads/crossref-mcp-server

doiget is an MCP server published by QAtlasHub. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.cyanheads/crossref-mcp-server is an MCP server published by cyanheads. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplacedoigetio.github.cyanheads/crossref-mcp-server
Official MCP Registry Listed
Version: 0.9.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 0.4.3
Downloads/month (npm): 2 672
Downloads/week (npm): 648
Forks (GitHub): 0
Stars (GitHub): 4
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

doiget vs io.github.cyanheads/crossref-mcp-server
Factdoigetio.github.cyanheads/crossref-mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)4 (better)
Forks (GitHub)00
Last release (differs)Not published2026-10-23
Where it runs (differs)On your machine (https://github.com/QAtlasHub/doiget/releases/download/v0.9.0/doiget-0.9.0.mcpb)Remote server (crossref.caseyjhand.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published9, secrets among them: 0
Licence (differs)MITNot stated
Repository (differs)github.com/qatlashub/doigetgithub.com/cyanheads/crossref-mcp-server
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago

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

doiget

In its own words, on Official MCP Registry:

OA-first paper fetcher: DOIs/arXiv IDs to local PDFs + metadata via Open Access APIs.

io.github.cyanheads/crossref-mcp-server

In its own words, on Official MCP Registry:

Resolve DOIs, search ~188M scholarly works, and fetch references via the Crossref REST API.

How to run each

doiget

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

io.github.cyanheads/crossref-mcp-server As a remote MCP server

Claude Code
claude mcp add --transport http crossref-mcp-server https://crossref.caseyjhand.com/mcp

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

Only io.github.cyanheads/crossref-mcp-server has a remote endpoint we check. How we check endpoints

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 doiget publish no settings it asks for, so we do not compare settings.

What it can do: doiget · What it can do: io.github.cyanheads/crossref-mcp-server · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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