Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VerifyAPI — fact-check with signed receipts

NPM · @VERIFY-API/MCP · SCANNED SEP 25

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

Available components

npm · @verify-api/mcp 74
+6 this week 74 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 554 tokens (~554/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the VerifyAPI — fact-check with signed receipts MCP server?

VerifyAPI — fact-check with signed receipts runs locally as an npm package, launched with npx -y @verify-api/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @verify-api/mcp

# add to Claude Code
claude mcp add kythekitty-verifyapi -- npx -y @verify-api/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "kythekitty-verifyapi": {
      "command": "npx",
      "args": [
        "-y",
        "@verify-api/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "kythekitty-verifyapi": {
      "command": "npx",
      "args": [
        "-y",
        "@verify-api/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add kythekitty-verifyapi -- npx -y @verify-api/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kythekitty-verifyapi": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@verify-api/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add kythekitty-verifyapi --command npx --arg -y --arg @verify-api/mcp
# ~/.hermes/config.yaml
mcp_servers:
  kythekitty-verifyapi:
    command: "npx"
    args: ["-y", "@verify-api/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "kythekitty-verifyapi": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@verify-api/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add kythekitty-verifyapi -t stdio -c npx -a -y @verify-api/mcp
// mcp.json
{
  "mcpServers": {
    "kythekitty-verifyapi": {
      "command": "npx",
      "args": [
        "-y",
        "@verify-api/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +3
    • Stability: unverified → 0.23 ▲ functional
  • 13 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Sept 26 +20
    • Malware scan: pass → unverified ▼ security
    • Injection markers: unverified → pass ▲ security
    • Source repository: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Security disclosure: unverified → fail ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.1.8 → 0.1.9 functional
  • 10 Sept 26 +10
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.84 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Analysed npm/@verify-api/mcp@0.1.9

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~554 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
verify_claim ~554

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.

NameTypeReqDescription
as_ofstring–Optional 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.
freshnessstring–Optional 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). `c…
max_age_secondsnumber–Optional 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 `f…
max_wait_msnumber–Optional soft deadline in milliseconds. Default 15000. If the pipeline cannot finish in time you'll get insufficient_evidence.

No output schema declared.

No examples provided.

Common questions

What is the VerifyAPI — fact-check with signed receipts MCP server?

VerifyAPI — fact-check with signed receipts is an MCP server listed in the public MCP registry as io.github.KyTheKitty/verifyapi. Fact-check any claim with live web sources. Ed25519-signed receipts. Catches hallucinations. This page covers its npm package (@verify-api/mcp).

Is the VerifyAPI — fact-check with signed receipts MCP server safe to use?

VerifyAPI — fact-check with signed receipts scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the VerifyAPI — fact-check with signed receipts MCP server expose?

VerifyAPI — fact-check with signed receipts exposes 1 tool: verify_claim. Their descriptions and schemas cost roughly 554 tokens of context every time the server is loaded.

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

VerifyAPI — fact-check with signed receipts is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the VerifyAPI — fact-check with signed receipts MCP server under?

VerifyAPI — fact-check with signed receipts declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.