Hive Zk Attestation
Server Details
Zero-knowledge attestation for agent capability and trust score claims
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- srotzin/hive-mcp-zk-attestation
- GitHub Stars
- 0
- Server Listing
- hive-mcp-zk-attestation
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 8 of 8 tools scored. Lowest: 3.5/5.
Tools are cleanly split into two distinct domains (earn and zk attestation), each with well-defined individual purposes. Within each domain, no two tools overlap: leaderboard, me, register are clearly different; anchor, attest, list, query, verify are all distinct operations.
The naming uses consistent snake_case with clear prefixes: 'hive_earn_' for earn tools and 'zk_' for attestation tools. Each group follows a verb_noun pattern (e.g., hive_earn_register, zk_anchor_to_base). The two prefixes are mixed but are semantically justified and consistent within themselves.
With 8 tools, the server is well-scoped. It covers both the earn and attestation functionalities without being bloated. Each tool has a clear purpose and earns its place.
The tool surface covers the core lifecycle for both domains: register, view leaderboard, check own earnings; produce, anchor, query, verify attestations. Minor gaps exist (e.g., no update/withdraw for earn, no revoke for attestations) but these are not essential for the primary use cases.
Available Tools
8 toolshive_earn_leaderboardInspect
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=. Returns "rails not yet live" gracefully if upstream is not yet deployed.
| Name | Required | Description | Default |
|---|---|---|---|
| window | No | Time window. One of: "7d", "30d", "lifetime". Default "7d". |
hive_earn_meInspect
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=. Returns "rails not yet live" gracefully if upstream is not yet deployed.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_did | Yes | Agent DID to look up. Required. |
hive_earn_registerInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_did | Yes | Caller agent DID (e.g. did:hive:0x… or did:web:…). Required. | |
| payout_address | Yes | Base L2 EVM address (0x…) to receive USDC kickback payouts. | |
| attribution_url | Yes | Public URL of the agent / page driving attributed traffic to Hive. Used for ranking + audit. |
zk_anchor_to_baseInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_did | Yes | DID of the attesting agent | |
| proof_commitment | Yes | Hex-encoded 32-byte commitment to the proof | |
| verification_key_id | No | Identifier of the verification key referenced by the proof |
zk_attest_agent_stateInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| circuit | No | Circuit identifier; defaults to varuna-bls12377-agent-state-v1 (snarkVM-compatible) | |
| agent_did | Yes | DID of the agent whose state is being attested | |
| state_hash | Yes | Hex-encoded 32-byte hash of the agent state (poseidon or sha256) | |
| public_inputs | No | Optional public inputs as hex strings |
zk_list_circuitsInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
zk_query_attestationInspect
Fetch a previously-anchored attestation by Base transaction hash. Returns the proof commitment, verification key id, agent DID, and block number. Free. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
| tx_hash | Yes | Base L2 transaction hash of the anchored attestation |
zk_verify_proofInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| proof | Yes | Hex-encoded proof bytes (Varuna; Groth16/Plonk research-stage only) | |
| public_inputs | No | Public inputs the proof was generated against | |
| verification_key_id | Yes | Identifier of the verification key to check against |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.