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 分