hive-mcp-ledger-bridge
Integrates with the Hive blockchain to provide tools for creating and verifying EIP-712 intent envelopes, querying confirmation levels, and attesting signed authorizations via a ledger-bridge.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hive-mcp-ledger-bridgecreate intent envelope for 100 USDC transfer"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
hive-mcp-ledger-bridge
Hive Civilization — EIP-712 over USB/DMK ledger-bridge MCP server.
Implements the same signer-backend contract that shisa-ai/shisad exposes through contrib/ledger-bridge. Ledger is a partner. This server complements shisad — it does not replace it.
Partner Doctrine
Layer | Operator | Function |
Hardware countersignature | Ledger device | EIP-712 signature over |
ledger-bridge | shisa-ai (in | Signer-backend contract; HTTP-to-USB/DMK adapter |
8-layer PEP + ConfirmationLevel | shisad | Per-call policy enforcement; routes confirmation to backend |
DID resolution + identity passport | Hive ( | Read-only identity surface |
Spectral receipts | Hive | Settlement audit record per fee event |
No overlap. The hardware tier remains Ledger's. The runtime policy tier remains shisad's. Hive contributes IntentEnvelope construction, hash verification, confirmation-level policy, and settlement attestation — all above the PEP, without modifying the ConfirmationLevel enum or the signer-backend contract.
Related MCP server: Cryptair MCP Server
ConfirmationLevel Enum
From the shisa-ai/shisad specification:
Level | Name | Integer |
L0 |
| 0 |
L1 |
| 1 |
L2 |
| 2 |
L3 |
| 3 |
L4 |
| 4 |
This server uses the enum verbatim. No extensions, no invented tiers.
Tools
Tool | Description | Default ConfirmationLevel |
| Build an | Derived from |
| Verify | Read-only / none |
| Return required | Read-only / none |
| Hive-side attestation that an intent reached L3 or L4 | L3 / L4 required |
| Partner integration directory: shisad reference, Ledger Live, Hive contact | Read-only / none |
ledger_intent_envelope_create
Build a signed-ready IntentEnvelope. The server produces the EIP-712 domain separator and intent_envelope_hash — the hash is what the Ledger device signs.
{
"intent_id": "uuid-or-did-fragment",
"agent_did": "did:hive:0xabc...",
"action": "transfer",
"target": "0xRecipientAddress",
"amount": "1000.00",
"chain_id": 8453,
"nonce": 1,
"deadline": 1777699200,
"verifying_contract": "0x0000000000000000000000000000000000000000"
}Response includes envelope, intent_envelope_hash, domain_separator, and suggested_confirmation_level.
ledger_intent_envelope_verify
Supply an IntentEnvelope body and an intent_envelope_hash. Returns match: true|false and the recomputed hash.
ledger_confirmation_level_query
{ "action": "transfer", "amount_usd": 50000 }Returns the integer level and name. Useful for pre-call policy checks before routing to the ledger-bridge.
ledger_signed_authorization_attest
Record a Hive-side attestation that a device returned an ECDSA signature at L3 or L4. This is not on-chain settlement — it is an audit record that the intent_envelope_hash was device-countersigned.
{
"intent_envelope_hash": "0xabc...",
"agent_did": "did:hive:0xabc...",
"confirmation_level": 4,
"ecdsa_signature": "0xsignatureHex..."
}ledger_partner_directory
Returns the full partner directory with URLs, roles, and contact information.
Endpoints
Path | Method | Description |
| GET | Service health and version |
| GET | MCP manifest |
| POST | JSON-RPC 2.0 (MCP 2024-11-05) |
Connect
MCP endpoint: https://hiveledgerbridge.onrender.com/mcp (pairs with shisa-ai/shisad contrib/ledger-bridge + future hive-ledger-attest backend)
JSON-RPC 2.0 — tools/list
curl -s -X POST https://hiveledgerbridge.onrender.com/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'JSON-RPC 2.0 — ledger_intent_envelope_create
curl -s -X POST https://hiveledgerbridge.onrender.com/mcp \
-H 'Content-Type: application/json' \
-d '{
"jsonrpc":"2.0","id":2,"method":"tools/call",
"params":{
"name":"ledger_intent_envelope_create",
"arguments":{
"intent_id":"550e8400-e29b-41d4-a716-446655440000",
"agent_did":"did:hive:0xabc",
"action":"transfer",
"target":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"chain_id":8453,
"nonce":1,
"deadline":1777699200
}
}
}'Integration with shisad
shisa-ai/shisad routes trusted_display_authorization (L4) intents through contrib/ledger-bridge — the daemon POSTs an IntentEnvelope plus intent_envelope_hash to the bridge, the user reviews on the Ledger device, and the ECDSA signature returns to the daemon.
This server speaks the same IntentEnvelope / intent_envelope_hash vocabulary. A shisad deployment can use ledger_intent_envelope_create upstream of the bridge call, ledger_intent_envelope_verify on the returned hash, and ledger_signed_authorization_attest to anchor the device signature as a Hive Spectral receipt.
Operator policy continues to control ConfirmationLevel through the standard tools."x".confirmation.level config — no new mechanism required.
Infrastructure
Property | Value |
Transport | Streamable-HTTP, JSON-RPC 2.0, MCP 2024-11-05 |
Runtime | Node.js ≥ 18, ESM |
LLM (if extended) |
|
Treasury |
|
USDC (Base) |
|
Brand |
|
Spec reference | |
Ledger partner program |
License
MIT — see LICENSE.
Contact: steve@thehiveryiq.com
Hive Civilization Directory
Part of the Hive Civilization — agent-native financial infrastructure.
Endpoint Directory: https://thehiveryiq.com
Live Leaderboard: https://hive-a2amev.onrender.com/leaderboard
Revenue Dashboard: https://hivemine-dashboard.onrender.com
Other MCP Servers: https://github.com/srotzin?tab=repositories&q=hive-mcp
Brand: #C08D23
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with the Hive blockchain through the Model Context Protocol, allowing for account info retrieval, content reading/creation, cryptocurrency transfers, and cryptographic operations.Last updated17385ISC
- AlicenseAqualityDmaintenanceEnables AI agents to certify documents, prove agreements, and verify counterparty claims with on-chain receipts on Hedera Hashgraph. Provides tools for document certification, two-party attestation, and agent registration with zero-config setup.Last updated677MIT
- Alicense-qualityDmaintenanceA comprehensive MCP server for secure Ledger hardware wallet integration with Ethereum blockchain operations, enabling AI agents to safely manage crypto assets, sign transactions, and interact with multiple networks.Last updated6MIT
- Flicense-qualityCmaintenanceEnables AI compliance attestation and verification for EU AI Act, HIPAA, and other regulations, with tools for signing, proving, and anchoring AI decisions to Hedera mainnet.Last updated235
Related MCP Connectors
MCP server: NEED + YIELD + CLEAN-MONEY gates with EIP-3009 attestations · Hive Civilization
HiveAddressScreen MCP — pre-settlement on-chain risk screen. 17-vector GoPlus rail
A2A ZK wallet recovery — guardian swarm, no seed phrase, HiveLaw enforcement
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/srotzin/hive-mcp-ledger-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server