mcpbeat

Verifi MCP Server

cloud.verifi/human-verification
answering

Verifi is answering right now. Last checked 3 min ago. It exposes 4 tools.

Get a real human to verify, decide, or improve an AI agent's work.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
136 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add human-verification --transport http https://verifi.cloud/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "human-verification": {
      "url": "https://verifi.cloud/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.human-verification]
url = "https://verifi.cloud/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "human-verification": {
      "url": "https://verifi.cloud/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "human-verification": {
      "url": "https://verifi.cloud/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify
get_verify
Poll until ready or failed. Honor retry_after_seconds while processing.
verify_claim
Ask a real human to verify a claim. intent: what your agent is trying to do (max 2000 chars). claim: the claim a human should verify (max 4000 chars). agent_id: your wallet address (0x + 40 hex). Grants 5 free verifies. callback_url: optional HTTPS endpoint for verify.ready or verify.failed. Use it to avoid an active polling loop; retain verify_id for recovery. payment_signature: optional manual compatibility input. Standard x402-aware MCP clients send the signed payment through request metadata automatically. Returns status "processing" with a verify_id. Prefer callback_url, or poll get_verify at the returned interval until status is "ready" or "failed". If ready, call unlock_verify. Only one active verify per agent_id at a time.
unlock
unlock_verify
Pass gate 2 for a ready chain and return the human result. The first five chains per wallet are free at both gates. After that, omit payment_signature first. Standard x402-aware MCP clients handle the payment request and retry through MCP metadata automatically. Generic clients can pass the resulting x402 signature manually. Never pass a private key.
verifi
verifi_info
Service description, pricing, and rules.

Endpoints

URLTransportStateLatencyChecked
https://verifi.cloud/mcp streamable-http answering 160 ms 3 min ago

Verifi — questions

Answers built from our own checks of this server.

What can Verifi do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_verify, unlock_verify, verifi_info, verify_claim. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Verifi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 136 ms. The bar chart above shows every period we have measured.
How do I connect Verifi?
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 is a remote server, so there is nothing to install — the client connects to the address.
Does Verifi need an API key?
No. Verifi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Verifi?
It answers our handshake in 136 ms on average, which is faster than 76% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.