Log inSubmit server
Hive Zk Attestation logo

Hive Zk Attestation

Creates zero-knowledge attestations for agent state hashes and DIDs, with proof verification and Base commitment anchoring.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Hive Zk Attestation

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for Hive Zk Attestation, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

Hive Zk Attestation MCP server exposes tools for creating zero-knowledge attestations about an agent’s 32-byte internal state hash and DID. It can verify proofs, anchor commitments to Base, list circuits, and query attestations, with Aleo snarkVM as the primary intended verification target. Reach for it when agents or auditors need verifiable state claims without revealing the underlying state, but note that the backend-dependent tools currently return 503.

Use cases

  • Attest an agent’s private state hash to a counterparty
  • Verify zero-knowledge proofs without exposing internal state
  • Anchor proof commitments to Base for audit trails
  • List available attestation circuits
  • Query previously created attestations

Key features

  • State-hash and DID attestations
  • Zero-knowledge proof verification
  • Base commitment anchoring
  • Inline circuit catalog
  • Attestation querying
  • Aleo snarkVM interoperability target

Tools5

What Hive Zk Attestation lets your agent do. Expand a tool for its parameters.

Self-reported~56 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

5/5 checks healthy over the last 34d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit5mo agoMost recent push to the default branch.
Tools exposed5Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Hive Zk Attestation works

What Hive Zk Attestation MCP server does

Hive Zk Attestation MCP server provides an MCP interface for producing attestations about an autonomous agent’s internal state without disclosing that state. An attestation identifies a 32-byte state hash and the DID associated with it. The intended result lets another agent, counterparty, regulator, or auditor check a claim while receiving only the proof result and public inputs.

The design separates attestation from asset movement. It does not bridge tokens, custody funds, wrap value, or provide signing authority. Its role is to emit proofs and commitments that other systems can verify.

How it works

An agent supplies its state hash and DID to the attestation flow. The resulting proof or commitment can then be anchored to Base, creating a public-chain audit reference associated with a block and transaction hash. Downstream verification is intended to occur either through Aleo snarkVM or, later, through the native Hive backend.

Aleo is the primary interoperability target. The stated path uses Varuna over BLS12-377, with verification through snarkVM and compatible Leo programs. Native Hive verification is planned but is not yet live. Risc0 and Plonky2 are research targets rather than implemented backends.

The model preserves state confidentiality, but it does not establish that the original state hash was truthful. A compromised agent can generate a valid proof for a false input, and a verifier still needs to trust the relevant verification key.

Tools and capabilities

The MCP tool surface includes:

  • zk_attest_agent_state for producing an agent-state attestation. The listed price is $0.05 USDC on Base.
  • zk_verify_proof for checking a proof. The listed cost is free.
  • zk_anchor_to_base for committing an attestation to Base. The listed price is $0.02 USDC plus L1 gas.
  • zk_list_circuits for returning the circuit catalog. The catalog is available inline even while the backend is pending.
  • zk_query_attestation for querying an attestation.

These tools are defined for the v0.1.1 RFC surface.

Limitations and notes

Hive Zk Attestation MCP server is RFC-stage software, so production availability should not be assumed. The tool surface, costs, and circuit catalog are described as stable for the v0.1 RFC, but the backend integration remains pending.

Aleo accounts use BLS12-377 scalar-field keypairs and are separate from Base or Solana keys. An agent that verifies on Aleo therefore needs a separate Aleo account. The project does not implement native Groth16 verification on Aleo; translating Groth16 over BN254 into a snarkVM-compatible path is described as research requiring a large constraint circuit.

Leo deployment costs are outside this MCP shim. The README estimates roughly 1.5 to 2 ALEO credits per Leo program on Aleo mainnet and says the future hive-leo-circuits repository will carry that work. No Leo circuit repository is included here. Base anchoring also does not move value between Base and Aleo; it records a proof commitment only.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Hive Zk Attestation

Hive Zk Attestation is an MCP server that connects agent runtimes to zero-knowledge attestation workflows and exposes tools for emitting state-hash/DID attestations, verifying proofs, anchoring commitments to Base, listing circuits, and querying attestations. It targets Aleo snarkVM as the primary verification path, while native Hive verification remains pending.

Consult the repository for setup instructions before attempting deployment.

The circuit catalog for `zk_list_circuits` is returned inline.

Aleo snarkVM using Varuna over BLS12-377 is the primary verification target. Native Hive verification is planned but not live, while Risc0 and Plonky2 are research targets and are not implemented.

No. The system anchors proof commitments to Base but does not bridge tokens, wrap value, custody funds, or transfer assets between Base and Aleo.

Related MCP servers

All in Cryptography All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewHive Zk Attestation AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/hive-zk-attestation?style=directory)](https://allmcps.com/mcp/hive-zk-attestation)
HTML Embed
<a href="https://allmcps.com/mcp/hive-zk-attestation"><img src="https://allmcps.com/api/badge/hive-zk-attestation?style=directory" alt="Hive Zk Attestation on AllMCPs" /></a>