Verifi MCP server

Which servers in the official MCP registry are Verifi's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to Verifi

Whose server it is

Registry namecloud.verifi/human-verificationverified in the MCP registry

The registry name sits under verifi.cloud. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13

Stateanswerschecked 2026-10-13
Tools4
Server calls itselfverifi
Server version3.0.1
Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 182 ms.

Tools it offers4 tools · read 2026-10-13

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…
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…
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…
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, authentication (none, only a wallet address), the live price terms (0.10 EUR admission, then…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "human-verification": {
      "type": "http",
      "url": "https://verifi.cloud/mcp"
    }
  }
}

OpenAPI spec

5 paths, read 2026-10-13. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.