mcp-citation-checker
An MCP server that verifies whether a claim is actually supported by the source text at a given citation — independent of what the calling LLM asserts.
README
mcp-citation-checker
An MCP server that verifies whether a claim is actually supported by the source text at a given citation — independent of what the calling LLM asserts.
Why this exists
LLM agents that cite sources can still get the citation wrong: paraphrasing loosely, citing the wrong page, or asserting a source says something it doesn't. check_citation closes that gap by independently fetching the real text at the claimed citation and asking a separate LLM call to judge, strictly from that text, whether the claim holds up. The agent's own paraphrase is never trusted as evidence — only the independently-fetched source is.
Design: pluggable backends
Looking up "the real text at citation X" depends entirely on where your documents actually live — Weaviate, Postgres, a flat file, something else. Rather than hardcoding one storage system, this package defines a small interface any backend can implement:
class SourceLookup(Protocol):
def fetch(self, pdf_name: str, page_number: int) -> list[dict]:
...
weaviate is included out of the box as a working, tested implementation (bundled as an optional extra, so installing the base package doesn't force a Weaviate dependency on anyone who doesn't need it). Writing your own backend for another storage system just means implementing that one fetch method — see Writing your own backend below.
Install
pip install "mcp-citation-checker[weaviate]"
(Omit [weaviate] if you're supplying your own backend instead.)
Configuration
Set via environment variables when the server starts:
| Variable | Default | Purpose |
|---|---|---|
CITATION_BACKEND |
weaviate |
Which backend to use (currently only weaviate ships built-in). |
ANTHROPIC_API_KEY |
— | Required. Used for the verification LLM call. |
WEAVIATE_MODE |
local |
local (self-hosted) or cloud (Weaviate Cloud). |
WEAVIATE_HOST / WEAVIATE_PORT |
localhost / 8081 |
Used when WEAVIATE_MODE=local. |
WEAVIATE_CLOUD_URL / WEAVIATE_API_KEY |
— | Required when WEAVIATE_MODE=cloud. |
Usage
Run directly:
mcp-citation-checker
Or wire it into an MCP client config (e.g. Claude Desktop, or your own agent) like any other stdio MCP server:
{
"mcpServers": {
"citation-checker": {
"command": "mcp-citation-checker",
"env": {
"ANTHROPIC_API_KEY": "...",
"WEAVIATE_MODE": "cloud",
"WEAVIATE_CLOUD_URL": "...",
"WEAVIATE_API_KEY": "..."
}
}
}
}
The server exposes one tool, check_citation(claim, pdf_name, pdf_page), returning "<label>: <one-sentence reasoning>" where <label> is one of supported, contradicted, or not_mentioned.
Writing your own backend
The verification logic (mcp_citation_checker.checker.check_citation) has no storage-specific coupling at all — it only needs claim and a list of chunk dicts (pdf_name/page_number/text). Any backend just needs to implement the SourceLookup shape:
class MyBackend:
def fetch(self, pdf_name: str, page_number: int) -> list[dict]:
# return [{"pdf_name": ..., "page_number": ..., "text": ...}, ...]
...
No inheritance required — SourceLookup is a typing.Protocol, so any object with a matching fetch method satisfies it.
Two ways to actually use a custom backend:
- Bypass the bundled server entirely: call
checker.check_citation(claim, my_backend.fetch(pdf_name, page))directly from your own code/MCP server — this works today, no changes to this package needed. - Wire it into this package's own server: the current version only registers a
weaviatebackend in_get_backend()(src/mcp_citation_checker/__init__.py) — using a different backend through the bundledmcp-citation-checkercommand currently means adding a branch there yourself (a small, welcome PR).
Development
pip install -e ".[weaviate,dev]"
pytest
License
MIT — see LICENSE.
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.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
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.