io.github.LumiRx/5arz-proof-of-human
REMOTE · MCP.5ARZ.COM · SCANNED AUG 3
Prove a real, unique human performed an action; mint a signed, verifiable Proof-of-Human credential.
Available components
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 →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 768 tokens (~128/item across 6 items; 6 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 Management27
- Stability observed for 8 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.5arz.com
claude mcp add --transport http lumirx-5arz-proof-of-human https://mcp.5arz.com/
[mcp_servers.lumirx-5arz-proof-of-human] url = "https://mcp.5arz.com/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lumirx-5arz-proof-of-human": {
"type": "remote",
"url": "https://mcp.5arz.com/",
"enabled": true
}
}
} openclaw mcp add lumirx-5arz-proof-of-human --url https://mcp.5arz.com/ --transport streamable-http
mcp_servers:
lumirx-5arz-proof-of-human:
url: "https://mcp.5arz.com/" {
"mcpServers": {
"lumirx-5arz-proof-of-human": {
"type": "http",
"url": "https://mcp.5arz.com/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 65
First indexed and scored.
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 3 Aug 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 | 15 Jul 2026 | 13 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | fc00b13a5465122a1308210851041c96 |
| 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 |
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 |
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.
buy_credits Buy a prepaid verification pack ~132
Get a Stripe checkout link for a prepaid verification pack: starter (100 / $49), growth (1,000 / $299), or scale (10,000 / $1,999). Credits post on payment. Test keys skip this (unlimited). For pay-per-call settlement, 5arz also supports x402. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | — | Optional: pass your key here if your client cannot set the Authorization header. |
| pack | string | yes | starter=100/$49, growth=1,000/$299, scale=10,000/$1,999. |
No output schema declared.
No examples provided.
check_credential Verify a PoHF credential (no 5arz trust required) ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pohf_jwt | string | yes | The compact JWT string returned by verify_human. |
No output schema declared.
No examples provided.
get_balance Check remaining verifications ~48
Return remaining prepaid verification credits, plus lifetime purchased/consumed. 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.
register_agent Register an agent (get a 5arz API key) ~124
Create a 5arz API key so your agent can request proof-of-human credentials. Every new key includes a 20-verification free tier (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.
verify_human Verify a human (mint a PoHF credential) ~236
Mint a signed Proof-of-Human-Fulfillment (PoHF) credential attesting a real, unique, attentive human performed an action. Provide sessionId to attest work fulfillment, or memberId to attest personhood (anti-sybil, optionally wallet-bound). Spends 1 credit (free inside the 20-verification tier; 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 a unique 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.