CiteStamp MCP server
Commit Nov 10, 2026Verifies scholarly references and identifies supporting, refuting, or retracted citations using public registries and a CC0 citation graph.
Also known as citestamp/mcp, mcp
- Stars
- 0
- Tools
- 3
- Downloads, 30 days
- —
- Latest version
- 1.3.1
- Last commit
- Nov 10, 2026
- License
- MIT
What is CiteStamp MCP?
CiteStamp verifies scholarly references and identifies supporting, refuting, or retracted citations using public registries and a CC0 citation graph. It exposes 3 tools, such as edges_about, retraction_listing, check_reference.
Summary generated from the project's README
About CiteStamp MCP server
CiteStamp provides a remote MCP server that allows researchers and developers to verify the validity of scholarly citations. By connecting to the hosted endpoint via streamable-http, users can prevent AI hallucinations by checking if references resolve to real works or if they have been retracted. The server accesses a CC0 citation graph and cross-references data against public registries like Crossref, DataCite, OpenAlex, and PubMed.
This tool is designed for use with various AI clients including Claude, Cursor, Gemini, and Cline. It operates without mandatory authentication, offering an anonymous tier limited to 10 requests per minute per IP. Users can increase this limit to 60 or 600 requests per minute by providing an optional free or Pro API key via an authorization header. The system distinguishes between accountable edges signed by human ORCID identities and machine-inferred edges, allowing agents to filter for specific data reliability tiers.
Written from the project's README. Every use case is checked against a quote from it.
How to install CiteStamp MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall CiteStamp MCP in Claude Code
$ claude mcp add --transport http mcp https://mcp.citestamp.com/mcpInstall CiteStamp MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.citestamp.com/mcp"
}
}
}Install CiteStamp MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.citestamp.com/mcp"
}
}
}Install CiteStamp MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"http","url":"https://mcp.citestamp.com/mcp"}'Install CiteStamp MCP in Codex
$ codex mcp add mcp --url https://mcp.citestamp.com/mcpInstall CiteStamp MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] url = "https://mcp.citestamp.com/mcp"
Install CiteStamp MCP in Gemini CLI
$ gemini mcp add -s user --transport http mcp https://mcp.citestamp.com/mcpInstall CiteStamp MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.citestamp.com/mcp",
"type": "http"
}
}
}CiteStamp MCP tools 3
Detected from the READMEedges_aboutretraction_listingcheck_reference
| edges_about | — | |
| retraction_listing | — | |
| check_reference | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablecitestamp/mcp is public and reachablegithub.com/citestamp/mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-10github.com/citestamp/mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model3 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 794 msPass
README
View on GitHubCiteStamp 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.
| Endpoint | https://mcp.citestamp.com/mcp |
| Transport | streamable-http |
| Protocol | 2025-06-18 |
| Auth | None. Anonymous at 10 requests/min per IP. An optional free key (email info@citestamp.com) raises that to 60/min; Pro to 600/min |
| Data | CC0 citation graph; human-signed and machine-inferred claims kept strictly apart |
The tools (all read-only)
what_supports/what_refutes: typed edges bearing on a claimwhat_cites/references_of: the citing and cited works around a referenceedges_about: edges on a topicretraction_listing: whether the Retraction Watch database lists a DOI as retracted, from the dated export CiteStamp joins weekly. Not listed means not in that export; it does not check the publisher recordcheck_reference: whether a reference resolves to a real work, before an answer cites it. Give a DOI, an arXiv id, a PubMed ID or the reference as written. It reads Crossref, DataCite and doi.org (which answers for every DOI agency), and PubMed for a PubMed ID given without a DOI, and says found, confirm (with the reason), not found in the named sources on a date, or couldn't check. A PubMed ID that leads to no record, or to another paper, is a confirm: only a DOI that no agency registered can be not found. A not-found is not proof that a work was never published
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/mcp
Or 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/mcp
Cursor (~/.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 <your key>"; for the JSON
configs, add "headers": { "Authorization": "Bearer <your key>" } 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. check_reference 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. retraction_listing says whether the dated
Retraction Watch export lists a DOI, and does not check the publisher record.
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.
CiteStamp MCP questions
How do I add CiteStamp MCP to Claude Code?
Run claude mcp add --transport http mcp https://mcp.citestamp.com/mcp in your terminal. Add --scope user to make it available in every project.
How do I add CiteStamp MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does CiteStamp MCP provide?
It exposes 3 tools, including edges_about, retraction_listing, check_reference.
What is the difference between accountable and inferred edges?
Accountable edges are signed by a human identity via ORCID, while inferred edges are machine-derived.