Hive Keet Bridge

io.github.srotzin由 GitHub 账号 srotzin 发布v1.0.0更新于 Oct 25, 2026

MCP server bridging holepunchto/keet-identity-key to the Hive agentic identity network

已验证Streamable HTTP可网页运行知识与记忆安全与监控

概览

AI 生成的概览

远程 MCP 桥接服务,可将 Keet 身份密钥解析为 Hive DID、验证 ed25519 签名证明,并把密钥关联到 Hive 注册表。

可以做什么
将 Keet 身份密钥(十六进制或 base58)解析为 did:hive DID 文档和 agent card URI,并查询某密钥的缓存 hyperdht announce 记录(Hive 本身不运营 hyperdht)。验证由 Keet 身份密钥签名的 ed25519 证明,无需网络调用。把 Keet 身份密钥关联到 Hive DID,这是对 Hive 注册表的幂等写入,需要能证明密钥控制权的签名证明。浏览 Holepunch 与 Keet 合作伙伴目录,含规范链接和桥接端点。
适用场景
当助手需要把 Keet 身份密钥映射为 Hive DID、核验某密钥是否签署了特定消息,或在 Hive 注册表中登记密钥与 DID 的关联时适用。主要面向代理身份与证明类工作流,而非通用任务。
运行要求
通过 streamable HTTP 连接的远程 MCP 端点,无需本地运行时或安装包。未声明认证、环境变量或请求头。客户端连接托管网关地址即可。
安装前请注意
关联工具会写入 Hive 注册表,关联密钥前请先确认。身份密钥和证明签名会发送到第三方托管服务。README 提到 x402 代理商业定价和 Hive 金融基础设施,使用前请确认是否存在付费环节。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Hive Keet Bridge,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.srotzin%2Fhive-mcp-keet-bridge/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

README

hive-mcp-keet-bridge

MCP server — Hive–Holepunch/Keet identity bridge

Bridges holepunchto/keet-identity-key (Apache-2.0) into the Hive agentic identity network. Exposes DID resolution, signed attestation verification, and a partner directory as MCP tools. Read-only resolution and attestation — Hive does not operate hyperdht bootstrap nodes or Keet servers.

Holepunch is a partner. This shim composes on top of the Holepunch identity primitive. It does not fork, replace, or compete with Keet, hyperswarm, or hyperdht.


Partner doctrine

LayerOwner
DHT peer discovery and transportHolepunch (hyperswarm, hyperdht)
HD ed25519 key derivationHolepunch (keet-identity-key, Apache-2.0)
Keet UX and messagingHolepunch / Keet
DID resolution and trust registryHive
Signed attestation and receipt layerHive
x402 agent commerce pricingHive

Tools

ToolDescriptionRead-only
keet_identity_resolveResolve a Keet identity key (ed25519, hex or base58) to a did:hive: DID document and agent_card URIYes
keet_did_linkLink a Keet identity key to a Hive DID — idempotent, requires a signed attestation proving key controlWrite (Hive registry only)
keet_signed_attestation_verifyVerify an ed25519 attestation signed by a Keet identity key — no network call requiredYes
keet_hyperdht_announceReturn cached hyperdht announce record for a given identity key — Hive does not operate hyperdhtYes
keet_partner_directoryHolepunch + Keet partner integration directory with canonical links and Hive bridge endpointsYes

Endpoints

PathMethodDescription
/mcpPOSTJSON-RPC 2.0 MCP endpoint (protocol: 2024-11-05)
/healthGETServer health and tool count
/.well-known/mcp.jsonGETMCP manifest

Connect

MCP client config (stdio-compatible HTTP)

json
{  "mcpServers": {    "hive-mcp-keet-bridge": {      "url": "https://hive-mcp-keet-bridge.onrender.com/mcp",      "transport": "http"    }  }}

Smithery

Submit at: https://smithery.ai/new?repo=srotzin/hive-mcp-keet-bridge

Glama / MCP.so

Auto-crawled from GitHub. Claim after 24-72h at:

  • https://glama.ai/mcp/servers/srotzin/hive-mcp-keet-bridge

Usage examples

Resolve a Keet identity key

json
{  "jsonrpc": "2.0",  "id": 1,  "method": "tools/call",  "params": {    "name": "keet_identity_resolve",    "arguments": {      "identity_key": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2"    }  }}

Verify a signed attestation

json
{  "jsonrpc": "2.0",  "id": 2,  "method": "tools/call",  "params": {    "name": "keet_signed_attestation_verify",    "arguments": {      "identity_key": "a1b2c3d4e5f6...",      "message": "did:hive:keet:abc123",      "signature": "<base64-encoded ed25519 signature>"    }  }}

Partner directory

json
{  "jsonrpc": "2.0",  "id": 3,  "method": "tools/call",  "params": {    "name": "keet_partner_directory",    "arguments": { "format": "json" }  }}

Key derivation spec

Identity keys are produced by holepunchto/keet-identity-key — a BIP32-style hierarchical deterministic (HD) derivation generating ed25519 keypairs for the Keet identity system. This library is licensed under Apache-2.0 and is developed and maintained by Holepunch.

Hive's DID composition maps each Keet identity root deterministically to a did:hive:keet:<base64url-pubkey> string. The mapping is purely additive — the Holepunch key derivation spec is unchanged.


Boundary: what Hive does not do

  • Hive does not operate hyperdht bootstrap nodes.
  • Hive does not operate Keet servers or relay traffic.
  • Hive does not fork or modify keet-identity-key.
  • Hive does not issue settlement assets on behalf of Holepunch or Tether.
  • This shim does not claim to run on the Keet network — it resolves and attests.

Runtime

  • Node.js >= 18
  • Express 4.x
  • Zero DHT or P2P dependencies in this shim
  • LLM calls: https://hivecompute-g2g7.onrender.com/v1/compute/chat/completions (Hive internal)

Pairs with

  • holepunchto/keet-identity-key (Apache-2.0) — key derivation spec
  • future: hive-keet-attest backend — signed attestation persistence layer (in roadmap)
  • hive-mcp-inbox spec — peer-to-peer agent messaging over Holepunch transport

License

MIT — see LICENSE.

Composes on top of holepunchto/keet-identity-key, which is licensed under the Apache License, Version 2.0. That library is referenced as a specification — it is not bundled with this package.


Hive Civilization. Brand gold #C08D23. Treasury 0x15184bf50b3d3f52b60434f8942b7d52f2eb436e.

Hive Civilization Directory

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

Brand: #C08D23

来源:README.md,提交 84bbcc9

工具

0
SourceWeft 尚未读取此服务器的工具。

版本历史

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

评分

已满足适用检查项的 75%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。