CiteStamp MCP server

• Registry namecom.citestamp/citestampverified in the MCP registry

The registry name sits under citestamp.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-21
• Tools7
• Server calls itselfcitestamp
• Server version1.3.0
• Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 390 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 4 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
• Answeredmeasuring4 of the 7 daily checks it takes to print a share
• Median first answer567 ms
• Space in an agent's context≈ 1,787 tokensthe definitions of all its tools (7), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

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

• what_refutes

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

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

• references_of

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

• edges_about

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

• retraction_listing

  Whether 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…

• check_reference

  Whether 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…