
Hive Secrets
io.github.srotzin由 GitHub 帳號 srotzin 發布v1.0.0更新於 Oct 24, 2026
Encrypted secret store and rotation for autonomous agent credentials
發布方自己的服務:Secrets.RealEstate
概覽
一個遠端 MCP 伺服器,依代理命名空間加密存放與讀取代理憑證,讀寫操作以 Base 上的 USDC 付費結算。
- 可以做什麼
- 依命名空間與鍵存放、讀取、刪除密鑰,靜態加密採用 AES-256-GCM,並限定在呼叫方代理 DID 的命名空間內。列出某個命名空間中的鍵。讀取依命名空間記錄的稽核日誌,包含付款與錯誤事件。查看當日營收快照與服務健康狀態。付費操作需提供 Base USDC 交易雜湊,服務會先在鏈上核驗再執行呼叫。
- 適用情境
- 適用於自主代理需要在多次執行之間託管保存 API 金鑰等憑證、且依代理身分隔離,並能接受為讀寫支付少量 USDC 單次費用的情境。
- 執行需求
- 遠端 streamable-HTTP 端點;無需本機安裝,也未宣告身分驗證。付費呼叫需向營運方錢包發起 Base USDC 轉帳,並在請求內容或 x402-tx-hash 標頭中提供交易雜湊。自架需要 Node.js、npm 與 SECRETS_MASTER_KEY 環境變數;未設定時寫入會回傳 503。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Hive Secrets,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.srotzin%2Fhive-mcp-secrets/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"hive-secrets": {
"type": "http",
"url": "https://hive-mcp-secrets.onrender.com/mcp"
}
}
}README
hive-mcp-secrets
[srotzin/hive-mcp-secrets MCP server]
Encrypted secret store for the A2A network — Hive Civilization. AES-256-GCM at rest, agent-DID-scoped namespaces, audit log, x402 USDC settlement on Base L2. MCP 2024-11-05. Inbound only.
Agents put encrypted secrets keyed by (namespace, key) and retrieve them later. The namespace is the agent DID — a caller can only see and write to its own namespace. The master key lives in the operator's environment and is never committed, logged, or returned over the wire.
Quick start
Hosted endpoint: https://hive-mcp-secrets.onrender.com/mcp
Tools and pricing
All payments are inbound. Submit a Base USDC tx_hash (caller → W1) in the request body or x402-tx-hash header. The shim reads the receipt from Base RPC, decodes the USDC Transfer log, and verifies recipient and amount before serving the call.
Operator note — master key required for writes
hive-mcp-secrets reads SECRETS_MASTER_KEY from the process environment at startup.
- If set, it is parsed as 64-char hex → 32 raw bytes; or as base64 → 32 raw bytes; or otherwise SHA-256 hashed to 32 bytes.
- If not set, writes return
503 service_unavailablewithreason: "SECRETS_MASTER_KEY not set". Reads of records that do not exist return404as usual; reads of stored records require the same key that wrote them, since AES-256-GCM rejects decryption with any other key.
The key is never committed to the repository, never logged, and never returned over the wire. Operators are expected to set it in the deployment environment (Render env var, Kubernetes secret, etc.) before enabling production traffic. Rotating the key invalidates all previously stored ciphertexts.
Namespace model
The namespace parameter on every endpoint is the agent DID that owns the data. Every endpoint enforces caller_did === namespace and returns forbidden_namespace_mismatch otherwise. There is no superuser, no cross-namespace read, and no multi-DID sharing in v1.
The audit log is per-namespace and records every action — get, put, delete, list, audit, plus the negative paths payment_required, error:not_found, error:integrity_check_failed, etc. Entries store caller_did, action, ts_ms, and (for paid ops) tx_hash, payer, and amount_usd.
REST endpoints
PUT /v1/secrets/{namespace}/{key} body
Without tx_hash, the response is a 402 envelope:
Encryption details
- Algorithm:
aes-256-gcm(FIPS-recognized AEAD) - Key length: 32 bytes
- IV length: 12 bytes, fresh
crypto.randomBytes(12)per record - Auth tag length: 16 bytes
- Storage: SQLite
secretstable —(namespace, key, ciphertext, iv, auth_tag, created_ms, updated_ms, version)with PRIMARY KEY(namespace, key) - Write path:
node:crypto.createCipheriv → update → final, thengetAuthTag(). All three values stored as base64 TEXT. - Read path:
createDecipheriv → setAuthTag → update → final. Any single bit flipped inciphertext,iv, orauth_tagcausesfinal()to throw, which surfaces asintegrity_check_failed.
The smoke test below verifies tampered ciphertext fails to decrypt — this is real AES-GCM, not an integrity check tacked on after the fact.
MCP usage
Local smoke test
Hosting
Deployed to Render: srv hive-mcp-secrets, oregon, starter, autoDeploy=true. The Render env var SECRETS_MASTER_KEY is the operator's responsibility to set. Without it, the deployed service still runs, /health reports master_key_loaded: false, and writes return 503.
License
MIT — see LICENSE.
Hive Civilization Directory
Part of the Hive Civilization — agent-native financial infrastructure.
- Endpoint Directory: https://thehiveryiq.com
- Live Leaderboard: https://hive-a2amev.onrender.com/leaderboard
- Revenue Dashboard: https://hivemine-dashboard.onrender.com
- Other MCP Servers: https://github.com/srotzin?tab=repositories&q=hive-mcp
Brand: #C08D23
來源:README.md,提交 d7d19b7
工具
0版本歷史
1- v1.0.0最新Sep 16, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具必需15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
其他 Secrets 整合
Secrets.RealEstate
realestate.secrets官方發布者
遠端 MCP 端點,讓助理取得有來源的法國房產情報:地址的成交價、能耗、風險、治安與學校資料。

Bitwarden Public API and Secrets Manager (unofficial)
由 GitHub 帳號 mguttmann 發布
非官方本機 MCP 伺服器,讓助理管理 Bitwarden 組織的成員、群組、集合、原則,以及 Secrets Manager 的專案與密鑰。

LLM Data Guard: PII & Secrets Redaction
由 GitHub 帳號 fairquery 發布
在文字、HTML或PDF進入LLM之前,檢測並遮蓋其中的PII和機密資訊(API金鑰、權杖)。AI 翻譯

Keeper Secrets Manager
由 GitHub 帳號 WYRE-AI 發布
Read-only multitenant Streamable HTTP bridge over Keeper Secrets Manager's MCP server.

Keeper Secrets Manager
由 GitHub 帳號 wyre-technology 發布
唯讀的多租戶 HTTP 橋接服務,重新提供 Keeper Secrets Manager 的 MCP 伺服器,讓助理依租戶列出、搜尋與讀取保險庫機密。