CiteStamp MCP server
online · 100% uptimecom.citestamp/citestamp·v1.3.1Check that a reference resolves; see what supports, refutes or cites a paper. CC0 graph, read-only.
0 stars
Reviews
Write oneNobody has reviewed CiteStamp yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
CiteStamp tools (7)
write = sends, deletes, buys or postscheck_referenceFreeWhether a reference resolves to a real work. Use when an answer is about to cite a paper. Give a DOI, an arXiv id or the reference as written. Answers found, confirm (with the reason), not found in the named sources on a date, or couldn't check. A not-found is not proof a work was never published.
edges_aboutFreeEvery edge touching the given work in either direction, each tagged asserted|inferred with attribution and provenance. Use when a user asks 'what is known about this paper's citations' or wants the whole neighbourhood in one call. Paged.
references_ofFreeWhat the given work CITES (its reference list). Use when a user asks what a paper relies on, whether a specific citation in it exists, or wants to check a reference before reusing it. Paged.
retraction_listingFreeWhether the Retraction Watch database lists the given DOI as retracted, from the dated export CiteStamp joins weekly. Use when a user asks whether a paper has been retracted or carries a retraction notice. Not listed means not in that export; the publisher record is not checked.
what_citesFreeWorks that CITE the given DOI (incoming citations). Use when a user asks who cites a paper, how much a work has been cited, or whether a claimed 'cited by' is real. Returns edges with tier + attribution; paged.
what_refutesFreeEdges recorded as REFUTING the given work or claim: human-signed refutations plus failed replication outcomes coded by the FORRT Replication Database. Use when a user asks whether a finding failed to replicate or has been contradicted.
what_supportsFreeEdges recorded as SUPPORTING the given work or claim: human-signed support claims plus successful replication outcomes coded by the FORRT Replication Database. Use when a user asks whether a finding held up or was replicated.
Public scan report
scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1130ms20/20
- Tool poisoning7 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
How CiteStamp compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 85% of 48,243 servers
- Tools
- 7
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 1,346 ms
- faster than 8% of 30,027 servers
What its tools let an agent do: 7 read
Release history: 5 versions in the registry since 2026-08-31, latest 2026-10-27, typically one every 16 days.
Install CiteStamp in Claude Code, Cursor or VS Code
claude mcp add --transport http citestamp https://mcp.citestamp.com/mcp
What the publisher says
From the CiteStamp repository's README, as published. We do not edit it. Read it on GitHub
CiteStamp MCP server
Ground citations before your agent emits them.
CiteStamp is a free citation-health tool for researchers: it checks references against the public scholarly registries (Crossref, DataCite, OpenAlex) and flags the ones that do not resolve to a known work or that a publisher has marked retracted, the hallucinated-citation failure mode LLM users keep hitting.
This repo is the install guide for the hosted MCP server over CiteStamp's CC0 citation graph. There is nothing to build or run locally; the server is remote.
The five tools (all read-only)
- whatsupports / whatrefutes: typed edges bearing on a claim
- whatcites / referencesof: the citing and cited works around a reference
- edges_about: edges on a topic
Every result carries its tier: accountable edges are signed by a human identity (ORCID); inferred edges are machine-derived. Your agent can ask for signed-only.
Add it to your client
No key is needed. Every snippet below works as written.
Gemini CLI (extension)
gemini extensions install https://github.com/citestamp/mcpOr add the server by hand in ~/.gemini/settings.json:
{ "mcpServers": { "citestamp": { "httpUrl": "https://mcp.citestamp.com/mcp" } } }Gemini Spark (custom app)
In the Gemini web app: Settings & help → Connected Apps → under "Custom apps for Spark" click Add a custom app → enter https://mcp.citestamp.com/mcp → Next. Type @ in a prompt and pick CiteStamp to make Gemini use it. Custom apps need access to Gemini Spark on a personal Google Account with Keep Activity on.
Claude (claude.ai / Desktop)
Settings → Connectors → Add custom connector → URL https://mcp.citestamp.com/mcp. Leave authentication empty.
Claude Code
claude mcp add --transport http citestamp https://mcp.citestamp.com/mcpCursor (~/.cursor/mcp.json)
{ "mcpServers": { "citestamp": { "url": "https://mcp.citestamp.com/mcp" } } }Cline (MCP settings)
{ "mcpServers": { "citestamp": {
"type": "streamableHttp",
"url": "https://mcp.citestamp.com/mcp" } } }VS Code (.vscode/mcp.json)
{ "servers": { "citestamp": {
"type": "http",
"url": "https://mcp.citestamp.com/mcp" } } }If a snippet drifts from your client's current config schema, your client's MCP docs win; the endpoint is the stable part.
Optional: raise the rate limit
A key is never required. If you hold one, send it as a header on the same endpoint:
Authorization: Bearer <your key>For Claude Code that is --header "Authorization: Bearer "; for the JSON configs, add "headers": { "Authorization": "Bearer " } to the server entry. A bad key is a loud 401, never a silent downgrade to anonymous, so add the header only once you have a key.
What this is not
CiteStamp reports what public registries say at a dated point in time. It does not judge the truth or quality of any work, and its only verdict vocabulary is "does not resolve to a known work" and "marked retracted by the publisher". Statements about works, never about people.
Links
- Integration guide + REST API: https://citestamp.com/for-ai
- Check a bibliography in the browser (free, nothing uploaded): https://citestamp.com/check
- Reference-health badge for any DOI: https://citestamp.com/citestamped/
- Privacy: https://citestamp.com/privacy · Contact: info@citestamp.com
CiteStamp is built by 3Rivers Enterprises LLC, Fort Wayne, Indiana.
Nothing above is checked by us. What we check is on the safety report.
CiteStamp: common questions
- Is CiteStamp MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the CiteStamp safety report
- How do I install CiteStamp?
- It runs remotely at mcp.citestamp.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does CiteStamp need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is CiteStamp maintained?
- The last commit was 10 days ago (2026-10-27). The latest release is v1.3.1.
- Is CiteStamp up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does CiteStamp compare with other MCP servers?
- safety score 91/100 (higher than 85% of 48,243 servers); tools 7 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.