The problem: supported somewhere is not the same as supported by the right source What ProvenanceGuard does Results Checking claims when sources look similar Repairing blocked answers Why this fits Multiverse Computing Tool-using LLM agents no longer read from a single retrieved passage. Through the Model Context Protocol (MCP), an agent can call a search tool, inspect a structured patient or account record, query a database, and pull metadata, then weave all of it into one answer. That m aakes the usual question of factuality more subtle than it looks. Most of the systems built to check LLM answers, from RAGAS faithfulness to fine-grained checkers like MiniCheck, AlignScore, and SummaC, ask whether a claim is supported by the available evidence once that evidence has been pooled together. In their usual form, they do not tell us which MCP tool output supports each claim, or whether that is the source the answer names.
Getting the Source Right, Not Just the Fact: Source-Aware Verification for MCP Agents
A Blog post by Multiverse Computing on Hugging Face

Key points
- Our latest paper, ProvenanceGuard: Source-Aware Factuality Verification for MCP-Based LLM Agents (read it on Hugging Face, or on arXiv in the meantime), targets that gap.
- A claim can be supported by one MCP source while the answer attributes it to another.
- ProvenanceGuard keeps that connection between claim and source available for inspection.
Sentences selected automatically from the original article by Hugging Face Blog.
Story details
- Published
- Format
- Article
- Original
- huggingface.co ↗


