Ext Ops Panel
Open dashboard
Comparison

CiteStamp vs refcheck

CiteStamp is an MCP server published by citestamp.com. Marketplaces we read that list it: 1 (Official MCP Registry). refcheck is an MCP server published by benchoi93. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceCiteStamprefcheck
Official MCP Registry Listed
Version: 1.2.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (PyPI): 98
Downloads/week (PyPI): 22
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

CiteStamp vs refcheck
FactCiteStamprefcheck
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.citestamp.com/mcp)On your machine (refcheck-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 4
LicenceNot statedNot stated
Repository (differs)github.com/citestamp/mcpgithub.com/umn-choi-lab/refcheck
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 29 h agono remote endpoint we check

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

CiteStamp

In its own words, on Official MCP Registry:

Citation-health over a CC0 citation graph: what supports, refutes, or cites a paper. Read-only.

refcheck

In its own words, on Official MCP Registry:

Verify academic citations against real databases. Catches hallucinated references, exports BibTeX.

How to run each

CiteStamp As a remote MCP server

Claude Code
claude mcp add --transport http citestamp https://mcp.citestamp.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

refcheck As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ELSEVIER_INSTTOKEN=<YOUR_ELSEVIER_INSTTOKEN>" --env "ELSEVIER_KEY=<YOUR_ELSEVIER_KEY>" --env "IEEE_API_KEY=<YOUR_IEEE_API_KEY>" --env "S2_API_KEY=<YOUR_S2_API_KEY>" --transport stdio refcheck -- uvx refcheck-mcp

Requires: ELSEVIER_INSTTOKEN (secret), ELSEVIER_KEY (secret), IEEE_API_KEY (secret), S2_API_KEY (secret)

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

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

What it can do: CiteStamp · What it can do: refcheck · 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