Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Verifi

REMOTE · VERIFI.CLOUD

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

Available components

0 this week 74 Trust /100

Last scanned (16 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 940 tokens (~235/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 20 Oct 26 0
    • Tool “verifi_info” rewrote its description, which is the text the model reads security
    • Schema quality: excellent → good functional
  • 1 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_verify” rewrote its description, which is the text the model reads security
    • Tool “verify_claim” rewrote its description, which is the text the model reads security
    • Tool “unlock_verify” rewrote its description, which is the text the model reads security
    • Tool “verifi_info” rewrote its description, which is the text the model reads security
    • Schema quality: 126 → 232 ▼ functional
    • Schema quality: 126 → 146 ▼ functional
    • Schema quality: good → excellent functional
    • Server version: 3.0.0 → 3.0.1 functional
    • Server version: 2.0.0 → 3.0.0 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://verifi.cloud/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=verifi.cloud CN=YE1,O=Let's Encrypt,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA384 594e7afa49f9b9a51e905f46d2c758170f3
SANs: verifi.cloud, www.verifi.cloud
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of verifi.cloud. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cloud. DS published 7041 13 Verified
verifi.cloud. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://verifi.cloud/mcp Verified 200
http (plaintext) http://verifi.cloud/mcp HTTPS enforced 301 https://verifi.cloud/mcp
MCP tools · 4 exposed · ~751 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_verify ~147

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.

NameTypeReqDescription
verify_idstringyes–

No output schema declared.

No examples provided.

unlock_verify ~132

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.

NameTypeReqDescription
payment_signature–––
verify_idstringyes–

No output schema declared.

No examples provided.

verifi_info ~142

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

verify_claim ~330

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.

NameTypeReqDescription
agent_idstringyes–
callback_url–––
claimstringyes–
intentstringyes–
payment_signature–––

No output schema declared.

No examples provided.

Install

How do I install the Verifi MCP server?

Verifi is a hosted endpoint at https://verifi.cloud/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · verifi.cloud

# add to Claude Code
claude mcp add --transport http cloud-verifi-human-verification 'https://verifi.cloud/mcp'
Common questions

What is the Verifi MCP server?

Verifi is an MCP server listed in the public MCP registry as cloud.verifi/human-verification. Get a real human to verify, decide, or improve an AI agent's work. Pay per review via x402 on Base. This page covers its hosted endpoint (https://verifi.cloud/mcp).

Is the Verifi MCP server safe to use?

Verifi scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Verifi MCP server expose?

Verifi exposes 4 tools: verify_claim, get_verify, unlock_verify, verifi_info. Their descriptions and schemas cost roughly 751 tokens of context every time the server is loaded.

Does the Verifi MCP server require authentication?

No. We connected to Verifi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Verifi MCP server still maintained?

Verifi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Verifi MCP server?

VerifyMCP ran 12 checks on Verifi, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Verifi: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.