Skip to content
External endpointresponds

Verifi

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

Endpoint URL
https://verifi.cloud/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:08 AM UTC
Check
MCP initialize · 8s limit
Latency
538 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
cloud.verifi/human-verification

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
verifi
Version
2.0.0
Capability keys
experimental, prompts, resources, tools
Tool names
verify_claim, get_verify, unlock_verify, verifi_info
Instructions excerpt

Verifi sends your claim to a real human who answers accept, reject, or a refined free-text correction. Every chain has two gates. Use verify_claim with callback_url, then use unlock_verify when the callback reports ready. If no callback is available, poll get_verify. Every chain is paid: 0.10 USDC entry, then 2.90 USDC unlock. There is no free human work. x402-aware MCP clients can sign and repeat paid tool calls automatically. Generic clients can pass the signed authorization as payment_signature. Pass callback_url to receive ready or failed events without an active polling loop. No account or API key is required. Never send a private key. A human reads every request: do not spam.

Reported Aug 17, 2026, 05:08 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 438ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 759ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 609ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 538ms