Is the Verifi Human Verification MCP server down?

mcp-registry/cloud.verifi/human-verification · v3.0.1

As of 2026-10-24 10:10 UTC, the Verifi Human Verification MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 4 minutes.

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

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

{
  "mcpServers": {
    "verifi-human-verification-mcp-server": {
      "type": "http",
      "url": "https://verifi.cloud/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (73/100)

What to fix (3)

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcloud.verifi%2Fhuman-verification/fixes

{
  "name": "get_verify",
  "description": "Read the current state of a verification. Free, never reveals a locked answer.\n\n    verify_id: the id returned by verify_claim.\n    Returns status \"processing\" (a human is working: wait retry_after_seconds,\n    or rely on the callback), \"ready\" (an answer exists; service_window shows\n    the window that applied and the exact unlock price, then call\n    unlock_verify), \"failed\" (no answer within 24 hours; failure explains the\n    reason and the free next admission), or \"completed\" (the answer is\n",
  "inputSchema": {
    "type": "object",
    "title": "get_verifyArguments",
    "required": [
      "verify_id"
    ],
    "properties": {
      "verify_id": {
        "type": "string",
        "title": "Verify Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "verifi_info",
  "description": "Describe Verifi before using it: what it does, how to pay, and the current price terms.\n\n    Free and needs no arguments. Returns the service summary, how payment\n    works (no sign-in: each paid call carries an x402 payment), the live\n    price terms (0.10 EUR admission,\n    then 2.90 EUR if a human answers within 60 minutes or 1.45 EUR within 24\n    hours, with the asset amounts and exchange rate used), the callback\n    events, and the rules for agents. Call it once to plan; the payment\n    re",
  "inputSchema": {
    "type": "object",
    "title": "verifi_infoArguments",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/cloud.verifi/human-verification"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/cloud.verifi/human-verification"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~878 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• verify_claim ~281 tokens
• unlock_verify ~226 tokens
• get_verify ~197 tokens
• verifi_info ~174 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcloud.verifi%2Fhuman-verification.svg)](https://glimind.com/server/mcp-registry%2Fcloud.verifi%2Fhuman-verification?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcloud.verifi%2Fhuman-verification?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcloud.verifi%2Fhuman-verification.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcloud.verifi%2Fhuman-verification.svg
   :target: https://glimind.com/server/mcp-registry%2Fcloud.verifi%2Fhuman-verification?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:dab432913424dda4…, first seen 2026-10-19, included at leaf 27703 of 58,164. Version history · verify what your client received.

Tools (4)

• get_verify
• unlock_verify
• verifi_info
• verify_claim

Compare: most reliable other servers · most reliable communication servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Verifi Human Verification MCP server down right now?

As of 2026-10-24 10:10 UTC, the Verifi Human Verification MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Verifi Human Verification MCP server provide?

Verifi Human Verification MCP server advertises 4 tools, including get_verify, unlock_verify, verifi_info, verify_claim.

How do I install Verifi Human Verification MCP server?

Point your MCP client at this streamable-http endpoint: https://verifi.cloud/mcp

Is the Verifi Human Verification MCP server safe to connect to an AI agent?

Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Verifi Human Verification MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.