Connect verifi and your agent gets 4 tools, among them get_verify, unlock_verify, verifi_info. It answers at https://verifi.cloud/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 1 of 1 times since 19 October 2026; the last check, on 19 October 2026, succeeded.
MCP server at verifi.cloud, verified by introspection: 4 tools exposed.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_verify | 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 answ Inputs: verify_id |
unlock_verify | 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_ Inputs: verify_id, payment_signature |
verifi_info | 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, authentication (none, only a wallet address), the live price terms (0.10 EUR admission, then 2 |
verify_claim | 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 th Inputs: intent, claim, agent_id, callback_url, payment_signature |
Every block below points at https://verifi.cloud/mcp. Pick your client and copy.
claude mcp add --transport http verifi https://verifi.cloud/mcp
{
"mcpServers": {
"verifi": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://verifi.cloud/mcp"]
}
}
}{
"mcpServers": {
"verifi": {
"url": "https://verifi.cloud/mcp"
}
}
}{
"servers": {
"verifi": {
"type": "http",
"url": "https://verifi.cloud/mcp"
}
}
}{
"context_servers": {
"verifi": {
"url": "https://verifi.cloud/mcp"
}
}
}{
"mcpServers": {
"verifi": {
"serverUrl": "https://verifi.cloud/mcp"
}
}
}{
"mcpServers": {
"verifi": {
"url": "https://verifi.cloud/mcp"
}
}
}name: verifi
version: 0.0.1
schema: v1
mcpServers:
- name: verifi
type: streamable-http
url: https://verifi.cloud/mcp{
"mcpServers": {
"verifi": {
"httpUrl": "https://verifi.cloud/mcp"
}
}
}{
"mcpServers": {
"verifi": {
"type": "http",
"url": "https://verifi.cloud/mcp"
}
}
}{
"mcpServers": {
"verifi": {
"url": "https://verifi.cloud/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fverifi.cloud%2Fmcp&type=streamable_http&id=verifi&name=verifi
It answered our last check on 19 October 2026. Over 1 checks since 19 October 2026 it answered 1. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by verifi.cloud and served from verifi.cloud, the vendor's own domain: https://verifi.cloud/mcp.
4, as returned by the server's own tools/list on 19 October 2026: get_verify, unlock_verify, verifi_info, verify_claim.
It answered our last check on 19 October 2026. Over 1 checks since 19 October 2026 it answered 1.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://verifi.cloud/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: verifi.cloud. Endpoint host: verifi.cloud. ARD identifier: urn:air:verifi.cloud:mcp:verifi.
First indexed 19 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.