CiteProof
Anti-hallucination checks for AI literature reviews. CiteProof checks recorded quotes and numbers against the source text, looks up DOIs, matches citations to a reference list, and checks that counts and risk-of-bias judgements hold up. It comes in two parts: an MCP server for Claude Science and other research agents, and a full research assistant app that writes evidence-grounded papers.

Research Web → CiteProof.top
Claude Science MCP → Customize → Connectors → Add connector → Local command:
Contents
What is CiteProof?
AI research agents are now good at finding and reading papers. They are less good at proving their work: which databases were searched, how many records were screened, whether a quoted sentence is really in the paper, whether two reviewers agreed. CiteProof is built around that gap.
| CiteProof MCP | CiteProof Research |
|---|
| What it is | An MCP server with 40 evidence and audit tools | A web app with a 24-agent research pipeline |
| Who does the research | Your agent (Claude Science, or any MCP client) | The app's own agents |
| Language model inside | None. It needs no API key | Yes, any OpenAI-compatible endpoint |
| Best for | Systematic reviews that need an audit trail | Fast cited reports and full evidence-grounded papers |
| Where it lives | MCP/ | backend/, frontend/ |
A small first benchmark (two reviews against Claude Science) showed that agents with strong search find far more of the known included studies than CiteProof Research does. That is why the MCP server does not try to search: it audits the work of the agent that does.
CiteProof MCP
CiteProof MCP adds evidence checks to a research agent. Language models can invent quotes, figures and references, so each quote is compared with the source text you supply, each number with its quote, each DOI with Crossref (with a doi.org fallback), and each author-year or DOI citation with the reference list you supply (numeric citations such as [1] are counted, not resolved). Around those checks it keeps a protocol, PRISMA counts, a screening log, an evidence table, claim checks, risk-of-bias records and an exportable audit trail. It flags what does not hold and never decides whether a study is right. It works with Claude Science and with other tools that can run a stdio MCP server, such as research agents and desktop AI clients.
The server has no language model inside. The agent searches, reads, decides and writes. The server stores each decision, checks the evidence it points to, computes the numbers and refuses bad input.
Full documentation: MCP/README.md · tool reference: MCP/docs/SPEC.md.
What it checks
| Check | How |
|---|
| A quote really appears in the source text | The agent sends the quote and the text. The server matches them after normalising case, whitespace, quotes, dashes and line-break hyphens, on word boundaries. The result is stored as quote_verified. |
| Numbers in the evidence table come from the quote | Sample size, estimate and confidence limits must be written in the quote. Estimates outside their interval are refused. |
| PRISMA numbers add up | Counts come from the recorded searches, the deduplication step and the screening decisions, and the flow invariants are checked on every call. |
| Two reviewers agree | Cohen's kappa over the papers both reviewers decided, with the disagreements listed. |
| DOIs exist and are not retracted | Crossref and doi.org lookups. An unreachable registry gives "unverified", never "not found". |
| Citations match the reference list | In-text citations are matched by DOI, author and year, or title. "Resolved" means matched, not supported. |
| Risk-of-bias overall judgements follow the published rules | RoB 2, ROBINS-I and Newcastle-Ottawa (AHRQ thresholds). |
| Duplicates | Deterministic clustering by DOI, PMID, then title plus year plus first author. |
Quick start
One command, in any MCP client that runs local (stdio) servers:
The citeproof-mcp npm package is a small launcher. It finds uv (or installs it, unless CITEPROOF_NO_AUTO_INSTALL=1), then runs the Python server from the wheel attached to the matching GitHub release. You need Node.js 18 or newer. Python and git are not required: uv downloads Python 3.12 when needed.
| Client | How to add CiteProof MCP | Status |
|---|
| Claude Science | Customize → Connectors → Add connector → Local command. Name citeproof, command npx -y citeproof-mcp. | npx install tested on Claude Science 0.1.70 (Windows 11, 24 tools listed for 0.2.1; 0.3.0 with 40 tools not yet tested in Claude Science); bundle install tested on 0.1.67 |
| Claude Desktop | Download citeproof.mcpb and open it (Settings → Extensions), or add the JSON below to claude_desktop_config.json. | New in 0.2.0 |
| Claude Code | claude mcp add citeproof -- npx -y citeproof-mcp | New in 0.2.0 |
| Cursor, VS Code, Windsurf, other clients | Add the JSON below to the client's MCP settings (VS Code: the servers form further down). | Not yet tested |
{
"mcpServers": {
"citeproof": {
"command": "npx",
"args": ["-y", "citeproof-mcp"]
}
}
}
VS Code's built-in MCP support (.vscode/mcp.json or your user MCP settings) uses servers instead of mcpServers:
{
"servers": {
"citeproof": {
"type": "stdio",
"command": "npx",
"args": ["-y", "citeproof-mcp"]
}
}
}
Everything runs on your computer. Review files go to CITEPROOF_MCP_HOME, or to ~/.citeproof-mcp when it is not set. The server's only network calls are DOI and retraction lookups to Crossref and doi.org. On first run the launcher also downloads its own files: the npm package, and, when no compatible Python is found, uv, Python 3.12 and the server wheel. claude.ai custom connectors need a remote server, so they are not supported.
If Claude Science reports that a file is not readable inside its sandbox, set CITEPROOF_UV_HOME (Advanced settings → environment variables) to a folder inside the connector's workspace, so uv keeps its cache and Python there. The older bundle install in MCP/docs/CLAUDE_SCIENCE.md still works.
Install from source with pip
Then point the client at the citeproof-mcp command (stdio), optionally with "env": { "CITEPROOF_MCP_HOME": "/path/to/your/review-data" }.
Companion skill
MCP/skills/citeproof-review teaches an agent the review workflow and the tool order. Install steps for Claude Code, Claude Desktop and Claude Science are in MCP/skills/README.md. A reviewer-instructions snippet for Claude Science is in MCP/docs/REVIEWER_SNIPPET.md.
The 40 tools