mcp server
Verifi
Get a real human to verify, decide, or improve an AI agent's work.
Description as published by the maintainer. Source
- version 2.0.0
- active
active — Registry entry last updated 2026-07-17.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_verify(verify_id)- Poll until ready or failed. Honor retry_after_seconds while processing. Required: verify_id.
unlock_verify(verify_id, payment_signature)- 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. Required: verify_id.
verifi_info- Service description, pricing, and rules.
verify_claim(claim, intent, agent_id, callback_url, payment_signature)- 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. Required: intent, claim, agent_id.
Last successful function declaration observed on . Source: https://verifi.cloud/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://verifi.cloud/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 2.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-17 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-17 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | verifi.cloud | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | verifi.cloud |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json