5arz-proof-of-human

Prove a real, unique human performed an action; mint a signed, verifiable Proof-of-Human credential.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
97%
Integridad del esquema
89%
Calidad de los nombres
96%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Hallazgos (1)

  • LOWTool 'get_vhh_index' description lacks action verben get_vhh_index

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~1,642Tokens (definiciones de herramientas)
~957 BTamaño de respuesta típico
Impacto moderado en la atención (1.28% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "5arz-proof-of-human": {
      "url": "https://mcp.5arz.com"
    }
  }
}

Puntos de conexión remotos

https://mcp.5arz.comstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (9)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟡register_agent(name, contactEmail, mode)

Create a 5arz API key so your agent can request proof-of-human credentials. Every new key starts on the Free plan — 1,000 credential seals a month and 10 document checks, no card. Pass mode:"test" for an unlimited free sandbox key (arz_test_…) whose credentials are marked test:true — never treat test credentials as production proof. The key is shown once; store it.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Your company or agent name."
    },
    "contactEmail": {
      "type": "string",
      "format": "email",
      "description": "Contact email for the account."
    },
    "mode": {
      "type": "string",
      "enum": [
        "live",
        "test"
      ],
      "default": "live",
      "description": "live for production keys; test for an unlimited free sandbox key."
    }
  },
  "required": [
    "name",
    "contactEmail"
  ],
  "additionalProperties": false
}
🟢verify_human(sessionId, memberId, wallet, walletSig, walletNonce, ...)

Mint a signed Proof-of-Human-Fulfillment (PoHF) credential attesting a real, ID-verified, live human performed an action. Provide sessionId to attest work fulfillment, or memberId to attest that an ID-verified human is behind an account (optionally wallet-bound). This does not establish that the person holds only one account — read sybil_checked in the returned claims before gating one-per-person actions. Counts as one seal against your monthly plan allowance (1,000/month on Free; unlimited for test keys). Returns an ES256 JWT that anyone can verify against the public JWKS — pass it to check_credential. Requires an API key (Authorization: Bearer, or the apiKey argument).

Esquema de entrada

{
  "type": "object",
  "properties": {
    "sessionId": {
      "type": "string",
      "description": "Verified session to attest (work-fulfillment path)."
    },
    "memberId": {
      "type": "string",
      "description": "Member to attest as an ID-verified, live human (personhood path)."
    },
    "wallet": {
      "type": "string",
      "description": "Optional EVM address to bind for on-chain isVerifiedHuman() gating (personhood path)."
    },
    "walletSig": {
      "type": "string",
      "description": "Optional EIP-191 personal_sign of the wallet challenge."
    },
    "walletNonce": {
      "type": "string",
      "description": "Optional wallet challenge nonce."
    },
    "apiKey": {
      "type": "string",
      "description": "Optional: pass your key here if your client cannot set the Authorization header."
    }
  },
  "additionalProperties": false
}
🟢check_credential(pohf_jwt)

Independently verify a 5arz PoHF JWT: checks the ES256 signature against the live public JWKS and validates expiry/not-before, then returns valid/invalid plus the decoded claims. No API key needed — this is pure cryptographic verification you could also do with any standard JWT library. Accepts either the legacy pohf_jwt / pop_jwt or the standards-conformant sd_jwt_vc (IETF SD-JWT VC, typ dc+sd-jwt).

Esquema de entrada

{
  "type": "object",
  "properties": {
    "pohf_jwt": {
      "type": "string",
      "description": "The credential returned by verify_human — the compact JWT, or the sd_jwt_vc string (ends in ~)."
    }
  },
  "required": [
    "pohf_jwt"
  ],
  "additionalProperties": false
}
🟢get_vhh_index

Return the current Verified-Human-Hour (VHH) index — the benchmark price of one hour of verified human work/attention, in USD. Free, no API key. Useful for pricing verified-human data and as a citable benchmark.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢subscribe(plan, apiKey)

Get a Stripe checkout link for a 5arz plan. Free (1,000 seals/mo, 10 document checks), Starter ($99/mo, 100k seals, $1.25/document check), Growth ($499/mo, 1M seals, $0.75/check), Scale ($2,499/mo, unlimited seals, $0.50/check). SEALS are credential signatures and are effectively free; DOCUMENT CHECKS are the vendor identity verification and are what you are really paying for. Human verification is always free to the human, at any volume. Requires an API key.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "plan": {
      "type": "string",
      "enum": [
        "starter",
        "growth",
        "scale"
      ],
      "description": "starter=$99/mo, growth=$499/mo, scale=$2,499/mo. See https://5arz.com/pricing."
    },
    "apiKey": {
      "type": "string",
      "description": "Optional: pass your key here if your client cannot set the Authorization header."
    }
  },
  "required": [
    "plan"
  ],
  "additionalProperties": false
}
🟢get_balance(apiKey)

Return the current plan, seals and document checks used this month, and what remains. Requires an API key.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "apiKey": {
      "type": "string",
      "description": "Optional: pass your key here if your client cannot set the Authorization header."
    }
  },
  "additionalProperties": false
}
🟢list_verified_human_tasks(limit)

List currently-buyable verified human work tasks. Each task includes its USD price, remaining slots, supported settlement chains, and the kind of Proof-of-Human-Fulfillment receipt issued on completion. Free, no API key.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max tasks to return (default 20, max 100)."
    }
  },
  "additionalProperties": false
}
🔴purchase_verified_human_task(task_id, x_payment, purchase_id, agent_key_thumb)

Buy one slot of a verified human task. Called without payment it returns an HTTP 402 / x402 challenge with settlement instructions; settle USDC on the offered chain and call again with x_payment and purchase_id to receive an attestation_id — a verifiable Proof-of-Human-Fulfillment receipt. No API key required; the payment is the authentication.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "task_id": {
      "type": "string",
      "description": "Task id from list_verified_human_tasks."
    },
    "x_payment": {
      "type": "string",
      "description": "Optional X-PAYMENT settlement proof. Omit to receive the 402 challenge."
    },
    "purchase_id": {
      "type": "string",
      "description": "Purchase id from the previous 402. Required when presenting an x_payment."
    },
    "agent_key_thumb": {
      "type": "string",
      "description": "Optional RFC 7638 JWK thumbprint of your agent key; embedded in the receipt's cnf.jkt claim."
    }
  },
  "required": [
    "task_id"
  ],
  "additionalProperties": false
}
🟢get_attestation_receipt(attestation_id)

Fetch a Proof-of-Human-Fulfillment receipt by attestation id. Returns the signed packet, verifier identifier, JWKS URL, and a how-to-verify hint. Free, no API key — pair it with check_credential to verify the signature yourself.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "attestation_id": {
      "type": "string",
      "description": "Returned at fulfillment, or in the X-Attestation-Id header on the buy response."
    }
  },
  "required": [
    "attestation_id"
  ],
  "additionalProperties": false
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada9 herramientas
verificadoversión no registrada9 herramientas
verificadoversión no registrada9 herramientas