mcpbeat Sign in

Verifi MCP Server

answering

Verifi is answering right now. Last checked 3 min ago. It exposes 4 tools. Last commit 21 Oct 2026.

Get a real human to verify, decide, or improve an AI agent's work. Pay per review via x402 on Base.

Uptime history 91 days of history · worst day 98%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
129 ms
Response time
average over 24h
0
Stars
last commit 21 Oct 2026

What changed 10

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

19 Oct a tool description was rewritten verifi_info
1 Oct 4 tool descriptions were rewritten5 times that day get_verify, unlock_verify, verifi_info and 1 more
1 Oct a tool changed version2 times that day
10 Aug 2 tool descriptions were rewritten unlock_verify, verify_claim
and 2 more, back to 10 August 2026

What the code does

We read the source, 2 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Sends data to a third-party sink core/notify.py:16
_API = "https://api.telegram.org/bot{token}/{method}"

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

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 3 min ago.

run in your terminal
claude mcp add human-verification --transport http https://verifi.cloud/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "human-verification": {
      "type": "http",
      "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
Read the current state of a verification. Free, never reveals a locked answer. verify_id: the id returned by verify_claim. Returns status "processing" (a human is working: wait retry_after_seconds, or rely on the callback), "ready" (an answer exists; service_window shows the window that applied and the exact unlock price, then call unlock_verify), "failed" (no answer within 24 hours; failure explains the reason and the free next admission), or "completed" (the answer is unlocked and included). Use it as a recovery path when no callback is set.
verify_claim
Ask a real human to verify, decide on, or improve something before your agent acts. Use it when a wrong answer is costly: a customer message, a fact the model is unsure of, an approval, or a matter of taste. A person reads the intent and the claim and answers accept, reject, or a refined answer with an explanation. This call is gate 1: it costs 0.10 EUR (paid on Base via x402) and returns a payment requirement first if unpaid; reading that requirement is free and shows every later price. 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
Unlock a ready chain and return the human result. The price was decided when the human answered: the SLA amount inside the SLA window, the grace amount after it, always in the asset the admission was paid in. get_verify shows it as service_window.unlock_amount before you pay. 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
Describe Verifi before using it: what it does, how to pay, and the current price terms. Free and needs no arguments. Returns the service summary, how payment works (no sign-in: each paid call carries an x402 payment), the live price terms (0.10 EUR admission, then 2.90 EUR if a human answers within 60 minutes or 1.45 EUR within 24 hours, with the asset amounts and exchange rate used), the callback events, and the rules for agents. Call it once to plan; the payment requirement returned by verify_claim is authoritative.

Endpoints

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

Alternatives to Verifi

same job, measured the same way
Agent Embassy
by tacticalnoot

Agents pay for work and prove it. Verified checks $0.15, recovery $1.00. USDC on Base via x402.

25 tools answering
Send Decision
by inboxpolicy

Send-decision email verification: agents get send/review/avoid with evidence, pay-per-call via x402.

answering
Deliverd
by davidpreid

Give any AI agent a way to ask a person — for approval, a decision, an answer or a review.

answering
Agents
by vevang

Hire Vevang's AI agents, pay-per-call in USDC on Base via x402: video, visibility, verify, extract

6 tools answering
Micropay Test Suite
by netlify-micropay-test-suite

Verify your agent's x402 payment flow for free on Base Sepolia testnet before real money moves.

1 tools answering
The Clubhouse
by therealmrfunguy

Play chess, pool and poker for real money against AI agents and humans on Base. Pays via x402.

52 installs/wk local only
402scrape
by redsoukas

Fetch a webpage and get clean, agent-ready Markdown. Paid per call via x402 (USDC on Base).

34 installs/wk local only
Gatewerk
by gatewerk

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

52 installs/wk local only

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 129 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 in the form 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 129 ms on average, which is faster than 86% 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.
Is Verifi open source?
The code is open source: it is published under the MIT licence, written in Python, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at verifi.cloud, which runs on its operator's own terms.