xrad
Provides an MCP server for storing and querying knowledge as verifiable claims, enforcing evidence-backed assertions with exact quotes and refusing paraphrases or unsupported relations.
README
xrad
Your agent cannot assert here without quoting the source.
Extraction pipelines produce knowledge graphs that assert. Acme ACQUIRED Beta, as a fact. That holds until the source only implies it, attributes it to
someone, or hedges it — and then the graph has quietly turned a rumour into a
fact, and nothing downstream can tell.
xrad stores claims: who said it, with what commitment, and the verbatim span that proves it. The contract lives in the tooling, not in the prompt.
uv tool install xrad # the CLI, isolated, on your PATH
uv pip install xrad # or as a library, in your project
In sixty seconds
git clone https://github.com/narimannemo/xrad && cd xrad
python examples/demo.py
-- 1. an agent paraphrases ---------------------------------
REFUSED | quote_not_found
The contract says 'hereby acquires'. The paraphrase is plausible,
would pass any human review, and is not in the document.
-- 2. it quotes verbatim -----------------------------------
STORED | contract:c00001 at characters [31, 64]
-- 3. it invents a relation --------------------------------
REFUSED | unknown relation 'SORT_OF_RELATED_TO' — use one of: ACQUIRED, OWNS
-- 4. it credits a source the quote does not name -----------
STORED, with a warning:
the quote does not name 'Reuters'...
Three refusals
A paraphrase is refused. A model quotes; xrad finds the quote in the source. Exact, case-insensitive, whitespace-insensitive — and deliberately nothing fuzzy, because a near-miss means the model paraphrased, and a paraphrase pointing at real offsets is the corruption this exists to prevent.
A relation outside the vocabulary is refused, with the valid options in the error so an agent can retry. Vocabularies are YAML; the prompt text is generated from the same file the code enforces, so the two cannot drift.
A claim with no evidence cannot be constructed. A claim you cannot check is indistinguishable from one that was invented.
Two questions an edge store cannot answer
$ xrad path Acme Gamma
1. Acme --ACQUIRED--> Beta the filing
2. Beta --OWNS--> Gamma (reported) Reuters
2 hops · 1 asserted · 1 reported or hedged
$ xrad path Acme Gamma --modality assertion
no chain — the connection may exist when reported claims are allowed
The argument does not survive on the filing's own authority. It is a shortest-path query by any other name, but what comes back is a chain of claims: every hop carries who committed to it, how strongly, and whether its evidence held.
$ xrad disagreements
Acme ACQUIRED Beta the filing (assertion) vs the auditor (rejected)
Two sources contradicting each other is the most interesting object in a corpus. An edge store would have kept one and lost the other.
Documentation
| Concepts | why claims and not edges, and what follows from it |
| MCP | wiring it to Claude Code, Cursor or your own agent |
| Vocabularies | designing the closed set of types and relations |
| Auditing | having a second model try to refute every claim |
| Reference | every command and the Python API |
| Packaging | uv, Homebrew, and which to use |
Why it exists
Extracted from a pipeline that put 5,646 claims from a 1652 folio into a graph where every one resolves to a rectangle on a scanned page.
The audit is the reason to trust any of it: a second model, shown only the cited span, tries to refute each claim. 23% did not survive. The largest single failure was an attribution the quote itself did not contain — the source names Strabo once and writes for three paragraphs, and the extractor quotes paragraph three while still crediting him. One prompt rule fixed it, refutation fell to 11.5%, and it replicated on a second volume (z = 5.05).
That finding ships as the warning record_claim emits when a reported claim
credits a source its own quote does not name.
What it is not
Not a vector index. No embeddings, no similarity search — a claim store you traverse.
Not an extraction model. Bring your own agent; xrad decides what it is allowed to record.
Not a fact database. Sources are wrong. A source being wrong is recorded, with the modality showing how it held the statement.
Apache-2.0. Contributions welcome — CONTRIBUTING.md says what will and will not be accepted before you spend an evening.
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.