VerifyAPI — fact-check with signed receipts MCP Server

by kythekitty Your server? Claim it

local only

VerifyAPI — fact-check with signed receipts runs on your own machine — the client starts it, so there is no endpoint to ping. 307 installs a week from npm.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 586 · avg 38 · +293% w/w

a month agotoday

307

Installs / week

npm · @verify-api/mcp

—

Stars

on GitHub

—

Last commit

0 releases in 90 days

—

License

language unknown

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add verifyapi -- npx -y @verify-api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "verifyapi": {
      "args": [
        "-y",
        "@verify-api/mcp"
      ],
      "command": "npx"
    }
  }
}

~/.codex/config.toml

[mcp_servers.verifyapi]
command = "npx"
args = ["-y", "@verify-api/mcp"]

.cursor/mcp.json

{
  "mcpServers": {
    "verifyapi": {
      "args": [
        "-y",
        "@verify-api/mcp"
      ],
      "command": "npx"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "verifyapi": {
      "args": [
        "-y",
        "@verify-api/mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: VERIFYAPI_API_KEY (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.). The author declared them in the registry entry; get the values from the project itself.

Alternatives to VerifyAPI — fact-check with signed receipts

same job, measured the same way

Ccs MCP Server

by dshcorrectover

Runtime verification for agent tool calls: Ed25519 signed receipts, fail-closed RCE/SSRF checks.

552 installs/wk local only

Trinity Research

by humanified

Fact-check claims against live web sources: verdict, consensus, cited sources, PII redaction.

4 tools answering

Verity

by clawdio777

Real-time fact-checking MCP. Verifies claims against live sources with structured verdicts.

48 installs/wk local only

Verify MCP

by tomjwxf

Offline Ed25519 verification of signed receipts, bundles, and trust artifacts.

62 installs/wk local only

Verify MCP

by scopeblind

Offline Ed25519 verification of signed receipts, bundles, and trust artifacts.

local only

Veritasacta Verify

by tomjwxf

Offline receipt verifier. Ed25519 signature verification without contacting any server.

3 602 installs/wk local only

Agent Receipts

by dropwatchhq

Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.

3 tools answering

Security Preflight

by jdhart81

Static MCP, source-code and injection-indicator checks with redacted signed receipts.

5 tools answering

VerifyAPI — fact-check with signed receipts — questions

Answers built from our own checks of this server.

Why is there no uptime for VerifyAPI — fact-check with signed receipts?

VerifyAPI — fact-check with signed receipts runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @verify-api/mcp was installed 307 times last week.

Is VerifyAPI — fact-check with signed receipts still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect VerifyAPI — fact-check with signed receipts?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @verify-api/mcp straight from npm; nothing to host, nothing to sign up for.

How many people use VerifyAPI — fact-check with signed receipts?

The npm package @verify-api/mcp was installed 307 times in the last week. Week over week that is +293%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.