Skip to content

Verifi MCP server

cloud.verifi/human-verificationverifi.cloudstreamable-httpv3.0.1Scanned

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

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Verifi MCP server can do

The Verifi MCP server is published by verifi.cloud, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: verify_claim and unlock_verify), but cannot delete data. 2 tools only read.

1 tool can send data out of your system (verify_claim).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 3.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • unlock_verifyUnlock a ready chain and return the human result.No findings

    Why it is in this group

    • The name "unlock_verify" says "unlock": a word for a change.
    Description, as the server wrote it
    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.
  • verify_claimAsk a real human to verify, decide on, or improve something before your agent acts.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.callback_url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.
Only reads 2Show 2 read-only tools
  • get_verifyRead the current state of a verification.No findings

    Why it is in this group

    • The name "get_verify" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • verifi_infoDescribe Verifi before using it: what it does, how to pay, and the current price terms.No findings

    Why it is in this group

    • The description's first verb is "describe": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:32 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://verifi.cloud/mcp: tools/list returned 4 tools to an anonymous client, including verify_claim (write), unlock_verify (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 3.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http human-verification https://verifi.cloud/mcp
claude mcp add --transport http human-verification https://verifi.cloud/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__human-verification__get_verify",
      "mcp__human-verification__verifi_info"
    ],
    "ask": [
      "mcp__human-verification__verify_claim",
      "mcp__human-verification__unlock_verify"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as human-verification. Review it before you use it.

Capability tags behind 1 rule
  • mcp__human-verification__verify_claim outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/cloud.verifi/human-verification/verify?hash=e8f235bcf3ff7003cc320c4f26f9ea80c4cfd52a2374668d3580b3eee7104961" | jq -e '.changed == false'

Pinned hash e8f235bcf3ff, from Nov 10, 2026, 08:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/cloud.verifi/human-verification/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for cloud.verifi/human-verification
[![Anlyon Radar](https://radar.anlyon.com/badge/cloud.verifi/human-verification.svg)](https://radar.anlyon.com/servers/cloud.verifi/human-verification)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:46 UTC.

Verifi MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Verifi MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Verifi MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Verifi MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Verifi MCP server have?

4 tools: 2 write, 2 read. verify_claim, unlock_verify, get_verify and verifi_info.

Does the Verifi MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Verifi MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): verify_claim.

Has the Verifi MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.