VerifyAPI MCP Server
Click 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., "@VerifyAPI MCP Server verify Python 3.13 was released in October 2024"
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.
VerifyAPI MCP Server
Fact-check any claim before you act on it. One tool. Live web sources. Cryptographically signed receipts.
What it does: VerifyAPI is a Model Context Protocol server that verifies factual claims against live web sources and returns a citable verdict — including the source URL, published date, a verbatim quote, and an Ed25519-signed receipt so downstream systems can prove the check actually happened.
When to use it: Any time your agent is about to act on a factual claim it can't cite. Prices, dates, versions, quotes, statistics, product specs, event outcomes. If getting it wrong would cost time, money, or trust — verify first.
Quick install (Claude Desktop / Cursor / Cline / any MCP client)
{
"mcpServers": {
"verifyapi": {
"command": "npx",
"args": ["-y", "@verify-api/mcp@latest"],
"env": {
"VERIFYAPI_API_KEY": "csk_live_..."
}
}
}
}No API key? Leave VERIFYAPI_API_KEY unset for the free trial (limited to 3 calls per IP per 24h, signed receipts included). Get a free key at https://verify-api.dev/signup — no credit card required.
Related MCP server: fact-checker
The one tool: verify_claim
Input:
{
"claim": "Python 3.13 was released in October 2024."
}Output:
{
"verdict": "supported",
"confidence": 0.99,
"source_url": "https://docs.python.org/3/whatsnew/3.13.html",
"exact_quote": "Python 3.13 was released on October 7, 2024.",
"reasoning": "Multiple authoritative sources confirm...",
"receipt": {
"jws": "eyJhbGci...",
"kid": "pQAd73zRp9Xq9Y5U"
}
}Verdicts: supported, contradicted, unverifiable. Every supported/contradicted verdict comes with a JWS receipt signed by keys served at https://api.verify-api.dev/.well-known/jwks.json.
Why signed receipts?
Because "the AI checked" is not the same as "the AI verified." A signed receipt lets a downstream system — compliance auditor, user, another agent, a smart contract — cryptographically prove that a specific claim was verified against a specific source at a specific time by VerifyAPI's known public key. It's the difference between saying "trust me" and handing over a notarized document.
Pricing
Free trial: no signup, no card. Limited to 3 calls per IP per 24h. Includes signed receipts.
With API key: $0.02 per verified claim. Unverifiable / out-of-scope calls are free (you don't pay for "I couldn't find enough evidence").
Freshness tiers: standard verification $0.02, real-time (fresh-fetch) $0.05.
Auto top-up: save a card, set a threshold, keep flowing.
POST /v1/balance/autorefill.
Example use cases
LangChain / LlamaIndex agents: wrap verify_claim as a Tool. Have your agent call it before returning any factual answer.
Cursor / Cline coding agents: verify version numbers, API existence, deprecation status before writing imports.
Claude Desktop workflows: "Verify this quote is real before I put it in the deck."
Multi-agent systems: pass receipts between agents to prove groundedness up the chain.
Compliance-sensitive automation: keep the JWS receipts as audit trail for every factual decision the agent made.
Environment variables
Variable | Required | Default | Description |
| No | (unset = trial) | Your VerifyAPI key ( |
| No |
| Override the API base URL. Useful for self-hosting or testing. |
Programmatic API (skip MCP, call directly)
curl -X POST https://api.verify-api.dev/v1/verify \
-H "Authorization: Bearer csk_live_..." \
-H "Content-Type: application/json" \
-d '{"claim": "Bitcoin ETFs were approved by the SEC in January 2024."}'Full OpenAPI spec: https://api.verify-api.dev/openapi.json
x402 payment support built in — see https://verify-api.dev/agents.txt for the agent-native discovery manifest.
Links
Website: https://verify-api.dev
API docs: https://verify-api.dev/docs
Signup (free, no card): https://verify-api.dev/signup
MCP Registry: https://registry.modelcontextprotocol.io/v0/servers/io.github.KyTheKitty/verifyapi
MCP source: https://github.com/KyTheKitty/verifyapi-mcp
Backend source (Fastify service, Terraform, receipts pipeline): https://github.com/KyTheKitty/verifyapi
Built by
Circuit Savers LLC — Wausau, Wisconsin.
License
MIT
Available Tools
1 toolverify_claimA
Fact-check a single factual claim against live web sources. Returns one of supported, refuted, insufficient_evidence, or out_of_scope, with confidence, source_url, published_date, and a verbatim exact_quote from that source. Every response is signed with an Ed25519 receipt (verifiable at https://api.verify-api.dev/.well-known/jwks.json).
Pricing (see /v1/pricing): $0.02 base per supported/refuted verdict; recent tier (<24h old cache) 2x; fresh tier (cache bypassed, guaranteed live) 5x. insufficient_evidence, out_of_scope, malformed, and cache hits within your account are free. Use freshness="cached" (default) for maximum savings; freshness="fresh" when you need a guaranteed-current answer (breaking news, live standings, latest release); set max_age_seconds for HTTP Cache-Control-style bounded staleness.
Running without an API key uses the FREE TRIAL (3 calls per IP per 24h, cached tier only, still returns signed receipts). Set VERIFYAPI_API_KEY in the mcpServers env block to remove the limit and unlock the recent/fresh tiers. Get a key at https://verify-api.dev/signup (no credit card).
Use this before committing to any factual claim you are not sure about — dates, statistics, prices, attributions, event outcomes.
Inputs: claim (required), as_of, freshness, max_wait_ms, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion between tools. The tool's purpose is clearly and uniquely defined, so an agent can unambiguously select it.
The lone tool name `verify_claim` follows a clear verb_noun pattern. With only one tool, naming is perfectly consistent and predictable.
The server exposes exactly one tool, which is below the typical 3-15 range but not trivial. The tool is substantial and directly serves the server's narrow fact-checking purpose, so the low count is reasonable, though slightly thin.
The domain is fact-checking a single claim, and the tool covers that end-to-end: it accepts a claim, returns a verdict with confidence, source, date, exact quote, and a signed receipt, and offers freshness controls. There are no obvious missing operations for this stated purpose.
Related MCP Connectors
Real-time fact-check, citation verification, and source-freshness for AI agents.
One-stop claim verification for AI agents: verdicts with confidence, evidence, signed receipts.
Check whether a real-world fact can be verified before an agent acts on it. Free, no auth.
Fact-check receipts: search published claim verdicts with cited evidence, or verify a new claim.
Related MCP Servers
- AlicenseAqualityCmaintenanceVerifies factual claims against live sources and returns a verdict, confidence score, and citations for any agent to use before stating uncertain facts.61MIT
- AlicenseNot gradedqualityCmaintenanceFacilitates fact-checking claims by searching the web and returning evidence snippets, with pay-per-call via x402 micropayments on Base L2.MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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 AI agents to verify claims against evidence through MCP tools, returning approved, rejected, or needs_review verdicts with replayable receipts.MIT