Hive Ledger Bridge

Official registry Other

Hive MCP server implementing the EIP-712 over USB/DMK ledger-bridge integration spec…

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http hive-ledger-bridge 'https://hive-mcp-gateway.onrender.com/ledger-bridge/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "hive-ledger-bridge": {
            "type": "http",
            "url": "https://hive-mcp-gateway.onrender.com/ledger-bridge/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. hive-mcp-ledger-bridge
  2. Partner Doctrine
  3. ConfirmationLevel Enum
  4. Tools
  5. Endpoints
  6. Connect
  7. Integration with shisad
  8. Infrastructure
  9. License
  10. Hive Civilization Directory

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

LayerOperatorFunction
Hardware countersignatureLedger deviceEIP-712 signature over intent_envelope_hash after on-device review
ledger-bridgeshisa-ai (in contrib/)Signer-backend contract; HTTP-to-USB/DMK adapter
8-layer PEP + ConfirmationLevelshisadPer-call policy enforcement; routes confirmation to backend
DID resolution + identity passportHive (hivetrust, hive-mcp-identity)Read-only identity surface
Spectral receiptsHiveSettlement 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.


ConfirmationLevel Enum

From the shisa-ai/shisad specification:

LevelNameInteger
L0SOFTWARE0
L1REAUTHENTICATED1
L2BOUND_APPROVAL2
L3SIGNED_AUTHORIZATION3
L4TRUSTED_DISPLAY_AUTHORIZATION4

This server uses the enum verbatim. No extensions, no invented tiers.


Tools

ToolDescriptionDefault ConfirmationLevel
ledger_intent_envelope_createBuild an IntentEnvelope with EIP-712 domain separator and intent_envelope_hashDerived from action
ledger_intent_envelope_verifyVerify intent_envelope_hash matches envelope contentsRead-only / none
ledger_confirmation_level_queryReturn required ConfirmationLevel for an intentRead-only / none
ledger_signed_authorization_attestHive-side attestation that an intent reached L3 or L4L3 / L4 required
ledger_partner_directoryPartner integration directory: shisad reference, Ledger Live, Hive contactRead-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

PathMethodDescription
/healthGETService health and version
/.well-known/mcp.jsonGETMCP manifest
/mcpPOSTJSON-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

PropertyValue
TransportStreamable-HTTP, JSON-RPC 2.0, MCP 2024-11-05
RuntimeNode.js ≥ 18, ESM
LLM (if extended)https://hivecompute-g2g7.onrender.com/v1/compute/chat/completions
Treasury0x15184bf50b3d3f52b60434f8942b7d52f2eb436e
USDC (Base)0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Brand#C08D23
Spec referenceshisa-ai/shisad contrib/ledger-bridge
Ledger partner programdevelopers.ledger.com

License

MIT — see LICENSE.

Contact: steve@thehiveryiq.com

Hive Civilization Directory

Part of the Hive Civilization — agent-native financial infrastructure.

Brand: #C08D23

Frequently asked questions

What is Hive Ledger Bridge?

Hive MCP server implementing the EIP-712 over USB/DMK ledger-bridge integration spec…

How do I install Hive Ledger Bridge?

It runs as a remote server. In Claude Code: claude mcp add --transport http hive-ledger-bridge 'https://hive-mcp-gateway.onrender.com/ledger-bridge/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Hive Ledger Bridge need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Hive Ledger Bridge open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Hive Ledger Bridge?

It is published by srotzin. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.