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.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。