io.github.LumiRx/5arz-proof-of-human
io.github.LumiRx/5arz-proof-of-human · 1.0.0
Prove a real, unique human performed an action; mint a signed, verifiable Proof-of-Human credential.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcp.5arz.comstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 9 tools.
- Protocol
- 2025-06-18
- Calls itself
- 5arz 1.0.0
- Handshake time
- 70 ms
- HTTP status
- 200
The tools it lists (9, as of 12 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
register_agentCreate 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.
verify_humanMint 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_c
check_credentialIndependently 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).
get_vhh_indexReturn 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.
subscribeGet 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
io.github.LumiRx/5arz-proof-of-human, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 87 days ago. The registry entry · 5arz.com