agent-evidence-mcp
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@agent-evidence-mcpverify whether this claim holds against the evidence bytes I supplied"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
agent-evidence-mcp
An offline, read-only MCP server that decides whether a claim about an AI system holds against evidence bytes you supply, and replays the agent-evidence conformance vectors.
It's for agent builders, auditors and platform engineers who want their assistant to check evidence instead of trusting a report.
Install the released package: pip install agent-evidence-mcp==0.1.0. It pins probity-verify==0.1.1, agent-evidence-vectors==0.23.0, agent-evidence-vocabulary==0.6.0 and agent-evidence-admission==0.1.2 exactly.
Quick start
Add it to Claude Code, then ask the assistant to run the sample claim:
claude mcp add agent-evidence -- uvx agent-evidence-mcp@0.1.0Or install the Claude Code plugin: /plugin install agent-evidence --marketplace probityai/agent-evidence-mcp.
Or call a tool from Python, with no client installed beyond the package:
uvx --from agent-evidence-mcp==0.1.0 python - <<'PY'
import asyncio
from mcp.client import Client
from mcp.client.stdio import StdioServerParameters
async def main():
async with Client(StdioServerParameters(command="agent-evidence-mcp")) as client:
result = await client.call_tool("verify_sample", {"scenario": "contradicted"})
print(result.structured_content["decision"], result.structured_content["reason"])
asyncio.run(main())
PYIt prints:
contradicted selected_span_missing_from_recordA passage the report quotes is missing from the source capture, so the claim is contradicted. Use supported or not_established as the scenario for the other two decisions.
Related MCP server: deepbom
Tools
Seven tools, all read-only, offline and bounded: verify_claim, verify_sample, list_vector_corpora, run_vectors, explain_vector, lookup_term and check_artifact_digest. Nothing is fetched, written or sent.
Status
Version 0.1.0. The tests run every tool through a real MCP client against the shipped corpus, and a mutation check confirms they fail when a tool's output is broken. canonicalize_json and verify_dsse come later, once their Rust crates ship Python wheels.
Documentation
page | read it for |
every tool, its arguments and what it returns | |
Claude Code, Gemini CLI, Docker and plain stdio | |
a short index for agents using the server | |
the commands to run and what never to hand-edit |
License
Apache-2.0.
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only verifier for 25 ProofRelay MCP tools and non-confidential evidence bundles.
Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.
Browser-local and CLI static evidence for deployed AI model artifacts.
Hand off AI work with a signed Verification Receipt — an independent verifier proves it runs.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to verify claims with evidence-based truth scores and confidence levels by running a deterministic pipeline of evidence lanes and adversarial checks.26MIT
- AlicenseNot gradedqualityBmaintenanceEnables local inspection of AI model deployment artifacts without executing model code, returning SHA-256, structure, defect analysis, and evidence-gap findings in Gemini CLI conversations.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents to verify C2PA Content Credentials entirely offline from base64 file bytes, returning validation state, signer chain, hard-binding results, actions, issues, and portable provenance cards without any upload or network calls.9 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to verify claims against evidence through MCP tools, returning approved, rejected, or needs_review verdicts with replayable receipts.MIT