Other · Local MCP server
VerifyAPI - fact-check with signed receipts
Fact-check any claim with live web sources. Ed25519-signed receipts. Catches hallucinations.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.KyTheKitty/verifyapi- Version
- 0.1.9
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-12
- Updated
- 2026-09-12
- Publisher
- KyTheKitty (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/KyTheKitty) · how
- Website
- verify-api.dev
- Repository
- github.com/KyTheKitty/verifyapi-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @verify-api/mcp | 0.1.9 | stdio |
How to connect VerifyAPI - fact-check with signed receipts
VerifyAPI - fact-check with signed receipts runs locally from a Node.js package published to the npm registry: @verify-api/mcp version 0.1.9. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @verify-api/mcp@0.1.9. It reads these environment variables: VERIFYAPI_API_KEY (secret) and VERIFYAPI_BASE_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"verifyapi": {
"command": "npx",
"args": [
"-y",
"@verify-api/mcp@0.1.9"
],
"env": {
"VERIFYAPI_API_KEY": "<secret>",
"VERIFYAPI_BASE_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Verify ApiAI claim verification MCP endpoint with x402 payments and stealth web fetch. | Remote · HTTP, SSELive check: ✓ handshake |
| Verify China Supplier | Supplier CheckVerify a Chinese supplier before you pay: company identity, status, risk signals. x402 per call. | Remote · HTTPLive check: ✗ no handshake |
| Verify MCPOffline Ed25519 verification of signed receipts, bundles, and trust artifacts. | Local · stdio |
| verify-atomSigned proof of web observations for AI agents: Ed25519 proof packets for any URL. | Local · stdio |
| VerifyAXEvaluate, benchmark, and simulate AI agents on the VerifyAX agent-evaluation platform. | Remote & Local · HTTP, stdioLive check: sign-in required |
| verifyfirstLook up what your verification method cannot see: 48 failures that report success. | Local · stdio |
| VerifyMCPIndependent trust scores, tool surfaces and change history for MCP servers. | Remote · HTTPLive check: ✓ handshake |
| VerikoValida y consulta transferencias SPEI mediante la API oficial de Veriko. | Local · stdio |