Reference integration with @kinthaiofficial OpenClaw 3-layer payment governance
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-srotzin-hive-mcp-openclaw-bridge": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Reference integration with @kinthaiofficial OpenClaw 3-layer payment governance
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in finance
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
A Model Context Protocol (MCP) server that provides AI assistants with direct access to the Spreedly payments API. Enables LLMs to manage gateways, process transactions, tokenize payment methods, and more, through structured, validated tool calls.
MCP server for InsightSentry financial data API - market data, options, screeners, and more
AI agents get on-chain identity, credentials, reputation, escrow, and persistent memory on XRPL.
MCP Security Weekly
Get CVE alerts and security updates for io.github.srotzin/hive-mcp-openclaw-bridge and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
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:
Namespace → User → Agent → Task
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.
| 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 |
| 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.
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 }
git clone https://github.com/srotzin/hive-mcp-openclaw-bridge
cd hive-mcp-openclaw-bridge
npm install
npm s
... [View full README on GitHub](https://github.com/srotzin/hive-mcp-openclaw-bridge#readme)