MCP server · Streamable HTTPLive

Proof of human, inside your agent.

You proved the payment. We prove the human. Any Claude, GPT or agent-framework session can register, issue a signed credential and check it — over the Model Context Protocol.

Server URLhttps://mcp.5arz.com
  • Streamable HTTP
  • Auth: Bearer <5arz API key>
  • Free: 1,000 seals/mo
  • Verify against the public JWKS, no SDK
  • x402 task purchase — no key (developer preview)
9 toolstools/list · no key
★check_credentialpure crypto · no trust in 5arz
An AI agent with a verified-human check mark.
Connect

Add it to Claude.

One command in Claude Code, or one block in any MCP client config.

Claude Code (CLI)
terminal
claude mcp add --transport http 5arz https://mcp.5arz.com \
  --header "Authorization: Bearer arz_live_YOUR_KEY"
Client config (.mcp.json / Claude Desktop)
.mcp.json
{
  "mcpServers": {
    "5arz": {
      "type": "http",
      "url": "https://mcp.5arz.com",
      "headers": { "Authorization": "Bearer arz_live_YOUR_KEY" }
    }
  }
}
No key yet? Add the server without the header. You can still call register_agent, get_vhh_index, check_credential, and all three marketplace tools (list_verified_human_tasks, purchase_verified_human_task, get_attestation_receipt). Then register_agent returns a key with Free plan: 1,000 seals/mo.
Reference

Nine tools.

What each one does, and whether it needs your API key.

ToolWhat it doesKey?
register_agentCreate a 5arz API key (Free plan: 1,000 seals/mo + 10 document checks). mode:"test" for an unlimited sandbox key.No
verify_humanMint a signed PoHF credential — sessionId for work fulfillment, or memberId for personhood (optionally wallet-bound).Yes
check_credentialIndependently verify a PoHF JWT against the public JWKS and read its claims. Pure crypto — no trust in 5arz.No
get_vhh_indexThe Verified-Human-Hour index ($/hr) — a citable benchmark for verified human work.No
subscribeStripe checkout for a plan: Starter $99/mo, Growth $499/mo, Scale $2,499/mo.Yes
get_balanceCurrent plan, seals and document checks used this month, and what remains.Yes
Verified-human-work marketplace — no API key, the payment is the authentication
list_verified_human_tasksCurrently-buyable verified human work: USD price, price_usdc_atomic, slots remaining, settlement chains, and the receipt kind issued on completion.No
purchase_verified_human_taskBuy one slot. With only a task_id it returns the x402 HTTP 402 challenge (accepts[] + purchase_id). Settle the USDC, call again with x_payment and purchase_id to get an attestation_id.No
get_attestation_receiptThe Proof-of-Human-Fulfillment receipt for an attestation_id — signed packet, verifier identity, JWKS URL, and how to verify it yourself.No
Quickstart

Three calls to a checked seal.

  1. register_agent

    Your API key (Free plan: 1,000 seals/mo).

  2. verify_human

    A signed PoHF credential (ES256 JWT).

  3. check_credential

    Anyone confirms it against the JWKS.

Kick the tires

List the tools with curl.

The server speaks JSON-RPC 2.0. No key needed to list tools.

tools/list
curl -s https://mcp.5arz.com \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Verified human workDeveloper preview · testnet

Buy verified human work — no key.

The same server sells the work, not just the proof. An agent can complete a purchase end to end, with no API key and no person — the x402 payment is the authentication.

Developer preview: USDC settlement runs on Base Sepolia (testnet) today. Stock varies, so list first — a sold-out task returns out_of_stock (HTTP 409 over REST).
  1. List

    list_verified_human_tasks → task id, USD price, slots left, settlement chains.

  2. Challenge

    purchase_verified_human_task {task_id} → HTTP 402 challenge: accepts[] + purchase_id.

  3. Settle

    Settle the USDC on an offered chain, then call again with x_payment + purchase_id.

  4. Receipt

    get_attestation_receipt {attestation_id} → the signed PoHF receipt + JWKS to verify it.

purchase
curl -s https://mcp.5arz.com \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"purchase_verified_human_task",
                 "arguments":{"task_id":"wf_support_reply_001"}}}'

The 402 is the protocol working.

It comes back as an ordinary tool result carrying accepts[] (scheme, network, payTo, USDC asset, maxAmountRequired) and a purchase_id. Calling with no payment costs nothing.

The same loop over plain REST: GET /api/agent/tasks, GET /api/agent/tasks/{task_id}/buy, GET /api/attestations/{attestation_id}.

bind_human_to_payment — attaching a verified human to a payment that already settled on another rail — is a separate product and still lives only at https://api.5arz.com/mcp.

Standards

Works with the agent-payment rails.

Compatible with Verifiable Intent and the Visa Trusted Agent Protocol. The credential binds to payments on Agent Pay, Stripe, or x402/USDC.

5arz binds an agent to an ID-verified, live human — the claim Web Bot Auth, Know Your Agent and the Trusted Agent Protocol reference but don’t provide.

Start free.

Call register_agent in-session, or get your key in the browser. Free plan: 1,000 seals a month, no card.