MCP Verify Claim

Name: MCP Verify Claim
Author: sudo-ai-git

by sudo-ai-gitversion 1.0.0i★ –iRuns on your computer

Registry nameio.github.sudo-ai-git/mcp-verify-claim

Install

Overview

Description from the maker (original English)

Force evidence-gated, tiered claim reporting (FACT/INFERENCE/SPECULATION). No-LLM.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "verify-claim": {
      "command": "uvx",
      "args": [
        "mcp-verify-claim"
      ]
    }
  }
}

Run this in your terminal

claude mcp add verify-claim -- uvx mcp-verify-claim

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "verify-claim": {
      "command": "uvx",
      "args": [
        "mcp-verify-claim"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "verify-claim": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-verify-claim"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account sudo-ai-git, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 7254 servers in this category
Published to the registry more recently than 34% of the other 7254 servers in this category
Basic checks equal to or better than 100% of the other 7254 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Verify Claim safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

mcp-verify-claim

A Model Context Protocol (MCP) server that forces evidence-gated, honestly tiered claim reporting. Every claim an agent makes gets classified into an evidence tier (FACT / INFERENCE / SPECULATION / UNVERIFIED) with attached evidence — the antidote to the silent-unverified-claim failure mode ("pushed successfully", "the tests pass", "the API returned 200" — asserted without ever running the command).

Deterministic, no LLM, no network calls. Self-hostable, MCP-compatible with any agent (Claude Code, Cursor, Copilot, OpenClaw, Codex CLI).

Why it exists

The most common agent failure is not wrong reasoning — it's reporting a plausible-sounding *result that was never verified*. mcp-verify-claim installs a hard gate: no unverified claim can be reported as fact.

The pattern it fits (agent tooling that answers with evidence, not opinion)

When you give an agent access to real operations (edits, checks, rule evaluation, mutations) through MCP, the value is that it can answer with evidence instead of opinion — it ran the check, it saw the real state, it can prove what it did. But that only holds if the agent is *forced* to attach the evidence. A rules-and-checks surface ("is the module valid?", "did this state change slice apply?", "what actually changed?") is exactly the high-value case: each check produces a machine-verifiable result.

mcp-verify-claim is the gate that guarantees the agent reports the result with its evidence attached (exit code, real read-back, actual HTTP status) and cannot pass off a guess or an unrun step as truth. Pair it with any MCP surface that exposes operations, and the agent's answers become auditable, line-by-line, instead of plausible.

Tools

tier_claim(claim, evidence, verification_kind) — classify a claim into a tier + verdict (TRUST / REVIEW / DO-NOT-REPORT) + honest next-action.
check_claim(claim) — deterministic scan for fabrication/hedging signals (completion-without-artifact, "the API returned", hedge words).
report_templates() — the canonical STATUS / EVIDENCE / GAPS completion shape and the 6-step behavioral loop.
tier_definitions() — the FACT / INFERENCE / SPECULATION / UNVERIFIED definitions.

Evidence tier (the core)

Tier	Meaning	Verdict
FACT	Saw it in raw tool output (exit code, body, file read-back, HTTP status)	TRUST
INFERENCE	Deduced from facts; show the chain	REVIEW
SPECULATION	A guess; never report as truth	REVIEW
UNVERIFIED	No evidence produced	DO-NOT-REPORT

Install & run

One command (recommended) — installs from the repo, no PyPI token needed:

uv tool install git+https://github.com/sudo-ai-git/mcp-verify-claim

mcp-verify-claim # run stdio server mcp-verify-claim --http --port 8137 # or Streamable HTTP for remote use

Or with pipx: pipx install git+https://github.com/sudo-ai-git/mcp-verify-claim

Direct from source (fallback):

pip install mcp

python3 mcp_server.py

Claude Desktop / agent config

{ "mcpServers": {

"verify-claim": { "command": "mcp-verify-claim", "args": [] } }}

Example

tier_claim("Successfully deployed", evidence="", verification_kind="")

--> tier UNVERIFIED, verdict DO-NOT-REPORT signals: [high] completion claim without artifact next: go get the evidence before reporting

tier_claim("Deploy is live", evidence="origin/main SHA==local HEAD, HTTP 200", verification_kind="read_back") --> tier FACT, verdict TRUST

Part of a family

This is one of three deterministic, no-LLM agent-trust MCP servers by sudo-ai-git:

mcp-skill-sec — pre-install skill/security audit
mcp-verify-claim — evidence-gated, honestly-tiered claim reporting (this repo)
mcp-benchmark-hygiene — pytest config-leakage / eval-honesty detection

Sibling product: mcp-token-saver — token-cost proxy + analyzer for agent conversations (dedupes redundant tokens before they're billed; live-proven 74% cut). Discussion

Also in the family (a free CLI, not an MCP server): harness-audit — deterministic agent-eval / benchmark-grading hygiene audit that catches the same silent config-leakage mis-scoring class. Free lead-magnet; the same verification discipline, zero dependencies, auditable line-by-line.

License & provenance

MIT. Written by sudo-ai-git. Standalone behavioral-rigor tool; encodes no proprietary method. MCP expression of the verify-before-claim agent skill.

Official MCP Registry metadata

mcp-name: io.github.sudo-ai-git/mcp-verify-claim

Hire a custom integration

Need this connected to *your* internal system (auth, logging, security-scan pass, hosted)? Open a custom-build request. MIT reference assets are free to use either way.

MCP Verify Claim

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

mcp-verify-claim

Why it exists

The pattern it fits (agent tooling that answers with evidence, not opinion)

Tools

Evidence tier (the core)

Install & run

Claude Desktop / agent config

Example

Part of a family

License & provenance

Official MCP Registry metadata

Hire a custom integration