MCP Refchecker
MCP server for verifying academic citations via Semantic Scholar, OpenAlex, and CrossRef.
README
mcp-refchecker
An MCP server that lets Claude verify academic citations in real time against Semantic Scholar, OpenAlex, and Crossref — catching hallucinated or incorrect references before they end up in your work.
Built on top of academic-refchecker (MIT).
Tool
verify_citation — verifies that a cited paper exists and that its metadata (title, authors, year, venue) matches what was cited.
| Parameter | Type | Required | Description |
|---|---|---|---|
title |
string | yes | Title of the cited paper |
authors |
string[] | no | List of author names |
year |
integer | no | Publication year |
doi |
string | no | DOI (e.g. 10.1145/12345) |
arxiv_id |
string | no | arXiv ID (e.g. 2301.00001) |
url |
string | no | Direct URL to the paper |
Returns JSON:
{
"verified": true,
"url": "https://...",
"matched_paper": {
"title": "...",
"authors": [...],
"year": 2023,
"venue": "..."
},
"possible_match": null,
"errors": null,
"warnings": null,
"info": null
}
Result fields
verified—trueif the paper was found and all provided metadata (year, authors, venue) matches.falseif there is a real metadata conflict or the paper could not be found.matched_paper— the authoritative metadata from the verification source.possible_match— a Crossref fallback match when the exact title was not found but a close variant was (see "Fuzzy fallback" below).errors— hard errors that block verification (wrong year, wrong authors, paper not found).warnings— soft warnings that don't block verification (arXiv v1 vs v2 differences, arXiv preprint vs published venue, incomplete input metadata).info— informational suggestions (e.g., "reference could include arXiv URL").
What counts as an error vs a warning
academic-refchecker returns a flat list of issues with some inconsistency (year mismatches get marked as warnings while author mismatches get marked as errors). This wrapper normalises the output:
- Promoted to hard errors: plain
year/author/venuemismatches where the cited metadata actually differs from reality. These blockverified. - Demoted to warnings: "missing field" errors when the paper was found but the user didn't provide that field in the first place. Missing input metadata is not evidence of a hallucinated citation.
- Kept as warnings: arXiv version differences (v1 vs v2), preprint-vs-published venue notes.
Fuzzy fallback and its limitations
When academic-refchecker reports that a paper could not be verified, this wrapper makes a secondary query to Crossref using fuzzy title matching and fuzzywuzzy.ratio. If a candidate with ≥ 85% similarity is found, it's returned as possible_match with a warning.
What the fuzzy fallback catches:
- Stylistic title variations (case differences, punctuation, word order)
- Minor rewording
- Titles where refchecker's strict comparison rejected an otherwise valid match
What the fuzzy fallback does NOT catch:
- Real typos in distinctive title words (e.g., "Atention Is All You Need")
- Heavily mangled titles
This is a fundamental limitation of free academic search APIs. Crossref, OpenAlex, and Semantic Scholar all do keyword/token-based search — as soon as a distinctive word is misspelled, it simply isn't in the search index, and the real paper won't appear in results regardless of how you post-process them. Catching real typos would require semantic embeddings from a paid API (OpenAI, Voyage, etc.) or a full-text fuzzy search engine, neither of which is exposed by free scholarly data sources.
If you suspect a typo but verify_citation returns unverified, the best workaround is to rewrite the title in the most canonical form you can and try again.
Installation & configuration
Recommended: uvx (no install step)
If you have uv installed, no separate installation is needed. Add directly to your claude_desktop_config.json:
{
"mcpServers": {
"refchecker": {
"command": "uvx",
"args": ["mcp-refchecker"]
}
}
}
uvx downloads and runs the package in an isolated environment automatically. Restart Claude Desktop after saving the config.
Alternative: pip
pip install mcp-refchecker
Then add to claude_desktop_config.json:
{
"mcpServers": {
"refchecker": {
"command": "mcp-refchecker"
}
}
}
From source
git clone https://github.com/JonasBaath/mcp-refchecker
cd mcp-refchecker
pip install .
Optional environment variables
SEMANTIC_SCHOLAR_API_KEY— apply for one here for higher rate limits on refchecker's primary verification path.CROSSREF_MAILTO— your contact email, used to opt into Crossref's polite pool for more reliable fuzzy fallback access.MCP_REFCHECKER_DEBUG— set to any non-empty value to print debug logging from the fuzzy fallback path to stderr.
Example with all optional settings (uvx):
{
"mcpServers": {
"refchecker": {
"command": "uvx",
"args": ["mcp-refchecker"],
"env": {
"SEMANTIC_SCHOLAR_API_KEY": "your-key-here",
"CROSSREF_MAILTO": "you@example.com"
}
}
}
}
License
MIT — © Jonas Bååth. Built on academic-refchecker (MIT).
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.