Hive Openclaw Bridge

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

Reference integration with @kinthaiofficial OpenClaw 3-layer payment governance

發布方自己的服務：OpenClaw Direct

已驗證Streamable HTTP可網頁執行金融開發者工具商業與電商

服務詳細資訊

識別碼: io.github.srotzin/hive-mcp-openclaw-bridge
傳輸: Streamable HTTP
執行環境: Web executable
信任: Verified
發布於: Sep 16, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此條目所屬的 GitHub 帳號 srotzin。這並不表明該帳號就是產品方。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.srotzin%2Fhive-mcp-openclaw-bridge.svg)](https://sourceweft.com/mcp/io.github.srotzin%2Fhive-mcp-openclaw-bridge?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

一個遠端 MCP 橋接服務，讓助理檢視並依四層支付預算進行支出，同時訂閱 Hive Gamification 的付費門。

可以做什麼: 檢視命名空間、使用者、代理與任務四層的預算上限、已花費、預留額度與剩餘額度，並可覆寫某一鍵的上限，或針對擬議金額與範圍做唯讀預檢。列出八個付費門及其端點、價格、資產與期限，並取得單一門的即時經濟資料。領取首次免費優惠。透過受控路徑訂閱門：原子預留預算、向上游發出請求，然後結算或釋放。
適用情境: 當你希望助理對 Hive Gamification 端點發出受預算約束的付費呼叫，或示範內部層級預算與外部結算之間的銜接時使用。它是參考整合，而非通用工具。
執行需求: 遠端 streamable HTTP 端點；未宣告驗證、環境變數或請求標頭。README 中的本機快速啟動則需要 Node.js、npm install 與監聽埠，並可選用上游基礎位址、逾時與各層預設上限的設定。

安裝前請注意

呼叫付費門會在真實鏈路上花費 USDC，各門價格從 0.15 到 10.00 USDC 不等，README 聲明沒有模擬結算。預算上限可被覆寫，設定不當可能導致支出超出預期。請求會傳送至第三方上游服務。

安裝

在 SourceWeft 中

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

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

交給代理程式安裝

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

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

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

其他 MCP 客戶端

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

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

README

hive-mcp-openclaw-bridge

[srotzin/hive-mcp-openclaw-bridge MCP server]

Reference integration with @kinthaiofficial's OpenClaw 3-layer payment governance framework. MCP server that wraps Hive Gamification's 8 BOGO doors behind a 4-level hierarchical budget — atomic reserve, upstream POST, settle/release. Real rails. No mock settlement.

Brand: Hive Civilization gold #C08D23 (Pantone 1245 C). License: MIT.

Why this exists

OpenClaw's three-layer model splits payment governance into three concerns:

Layer	Concern	Where it lives
Layer 1	Internal hierarchical budget — atomic reserve / settle	this server
Layer 2	Inter-agent millicent ledger settled at epoch boundaries	OpenClaw
Layer 3	External x402 settlement on real rails	Hive Gamification

This bridge demonstrates the Layer 1 ↔ Layer 3 seam. Every paid call to a Hive door (computational-debt, protocol-consensus-tax, pheromone-priority, zk-compliance-shield, capability-leasing, guild-synergy, audit-trail-premium, bounty-routing) is gated by an atomic reservation against every level in the caller's scope path:

The most-restrictive level governs. If any level is short of headroom, the upstream HTTP request is never made and no x402 settlement is signed.

The same BudgetHook interface is exposed from @hivemorph/qvac-client v0.2 — drop your own implementation in to wire this hierarchy into a different runtime.

Background reading

Agent wallet economic models for autonomous agents — kinthai
221 agents: multi-agent coordination lessons — kinthai
agents.kinthai.ai — running on OpenClaw

Tools

Tool	What it does
`budget_status`	Inspect caps, spend, reservations, headroom across all 4 levels
`budget_set_cap`	Override a per-key cap at one level
`budget_check`	Read-only pre-flight against a proposed amount + scope
`doors_list`	List all 8 BOGO doors with endpoint, price, asset, term
`door_economics`	Fetch live `/economics` for one door
`bogo_claim`	Claim first-use-free via `/v1/bogo/claim`
`door_subscribe`	Canonical gated path — atomic reserve → upstream POST → settle/release

Doors

Door	Endpoint	Price	Term
computational-debt	`/v1/debt/subscribe`	0.50 USDC	30d
protocol-consensus-tax	`/v1/pct/subscribe`	0.25 USDC	1 read
pheromone-priority	`/v1/pheromone/subscribe`	5.00 USDC	30d
zk-compliance-shield	`/v1/compliance/subscribe`	1.00 USDC	30d
capability-leasing	`/v1/lease/start`	0.15 USDC	1h
guild-synergy	`/v1/guild_synergy/subscribe`	10.00 USDC	30d
audit-trail-premium	`/v1/audit_premium/subscribe`	3.00 USDC	30d
bounty-routing	`/v1/bounty_routing/route`	0.50 USDC	1 routing

Backend: https://hive-gamification.onrender.com. All endpoints are live and verified.

Lifecycle of a paid call

client → tools/call door_subscribe { door_id, did, scope }       → atomicReserve(scope, price, asset)           ├─ each level checked: namespace, user, agent, task           ├─ headroom = cap − spent − reserved           └─ short on any level? reject before signing       → POST hive-gamification.onrender.com<endpoint>       → 2xx? settle(reservationId)         non-2xx or throw? release(reservationId)       → return { ok, reservationId, binding_level, upstream }

client → tools/call door_subscribe { door_id, did, scope }       → atomicReserve(scope, price, asset)           ├─ each level checked: namespace, user, agent, task           ├─ headroom = cap − spent − reserved           └─ short on any level? reject before signing       → POST hive-gamification.onrender.com<endpoint>       → 2xx? settle(reservationId)         non-2xx or throw? release(reservationId)       → return { ok, reservationId, binding_level, upstream }

Quickstart

bash

git clone https://github.com/srotzin/hive-mcp-openclaw-bridgecd hive-mcp-openclaw-bridgenpm installnpm start

git clone https://github.com/srotzin/hive-mcp-openclaw-bridgecd hive-mcp-openclaw-bridgenpm installnpm start

Then from any MCP client:

Configuration

Env	Default	Meaning
`PORT`	`3000`	listen port
`HIVE_BASE`	`https://hive-gamification.onrender.com`	upstream base URL
`HIVE_TIMEOUT_MS`	`15000`	upstream fetch timeout
`NAMESPACE_CAP`	`50`	default namespace-level cap (USDC)
`USER_CAP`	`10`	default user-level cap
`AGENT_CAP`	`2`	default agent-level cap
`TASK_CAP`	`0.50`	default task-level cap

Per-key caps override defaults via budget_set_cap.

@hivemorph/qvac-client v0.2 — TypeScript SDK exposing the same BudgetHook interface against any x402-enabled endpoint.
Hive Gamification agent card — A2A 0.1 advertisement of the 8 doors.