VerifyAPI — fact-check with signed receipts

Name: VerifyAPI — fact-check with signed receipts
Author: KyTheKitty

by KyTheKittyversion 0.1.9i★ –iRuns on your computer

Registry nameio.github.KyTheKitty/verifyapi

Install

Overview

Description from the maker (original English)

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

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: Other
You need to fill in: VERIFYAPI_API_KEY

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).
You fill in yourself: VERIFYAPI_API_KEY, VERIFYAPI_BASE_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx 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": {
    "verifyapi": {
      "command": "npx",
      "args": [
        "-y",
        "@verify-api/mcp"
      ],
      "env": {
        "VERIFYAPI_API_KEY": "your-value",
        "VERIFYAPI_BASE_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add verifyapi --env VERIFYAPI_API_KEY=your-value --env VERIFYAPI_BASE_URL=your-value -- npx -y @verify-api/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "verifyapi": {
      "command": "npx",
      "args": [
        "-y",
        "@verify-api/mcp"
      ],
      "env": {
        "VERIFYAPI_API_KEY": "your-value",
        "VERIFYAPI_BASE_URL": "your-value"
      }
    }
  }
}

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": {
    "verifyapi": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@verify-api/mcp"
      ],
      "env": {
        "VERIFYAPI_API_KEY": "your-value",
        "VERIFYAPI_BASE_URL": "your-value"
      }
    }
  }
}

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.

Values you fill in

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

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 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account KyTheKitty, 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 Otheri

More stars than 0% of the other 32505 servers in this category
Published to the registry more recently than 42% of the other 32505 servers in this category
Basic checks equal to or better than 100% of the other 32505 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 VerifyAPI — fact-check with signed receipts 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?

You need to fill in: VERIFYAPI_API_KEY

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 (0.1.9) 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 Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, topo^alpin

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

topo^alpin

by topoalpin.app

Avalanche bulletins and mountain weather forecasts for any place in the Alps.

Runs in the cloudUpdated today

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.

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

Variable	Required	Default	Description
`VERIFYAPI_API_KEY`	No	(unset = trial)	Your VerifyAPI key (`csk_live_...`). Get one free at https://verify-api.dev/signup
`VERIFYAPI_BASE_URL`	No	`https://api.verify-api.dev`	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.

Built by

Circuit Savers LLC — Wausau, Wisconsin.

License

MIT

VerifyAPI — fact-check with signed receipts

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

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 Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

topo^alpin

README from the maker

VerifyAPI MCP Server

Quick install (Claude Desktop / Cursor / Cline / any MCP client)

The one tool: verify_claim

Why signed receipts?

Pricing

Example use cases

Environment variables

Programmatic API (skip MCP, call directly)

Links

Built by

License

The one tool: `verify_claim`