Talandor
Public MCP report

Verifi

https://verifi.cloud/mcp

Official Registry

Official Registry · cloud.verifi/human-verification · Publisher namespace: cloud.verifi

Server checked today at 22:53 UTC

Displayed catalog: last complete observation from September 19

4 public tools observed. Tools were not executed. These tools come from the catalog observation above, not from the latest availability check.

Reachable

What Talandor observed

The server answered

Add the endpoint to your assistant using the configuration shown below. A Watch can alert you if this public catalog changes.

This is a public protocol and tools/list check, not a functional validation.

https://verifi.cloud/mcp
AvailabilityReachablemeasured
Tools4 public tools observedmeasured
Assistant testNot tested by Talandorunknown

Configure your assistant · Check details

How to use this MCP

Talandor checks the server; it does not connect the server to your assistant.

Choose your assistant, then copy the configuration shown for that client. Authentication is completed with the MCP provider, never inside Talandor.

    Open the official client guide (opens in a new tab)
    
      
    Check details
      
    What changed
    Public contract stable since 
    Last check  · No semantic contract change since the previous complete snapshot.
    Info
    This public timeline shows the latest check, the last 24 hours, and the most recent important change. Watch keeps 30 days.
    The notes above are for this connector.
    
      
    Server-provided content. Tool names, descriptions and schemas below are copied from the MCP server. They may be in another language. Talandor does not translate or verify them.
    Tools and declared exposure
    Server annotations are declarations, not verified behavior.
    Show 4 of 4 server-provided tool definitions
    get_verify
    No effect details provided
    Show server-provided details
    Server description (copied; language not verified)
    Poll until ready or failed. Honor retry_after_seconds while processing.
    Input schema (server-provided preview — do not copy)
    {
  "type": "object",
  "title": "get_verifyArguments",
  "required": [
    "verify_id"
  ],
  "properties": {
    "verify_id": {
      "type": "string",
      "title": "Verify Id"
    }
  }
}
    unlock_verify
    No effect details provided
    Show server-provided details
    Server description (copied; language not verified)
    Pass gate 2 for a ready chain and return the human result.

    This gate costs 2.90 USDC. 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.
    
    Input schema (server-provided preview — do not copy)
    {
  "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
    }
  }
}
    verifi_info
    No effect details provided
    Show server-provided details
    Server description (copied; language not verified)
    Service description, pricing, and rules.
    Input schema (server-provided preview — do not copy)
    {
  "type": "object",
  "title": "verifi_infoArguments",
  "properties": {}
}
    verify_claim
    No effect details provided
    Show server-provided details
    Server description (copied; language not verified)
    Ask a real human to verify a claim.

    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.
    
    Input schema (server-provided preview — do not copy)
    {
  "type": "object",
  "title": "verify_claimArguments",
  "required": [
    "agent_id",
    "claim",
    "intent"
  ],
  "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
    }
  }
}
    
      
    Evidence and limitations
    Method: anonymous Streamable HTTP probe. We never invoke a tool.
    Attempted protocols: 2026-07-28, 2025-11-25
    Protocol2025-11-25
    TransportStreamable HTTP
    AuthNo authentication challenge observed
    EvidencePublic contract observed
    Total latency4213 ms
    Response bytes2444
    No diagnostic errors.
    
      
    Observation history
    Operational
     · stable since 
    2025-11-25 · 4 tools · no change · 31 checks
    Unreachable now
    No protocol
    Operational
    2025-11-25 · 4 tools
    Unreachable now
    No protocol
    Operational
    2025-11-25 · 4 tools
    Unreachable now
    No protocol
    Operational
    2025-11-25 · 4 tools
    Unreachable now
    No protocol
    Operational
     · stable since 
    2025-11-25 · 4 tools · no change · 11 checks
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Operational
     · stable since 
    2025-11-25 · 4 tools · no change · 2 checks
    Unreachable now
    No protocol
    Operational
     · stable since 
    2025-11-25 · 4 tools · no change · 6 checks
    Unreachable now
    No protocol
    Operational
     · stable since 
    2025-11-25 · 4 tools · no change · 2 checks
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Operational
     · stable since 
    2025-11-25 · 4 tools · no change · 2 checks
    Unreachable now
    No protocol
    Operational
    2025-11-25 · 4 tools
    Unreachable now
    No protocol
    Operational
     · stable since 
    2025-11-25 · 4 tools · no change · 5 checks
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Operational
     · stable since 
    2025-11-25 · 4 tools · no change · 5 checks
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Operational
    2025-11-25 · 4 tools
    Operational
    2025-11-25 · 4 tools
    Complete public contract · 2025-11-25 · 4 tools
    b5884f6967a3
    Complete public contract · 2025-11-25 · 4 tools
    b5884f6967a3
    Complete public contract · 2025-11-25 · 4 tools
    b5884f6967a3
    
      
    Deep monitoring eligibility
    Eligible for deep monitoring
    A complete public tools/list contract was observed, so a future deep-monitoring baseline can be compared safely.
    A Watch starts from the payment section on this page, and only after a verified payment.
    See public monitoring
    
      
    
      
    Watch · recurring plan
    Watch this MCP
    Your agent depends on this MCP. When Watch is active, periodic checks alert you when we observe a change that may affect the client you selected.
    • Know when it goes downWhen Watch is active, availability is observed about every 5 minutes. An outage is confirmed after two failed checks, so a single miss is not treated as a lasting outage.
    • Know when its contract changesDeep checks about every hour compare public tool catalogs and authentication surfaces over time.
    • Know what changed and what to fixAn alert names the observed change and the next step for the client you selected.
    Full public-contract coverage: Availability, protocol, auth and public tool contract changes can be compared.
    Full WatchAvailability, protocol, auth and public tool contract changes
    Surface WatchAvailability, TLS, protocol and auth surface — no private tool diff
    Early access currently activates this first endpoint; adding more endpoints up to the planned limit of five is not open in this deployment. Live checkout is open. A Watch activates only after a verified payment event; a browser return never starts monitoring.
    Start Watch