mcpbeat Sign in

Verifi MCP Server

answering

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

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

Uptime history 48 days of history · worst day 98%
48 days agonow
100.0%
Uptime 24h
92 of 92 checks
4
Tools
read from the server
151 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 10 August 2026. No other catalogue keeps this.

10 Aug 2 tool descriptions were rewritten unlock_verify, verify_claim

Nothing serious here today

Today is the operative word: we check Verifi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 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). Signs the x402 payments. 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. This gate costs 2.90 USDC. 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 109 ms 1 min ago

Alternatives to Verifi

same job, measured the same way
I
ProofStream
by proofstreamai

Dispatch a human verifier to physically verify anything in the real world. For AI agents.

25 installs/wk local only
AgentGate
by agentkitai

Human-in-the-loop approval gateway for AI agents over MCP: request, decide, approve.

31 installs/wk local only
HumanOps
by thepianistdirector

MCP server for AI agents to dispatch real-world tasks to verified human operators

24 installs/wk local only
Gatewerk
by gatewerk

The open-source review layer for AI agents. Work done for humans is decided by humans.

32 installs/wk local only
Callable
by ccstt-dev

API for AI agents to delegate tasks to real humans.

3 tools answering
ROO$TER Agent Economy — Hire Humans to Post
by roosteragents

AI agents hire verified human creators to post on real social accounts.

7 tools answering
Marutap
by marutap

Agent requests a purchase, the human taps approve, the agent gets a card scoped to it.

7 tools answering
NeedHuman
by mariusaure

Human-as-a-Service for AI agents. Delegate tasks that need a real human, get results via API.

40 installs/wk 3 tools answering

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 92 of 92 checks got a reply (100.0%), average response time 151 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 151 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.