# VerifyAPI — fact-check with signed receipts (npm · @verify-api/mcp)

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

- Trust score: 74/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `@verify-api/mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/kythekitty-verifyapi/verify-api-mcp.md), [page](https://verifymcp.io/servers/kythekitty-verifyapi/verify-api-mcp)

## Channel facts

- Registry: `npm`
- Package: `@verify-api/mcp`
- Version: `0.1.9`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add kythekitty-verifyapi -- npx -y @verify-api/mcp
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "kythekitty-verifyapi": {
      "command": "npx",
      "args": [
        "-y",
        "@verify-api/mcp"
      ]
    }
  }
}
```

### Codex

```bash
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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kythekitty-verifyapi --command npx --arg -y --arg @verify-api/mcp
```

### Hermes

```yaml
mcp_servers:
  kythekitty-verifyapi:
    command: "npx"
    args: ["-y", "@verify-api/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "kythekitty-verifyapi": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@verify-api/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add kythekitty-verifyapi -t stdio -c npx -a -y @verify-api/mcp
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 74, +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.

### 2026-09-22 (score 73, +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.

### 2026-09-20 (score 72, +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.

### 2026-09-19 (score 71, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-13 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-12 (score 53, +20)

- [security regression] Malware scan: pass → unverified
- [security improvement] Injection markers: unverified → pass
- [security improvement] 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.
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] 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

### 2026-09-10 (score 33, +10)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.84

## MCP tools (1)

### `verify_claim` (~554 tokens)

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.

Input parameters:

- `as_of` (string): Optional ISO date (YYYY-MM-DD). Use for time-sensitive facts, e.g. prices or standings.
- `claim` (string, required): A single factual claim, ideally under 300 characters. If you have multiple claims, call verify_claim once per claim.
- `freshness` (string): 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_seconds` (number): 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_ms` (number): Optional soft deadline in milliseconds. Default 15000. If the pipeline cannot finish in time you'll get insufficient_evidence.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/kythekitty-verifyapi/verify-api-mcp#diagnostics

## Score history

- 2026-09-25: 74
- 2026-09-24: 74
- 2026-09-23: 73
- 2026-09-22: 73
- 2026-09-21: 72
- 2026-09-20: 72
- 2026-09-19: 71
- 2026-09-18: 68
- 2026-09-17: 68
- 2026-09-16: 68
- 2026-09-15: 68
- 2026-09-14: 68
- 2026-09-13: 68
- 2026-09-12: 53
- 2026-09-11: 33
- 2026-09-10: 33
- 2026-09-09: 23

## 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.

## Links

- npm package: https://www.npmjs.com/package/@verify-api/mcp
- Socket report: https://socket.dev/npm/package/@verify-api/mcp
- Repository: https://github.com/KyTheKitty/verifyapi-mcp
- Website: https://verify-api.dev/
- Changelog RSS feed: https://verifymcp.io/servers/kythekitty-verifyapi/verify-api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/kythekitty-verifyapi/verify-api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/kythekitty-verifyapi/verify-api-mcp