Hive Zk Attestation MCP server
io.github.srotzin/hive-mcp-zk-attestationsrotzinstreamable-httpv1.0.0Scanned
Zero-knowledge attestation for agent capability and trust score claims
8 tools: 6 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Hive Zk Attestation MCP server can do
The Hive Zk Attestation MCP server is published by the GitHub account srotzin. It has 8 tools. It can create or change data (6 tools: zk_attest_agent_state, zk_verify_proof, zk_anchor_to_base, hive_earn_register and 2 more), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 6Claude Code: ask
hive_earn_leaderboardTop earning agents on the Hive Civilization, by attribution payout in USDC.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Top earning agents on the Hive Civilization, by attribution payout in USDC. Real Base USDC settlement. Calls GET https://hivemorph.onrender.com/v1/earn/leaderboard?window=<window>. Returns "rails not yet live" gracefully if upstream is not yet deployed.
hive_earn_meLook up the caller agent's registered earn profile, lifetime + pending USDC balance, last payout tx hash, and next-payout ETA.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Look up the caller agent's registered earn profile, lifetime + pending USDC balance, last payout tx hash, and next-payout ETA. Real Base USDC, no mock data. Calls GET https://hivemorph.onrender.com/v1/earn/me?agent_did=<did>. Returns "rails not yet live" gracefully if upstream is not yet deployed.
hive_earn_registerRegister an agent for the Hive Civilization attribution payout program.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Register an agent for the Hive Civilization attribution payout program. Settlement on real Base USDC. 5% kickback on attributed traffic, weekly payout. Calls POST https://hivemorph.onrender.com/v1/earn/register on behalf of the caller. Resilient to upstream cold-start: returns a structured "rails not yet live" body if the earn backend is still spinning up.
zk_anchor_to_baseWrite an attestation commitment (32-byte hash) to Base via the Hive gateway.No findings
Why it is in this group
- The description's first verb is "write": a word for a change.
Description, as the server wrote it Write an attestation commitment (32-byte hash) to Base via the Hive gateway. Anchors the attestation only; does not bridge value or move state to Aleo. Aleo snarkVM consumes the attestation independently via Leo programs (future hive-leo-circuits repo). Cost: $0.02 USDC + L1 gas. Backend RFC-stage; returns backend_pending until rails land.
zk_attest_agent_stateProduce a zero-knowledge attestation of an agent state hash + DID.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Produce a zero-knowledge attestation of an agent state hash + DID. Primary verification target is Aleo snarkVM (Varuna over BLS12-377); native Hive verification is next. Attestation-only — emits a proof, not a token; no value crosses chains. Cost: $0.05 USDC on Base. Backend RFC-stage; returns backend_pending until rails land.
zk_verify_proofVerify a submitted attestation against a known verification key.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Verify a submitted attestation against a known verification key. Aleo snarkVM (Varuna/BLS12-377) is the primary verification target via the snark.verify opcode. Returns boolean validity plus the verification key fingerprint. Free. Read-only — no settlement, no on-chain write.
Only reads 2Show 2 read-only tools
zk_list_circuitsEnumerate supported circuits and verification key fingerprints.No findings
Why it is in this group
- The name "zk_list_circuits" says "list": a word for reading.
Description, as the server wrote it Enumerate supported circuits and verification key fingerprints. Primary: Varuna over BLS12-377 (Aleo snarkVM-compatible). Research-stage: Groth16, Plonk. Future: Risc0, Plonky2. Free. Read-only.
zk_query_attestationFetch a previously-anchored attestation by Base transaction hash.No findings
Why it is in this group
- The name "zk_query_attestation" says "query": a word for reading.
Description, as the server wrote it Fetch a previously-anchored attestation by Base transaction hash. Returns the proof commitment, verification key id, agent DID, and block number. Free. Read-only.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:11 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://hive-mcp-zk-attestation.onrender.com/mcp: tools/list returned 8 tools to an anonymous client, including zk_attest_agent_state (write), zk_verify_proof (write), zk_anchor_to_base (write), hive_earn_register (write), hive_earn_me (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http hive-zk-attestation https://hive-mcp-zk-attestation.onrender.com/mcpclaude mcp add --transport http hive-zk-attestation https://hive-mcp-zk-attestation.onrender.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__hive-zk-attestation__zk_list_circuits",
"mcp__hive-zk-attestation__zk_query_attestation"
],
"ask": [
"mcp__hive-zk-attestation__zk_attest_agent_state",
"mcp__hive-zk-attestation__zk_verify_proof",
"mcp__hive-zk-attestation__zk_anchor_to_base",
"mcp__hive-zk-attestation__hive_earn_register",
"mcp__hive-zk-attestation__hive_earn_me",
"mcp__hive-zk-attestation__hive_earn_leaderboard"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hive-zk-attestation. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.srotzin/hive-mcp-zk-attestation/verify?hash=e14be04f4cd29cbf74559573ec24f4a7d0b95138f5f65df47af00d7a832b8961" | jq -e '.changed == false'Pinned hash e14be04f4cd2, from Nov 20, 2026, 14:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.srotzin/hive-mcp-zk-attestation/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.srotzin/hive-mcp-zk-attestation)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:49 UTC.
Hive Zk Attestation MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Hive Zk Attestation MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Hive Zk Attestation MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Hive Zk Attestation MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Hive Zk Attestation MCP server have?
- 8 tools: 6 write, 2 read. zk_attest_agent_state, zk_verify_proof, zk_anchor_to_base, hive_earn_register, hive_earn_me, hive_earn_leaderboard, zk_list_circuits and zk_query_attestation.
Does the Hive Zk Attestation MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Hive Zk Attestation MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Hive Zk Attestation MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.