VerifyAPI — fact-check with signed receipts

Registre officiel Sécurité

Fact-check any claim with live web sources. Ed25519-signed receipts. Catches hallucinations.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @verify-api/mcp
Claude Code
claude mcp add verifyapi-fact-check-with-signed-receipt -e 'VERIFYAPI_API_KEY=<your verifyapi_api_key>' -e 'VERIFYAPI_BASE_URL=<VERIFYAPI_BASE_URL>' -- npx -y @verify-api/mcp@0.1.9
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "verifyapi-fact-check-with-signed-receipt": {
            "command": "npx",
            "args": [
                "-y",
                "@verify-api/mcp@0.1.9"
            ],
            "env": {
                "VERIFYAPI_API_KEY": "<your verifyapi_api_key>",
                "VERIFYAPI_BASE_URL": "<VERIFYAPI_BASE_URL>"
            }
        }
    }
}

Variables d'environnement

  • VERIFYAPI_API_KEY secret Your 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_URL Override the API base URL. Defaults to https://api.verify-api.dev.

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. VerifyAPI MCP Server
  2. Quick install (Claude Desktop / Cursor / Cline / any MCP client)
  3. The one tool: verify_claim
  4. Why signed receipts?
  5. Pricing
  6. Example use cases
  7. Environment variables
  8. Programmatic API (skip MCP, call directly)
  9. Links
  10. Built by
  11. License

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.

Built by

Circuit Savers LLC — Wausau, Wisconsin.

License

MIT

Questions fréquentes

Qu'est-ce que VerifyAPI — fact-check with signed receipts ?

Fact-check any claim with live web sources. Ed25519-signed receipts. Catches hallucinations.

Comment installer VerifyAPI — fact-check with signed receipts ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add verifyapi-fact-check-with-signed-receipt -e 'VERIFYAPI_API_KEY=<your verifyapi_api_key>' -e 'VERIFYAPI_BASE_URL=<VERIFYAPI_BASE_URL>' -- npx -y @verify-api/mcp@0.1.9. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour VerifyAPI — fact-check with signed receipts ?

Oui. Il attend VERIFYAPI_API_KEY, à renseigner dans sa configuration.

VerifyAPI — fact-check with signed receipts est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient VerifyAPI — fact-check with signed receipts ?

Il est publié par KyTheKitty. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.