io.github.LumiRx/5arz-proof-of-human
REMOTE · MCP.5ARZ.COM
Prove a real, unique human performed an action; mint a signed, verifiable Proof-of-Human credential.
Available components
Last scanned (23 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Security
Recent critical change
Authorization (18 Aug 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (purchase_verified_human_task). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1323 tokens (~147/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Sept 26 0
- Stability: fail → pass ▲ security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Aug 26 0
- Tool “verify_human” rewrote its description, which is the text the model reads security
- 18 Aug 26 0
- Authorization: unverified → fail ▼ critical
- Stability: 0.73 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “buy_credits” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- New tool “purchase_verified_human_task”, which the server declares destructive security
- Tool “get_balance” rewrote its description, which is the text the model reads security
- Tool “register_agent” rewrote its description, which is the text the model reads security
- Tool “verify_human” rewrote its description, which is the text the model reads security
- Schema quality: 128 → 141 ▼ functional
- New tool “get_attestation_receipt” functional
- New tool “list_verified_human_tasks” functional
- New tool “subscribe” functional
- “verify_human” reworded the description of “memberId” cosmetic
- Tool “get_balance” changed its title: Check remaining verifications → Check plan and remaining allowance cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.5arz.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=5arz.com | CN=WE1,O=Google Trust Services,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 376e19d544f87f8f0e501540bf0eaf26 |
| SANs: 5arz.com, mcp.5arz.com, *.mcp.5arz.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.5arz.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| 5arz.com. | present | 2371 | 13 | Verified |
| mcp.5arz.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.5arz.com | Verified | 200 | |
| http (plaintext) | http://mcp.5arz.com | HTTPS enforced | 301 | https://mcp.5arz.com/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_credential Verify a PoHF credential (no 5arz trust required) ~141
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).
| Name | Type | Req | Description |
|---|---|---|---|
| pohf_jwt | string | yes | The credential returned by verify_human — the compact JWT, or the sd_jwt_vc string (ends in ~). |
No output schema declared.
No examples provided.
get_attestation_receipt Fetch a Proof-of-Human-Fulfillment receipt ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attestation_id | string | yes | Returned at fulfillment, or in the X-Attestation-Id header on the buy response. |
No output schema declared.
No examples provided.
get_balance Check plan and remaining allowance ~52
Return the current plan, seals and document checks used this month, and what remains. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Optional: pass your key here if your client cannot set the Authorization header. |
No output schema declared.
No examples provided.
get_vhh_index Get the Verified-Human-Hour index ($/hr) ~59
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_verified_human_tasks List buyable verified human work ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max tasks to return (default 20, max 100). |
No output schema declared.
No examples provided.
purchase_verified_human_task Buy one slot of verified human work (x402) ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_key_thumb | string | – | Optional RFC 7638 JWK thumbprint of your agent key; embedded in the receipt's cnf.jkt claim. |
| purchase_id | string | – | Purchase id from the previous 402. Required when presenting an x_payment. |
| task_id | string | yes | Task id from list_verified_human_tasks. |
| x_payment | string | – | Optional X-PAYMENT settlement proof. Omit to receive the 402 challenge. |
No output schema declared.
No examples provided.
register_agent Register an agent (get a 5arz API key) ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contactEmail | string | yes | Contact email for the account. |
| mode | string | – | live for production keys; test for an unlimited free sandbox key. |
| name | string | yes | Your company or agent name. |
No output schema declared.
No examples provided.
subscribe Subscribe to a 5arz plan ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Optional: pass your key here if your client cannot set the Authorization header. |
| plan | string | yes | starter=$99/mo, growth=$499/mo, scale=$2,499/mo. See https://5arz.com/pricing. |
No output schema declared.
No examples provided.
verify_human Verify a human (mint a PoHF credential) ~274
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).
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Optional: pass your key here if your client cannot set the Authorization header. |
| memberId | string | – | Member to attest as an ID-verified, live human (personhood path). |
| sessionId | string | – | Verified session to attest (work-fulfillment path). |
| wallet | string | – | Optional EVM address to bind for on-chain isVerifiedHuman() gating (personhood path). |
| walletNonce | string | – | Optional wallet challenge nonce. |
| walletSig | string | – | Optional EIP-191 personal_sign of the wallet challenge. |
No output schema declared.
No examples provided.
How do I install the io.github.LumiRx/5arz-proof-of-human MCP server?
io.github.LumiRx/5arz-proof-of-human is a hosted endpoint at https://mcp.5arz.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.5arz.com
claude mcp add --transport http lumirx-5arz-proof-of-human 'https://mcp.5arz.com/'
What is the io.github.LumiRx/5arz-proof-of-human MCP server?
io.github.LumiRx/5arz-proof-of-human is an MCP server listed in the public MCP registry as io.github.LumiRx/5arz-proof-of-human. Prove a real, unique human performed an action; mint a signed, verifiable Proof-of-Human credential. This page covers its hosted endpoint (https://mcp.5arz.com).
Is the io.github.LumiRx/5arz-proof-of-human MCP server safe to use?
io.github.LumiRx/5arz-proof-of-human scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.LumiRx/5arz-proof-of-human MCP server expose?
io.github.LumiRx/5arz-proof-of-human exposes 9 tools: register_agent, verify_human, check_credential, get_vhh_index, subscribe, and 4 more. Their descriptions and schemas cost roughly 1,185 tokens of context every time the server is loaded.
Does the io.github.LumiRx/5arz-proof-of-human MCP server require authentication?
No. We connected to io.github.LumiRx/5arz-proof-of-human without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.LumiRx/5arz-proof-of-human MCP server still maintained?
io.github.LumiRx/5arz-proof-of-human is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.