mcpField
V
VerifyAPI

VerifyAPI

VerifiedFeaturedLocal
verify-api.devSearch0Updated 7w ago

About VerifyAPI

VerifyAPI is an MCP server for agents and automation that checks factual claims against live web sources. It returns a verdict with source details and a signed receipt that can be retained as evidence of the check.

Key features

  1. 01Live web claim verification
  2. 02Supported, contradicted, or unverifiable verdicts
  3. 03Source URL, date, and exact quote
  4. 04Ed25519-signed verification receipts

Use cases

  1. 01Check prices, versions, dates, or statistics before acting
  2. 02Verify API status before generating code
  3. 03Keep signed evidence for compliance reviews
  4. 04Pass verification receipts between agents

MCP support

VerifyAPI exposes the `verify_claim` tool to MCP clients. It accepts a claim and returns a verdict, source information, and—when supported or contradicted—a signed receipt.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"verifyapi": {
"command": "npx",
"args": [
"-y",
"@verify-api/mcp"
],
"env": {
"VERIFYAPI_API_KEY": "<VERIFYAPI_API_KEY>",
"VERIFYAPI_BASE_URL": "<VERIFYAPI_BASE_URL>"
}
}
}
}
Run commandnpx -y @verify-api/mcp
Environment variables to set
VERIFYAPI_API_KEYSecretYour VerifyAPI key (csk_live_...). Get one free at https://verify-api.dev/signup — no card required. Unset = free trial (3 calls per IP per 24h, cached tier, signed receipts still included).
VERIFYAPI_BASE_URLOverride the API base URL. Defaults to https://api.verify-api.dev.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@verify-api/mcp0.1.9

Tools

1

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
as_ofstringNoOptional ISO date (YYYY-MM-DD). Use for time-sensitive facts, e.g. prices or standings.
claimstringYesA single factual claim, ideally under 300 characters. If you have multiple claims, call verify_claim once per claim.
freshnessenumNoOptional freshness tier. `fresh` bypasses both caches and runs the full pipeline (5x price) — use when you need a guaranteed-current answer (breaking news, live standings, latest release version). `cached` (default) honors both cache tiers. See GET /v1/pricing for exact multipliers. (Ignored in trial mode — trial is cached-only.)fresh | cached
max_wait_msnumberNoOptional soft deadline in milliseconds. Default 15000. If the pipeline cannot finish in time you'll get insufficient_evidence.
max_age_secondsnumberNoOptional maximum age (in seconds) for a cached verdict. Acts like HTTP Cache-Control: max-age. Values below 3600 trigger the `fresh` tier; below 86400 trigger the `recent` tier (2x price). If both `freshness` and `max_age_seconds` are set, `freshness` wins. (Ignored in trial mode.)

Details

From the project README

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.

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

VariableRequiredDefaultDescription
VERIFYAPI_API_KEYNo(unset = trial)Your VerifyAPI key (csk_live_...). Get one free at https://verify-api.dev/signup
VERIFYAPI_BASE_URLNohttps://api.verify-api.devOverride 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

Built by

Circuit Savers LLC — Wausau, Wisconsin.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.