Hive MCP server implementing the EIP-712 over USB/DMK ledger-bridge integration spec…
io.github.srotzin/hive-mcp-ledger-bridge (MCP)
Hive MCP server implementing the “EIP-712 over USB/DMK ledger-bridge” integration spec, using Model Context Protocol. It is described as part of the Hive Civilization ecosystem and is tied to a specific signer-backend contract exposed by contrib/ledger-bridge in shisa-ai/shisad.
🛠️ Key Features
Implements EIP-712 over USB/DMK ledger-bridge integration spec
Uses the same signer-backend contract as shisa-ai/shisad (contrib/ledger-bridge)
Positioned as a complement to, not a replacement for, shisa-ai/shisad
🚀 Use Cases
Integrate EIP-712 signing via USB/DMK ledger-bridge through an MCP server
Work alongside shisa-ai/shisad to support ledger-bridge workflows
⚡ Developer Benefits
Aligns with an existing signer-backend contract (contrib/ledger-bridge) for compatibility
Clearly documented as complementary with shisa-ai/shisad
⚠️ Limitations
Complements shisad rather than replacing it; it is not presented as a standalone substitute
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 intent_envelope_hash after on-device review
ledger-bridge
shisa-ai (in contrib/)
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 (hivetrust, hive-mcp-identity)
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.
ConfirmationLevel Enum
From the shisa-ai/shisad specification:
Level
Name
Integer
L0
SOFTWARE
0
L1
REAUTHENTICATED
1
L2
BOUND_APPROVAL
2
L3
SIGNED_AUTHORIZATION
3
L4
TRUSTED_DISPLAY_AUTHORIZATION
4
This server uses the enum verbatim. No extensions, no invented tiers.
Tools
Tool
Description
Default ConfirmationLevel
ledger_intent_envelope_create
Build an IntentEnvelope with EIP-712 domain separator and intent_envelope_hash
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.
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.
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.