verifi

endpoint

https://verifi.cloud/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is verifi live?

Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.

Is verifi free to use?

Yes — the hub reached it with no key and no payment.

What tools does verifi have?

4 tools: verify_claim, unlock_verify, verifi_info, get_verify.

Is verifi safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• verify_claim sends messages unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344454647

  {
    "type": "object",
    "title": "verify_claimArguments",
    "required": [
      "intent",
      "claim",
      "agent_id"
    ],
    "properties": {
      "claim": {
        "type": "string",
        "title": "Claim"
      },
      "intent": {
        "type": "string",
        "title": "Intent"
      },
      "agent_id": {
        "type": "string",
        "title": "Agent Id"
      },
      "callback_url": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Callback Url",
        "default": null
      },
      "payment_signature": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Payment Signature",
        "default": null
      }
    }
  }

  arguments 47 lines copy
• unlock_verify moves money unknown never probed

  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.

  mcp-tool

  12345678910111213141516171819202122232425

  {
    "type": "object",
    "title": "unlock_verifyArguments",
    "required": [
      "verify_id"
    ],
    "properties": {
      "verify_id": {
        "type": "string",
        "title": "Verify Id"
      },
      "payment_signature": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Payment Signature",
        "default": null
      }
    }
  }

  arguments 25 lines copy
• verifi_info reads unknown never probed

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "verifi_infoArguments",
    "properties": {}
  }

  arguments 5 lines copy
• get_verify reads unknown 22h ago

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "title": "get_verifyArguments",
    "required": [
      "verify_id"
    ],
    "properties": {
      "verify_id": {
        "type": "string",
        "title": "Verify Id"
      }
    }
  }

  arguments 13 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.