Mcp

Hive Insurance

Agent liability insurance — claims, premiums, and on-chain payouts

Verified: 2026-05-13 (mcp-registry-ingest-2026-05-13+enrich-capability-skill)

When to use Hive Insurance

Choose if

You're explicitly designing inside the Hive Civilization stack and want parametric insurance primitives (uptime SLA, treasury slippage, oracle-failure coverage) callable from an agent loop, with claim payouts settled on-chain in Base L2 USDC via x402. The broker layer is live; pair with sibling Hive MCPs (storage, MOS) sharing the same gateway and earn rails.

Avoid if

README explicitly tags this as "scaffold shim — backend pending Q3 2026." The README does NOT enumerate any tools beyond the Hive earn-rails shared infrastructure, so the insurance-specific endpoints are not yet substantively callable. Also avoid for any use case outside DID + x402 + Base — there is no integration with conventional insurance carriers, no fiat settlement path, no regulatory accreditation disclosed.

Risk Flags

  • HIGH runtime README explicitly states "Scaffold shim — backend pending Q3 2026." Broker layer operational; underwriter layer in development. Treat as a discovery anchor, not a live insurance substrate.
  • MEDIUM scope Only meaningful inside the Hive Civilization stack (DID identity + x402 + Base USDC). No fiat path, no conventional carrier integration, no regulatory disclosure.
  • LOW data_quality No tool inventory or pricing detail in the README — only the gateway URL and discovery surface are documented. Verify actual tool list and pricing via live MCP `tools/list` before designing flows.

Cost

Type: Usage based

Distribution

MCP Registry
io.github.srotzin/hive-mcp-insurance
Repository
https://github.com/srotzin/hive-mcp-insurance