CiteStamp

com.citestampPublished by citestamp.comOfficial publisherv1.3.1Updated Oct 29, 2026

Check that a reference resolves; see what supports, refutes or cites a paper. CC0 graph, read-only.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping Knowledge & Memory

Server details

Identifier: com.citestamp/citestamp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to citestamp.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.citestamp%2Fcitestamp.svg)](https://sourceweft.com/mcp/com.citestamp%2Fcitestamp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Remote, read-only citation-health server that lets an assistant verify references and explore what cites, supports, refutes or retracts a paper.

What you can do: Check whether a reference resolves to a real work, given a DOI, arXiv id or the reference as written
List works that cite a paper, or the references a paper relies on, with paging
Show supporting and refuting edges, including replication outcomes from the FORRT Replication Database
Return every edge touching a work in either direction, tagged asserted or inferred with attribution and provenance
Report whether the Retraction Watch export lists a DOI as retracted
When to use it: Use it when an answer turns on a specific paper's citations, references, support, refutation or replication record, or when a reference is about to be cited and should be grounded first. It suits literature checks and catching citations that do not resolve.
Requirements: A remote streamable-HTTP endpoint; nothing to install or run locally. No authentication is required. Anonymous access is limited to 10 requests per minute per IP; an optional free key sent as an Authorization Bearer header raises the limit.

Before you install

Read-only, but answers are paged and a single page is not the complete answer; sparse results mean the sweeps have not reached a work, not that nothing cites it. A not-found from check_reference is not proof a work was never published, and retraction_listing only reflects a dated export, not the publisher record. Inferred edges are machine-derived and not independent of their source metadata. An optional key is sent as a bearer header; a bad key returns an error rather than falling back to…

Installation

In SourceWeft

Open CiteStamp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.citestamp%2Fcitestamp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "citestamp": {
      "type": "http",
      "url": "https://mcp.citestamp.com/mcp"
    }
  }
}

README

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.


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 [email protected]) 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 claim
what_cites / references_of: the citing and cited works around a reference
edges_about: edges on a topic
retraction_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 record
check_reference: whether a reference resolves to a real work, before an answer cites it. Give a DOI, an arXiv id or the reference as written. It reads Crossref, DataCite and doi.org (which answers for every DOI agency) and says found, confirm (with the reason), not found in the named sources on a date, or couldn't check. 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)

Or add the server by hand in ~/.gemini/settings.json:

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

Cursor (`~/.cursor/mcp.json`)

Cline (MCP settings)

json

{ "mcpServers": { "citestamp": {    "type": "streamableHttp",    "url": "https://mcp.citestamp.com/mcp" } } }

{ "mcpServers": { "citestamp": {    "type": "streamableHttp",    "url": "https://mcp.citestamp.com/mcp" } } }

VS Code (`.vscode/mcp.json`)

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:

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.

Tools

what_supports

What supports

Edges 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.