Hive Ledger Bridge

io.github.srotzin由 GitHub 帳號 srotzin 發布v1.0.0更新於 Oct 24, 2026

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

已驗證Streamable HTTP可網頁執行金融安全與監控

概覽

AI 產生的概覽

遠端 MCP 伺服器，用來建構、驗證並見證 EIP-712 意圖信封，搭配 Ledger 硬體簽章流程使用。

可以做什麼
  • 建構意圖信封，產生 EIP-712 網域分隔符與 intent_envelope_hash，並提供建議的確認等級
  • 驗證給定的 intent_envelope_hash 是否與信封內容相符
  • 依操作類型與金額查詢所需的 ConfirmationLevel（L0–L4）
  • 記錄 Hive 端見證，說明裝置已在 L3 或 L4 回傳 ECDSA 簽章
  • 讀取合作夥伴目錄，包含 shisad 參考實作、Ledger Live 與 Hive 聯絡資訊
適用情境
適合需要把代理程式或 shisad 類政策守護程序接到 Ledger 裝置，並在硬體聯署前建構、驗證或見證 EIP-712 意圖信封的情境。其他用途基本上不需要加入。
執行需求
需要一個遠端 streamable-HTTP 端點；未宣告本機執行環境、套件、API 金鑰或請求標頭。README 表示此服務以 Node.js 為基礎，並搭配 shisa-ai/shisad 的 ledger-bridge 與 Ledger 裝置完成實際簽章。
安裝前請注意
此伺服器處理簽章意圖：信封包含收款地址、金額、鏈 ID 與代理程式 DID，見證工具還會接收 ECDSA 簽章，都應視為敏感資料。見證僅是稽核紀錄，並非鏈上結算。README 列出資金庫地址與 USDC 合約地址，任何付款流程都應自行核實後再轉帳。清單未宣告任何身分驗證，且 README 中的端點主機與清單不一致。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Hive Ledger Bridge，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.srotzin%2Fhive-mcp-ledger-bridge/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

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

來源：README.md，提交 ec73fc8

工具

0
SourceWeft 尚未讀取此伺服器的工具。

版本歷史

1
  1. v1.0.0最新Sep 16, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分