Hive Ledger Bridge

io.github.srotzinPublished by GitHub account srotzinv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that builds, verifies and attests EIP-712 intent envelopes for a Ledger hardware-signing workflow.

What you can do
  • Build intent envelopes with an EIP-712 domain separator and intent_envelope_hash, plus a suggested confirmation level
  • Verify that a supplied intent_envelope_hash matches the envelope contents
  • Query the required ConfirmationLevel (L0-L4) for a given action and amount
  • Record a Hive-side attestation that a device returned an ECDSA signature at L3 or L4
  • Read a partner directory listing the shisad reference, Ledger Live and Hive contact
When to use it
Useful if you are wiring an agent or a shisad-style policy daemon to a Ledger device and need to construct, check or attest EIP-712 intent envelopes before a hardware countersignature. Most other users have no reason to add it.
Requirements
A remote streamable-HTTP endpoint; no local runtime, package, API key or header is declared. The README describes the service as Node.js based and pairs it with the shisa-ai/shisad ledger-bridge and a Ledger device for the actual signing.
Before you install
The server handles signing intents: envelopes carry recipient addresses, amounts, chain IDs and agent DIDs, and the attest tool accepts an ECDSA signature, so treat all of it as sensitive. Attestation is an audit record, not on-chain settlement. The README lists a treasury address and a USDC contract, so verify any payment flow independently before sending funds. The manifest declares no authentication, and the README's endpoint host differs from the manifest's.

Installation

In SourceWeft

  1. Open Hive Ledger Bridge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.srotzin%2Fhive-mcp-ledger-bridge/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "hive-ledger-bridge": {
      "type": "http",
      "url": "https://hive-mcp-gateway.onrender.com/ledger-bridge/mcp"
    }
  }
}

README

hive-mcp-ledger-bridge

[srotzin/hive-mcp-ledger-bridge MCP server]

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.

json
{  "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

json
{ "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.

json
{  "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

bash
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

bash
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: [email protected]

Hive Civilization Directory

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

Brand: #C08D23

Source: README.md at commit ec73fc8

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts