Skip to main content
Glama

Server Details

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

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
jyharju-code/verifi
GitHub Stars
0
Server Listing
cloud.verifi/human-verification
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct role in the verification lifecycle: verifi_info describes the service, verify_claim creates a verification request, get_verify checks status without unlocking, and unlock_verify pays to retrieve a result. The descriptions make the boundary between reading state and paying for the answer especially clear.

Naming Consistency4/5

Three tools follow a verb_noun pattern: get_verify, unlock_verify, and verify_claim. verifi_info is a minor deviation because it uses the service name plus info rather than a verb, but the set remains predictable overall.

Tool Count5/5

Four tools is well-scoped for this service: one informational tool, one creation tool, one status tool, and one unlock/payment tool. No tool feels redundant or missing from the minimal paid-verification workflow.

Completeness4/5

The surface covers the full core lifecycle: discover terms, submit a claim, poll status, and unlock the result via payment. Minor gaps include no explicit cancel or retry-active-verification operation, and error recovery relies on get_verify and callbacks rather than a dedicated tool.

Available Tools

4 tools
get_verifyAInspect

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.

Inputs: verify_id (required).

unlock_verifyAInspect

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.

Inputs: verify_id (required), payment_signature.

verifi_infoAInspect

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.

Inputs: no named parameters.

verify_claimAInspect

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.

Inputs: claim (required), intent (required), agent_id (required), callback_url, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Lets an AI agent hire and pay a verified human: post real-world tasks (voice, observation, judgment) and pay in USDC via a non-custodial x402 auth-capture escrow on Base, budget frozen at deploy. Humans verify their X identity before submitting.
      8
      81 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to call real human reviewers who inspect published work and return pinned comments and a verdict, so the agent can iterate until approved.
      38 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.