English Français العربية

Hive Sla Monitor

Official registry AI and agents

Service level agreement monitoring for the Hive agent fleet

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http hive-sla-monitor 'https://hive-mcp-sla-monitor.onrender.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "hive-sla-monitor": {
            "type": "http",
            "url": "https://hive-mcp-sla-monitor.onrender.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. hive-mcp-sla-monitor
  2. Observation only
  3. Surface
  4. Tools
  5. Probe semantics
  6. x402 envelope
  7. Settlement
  8. Environment
  9. Run
  10. License
  11. Hive Civilization Directory

hive-mcp-sla-monitor

SLA observation broker for the A2A network. Agents register a public health endpoint with target uptime and p95 latency; the shim probes it on a 60s schedule (read-only HTTP, 8s timeout) and records the result. When a rolling window misses the targets, a breach record is written. Reading breach records is paid. Inbound only. ENABLE=true by default.

Brand color: #C08D23 (Pantone 1245 C, Hive Civilization gold).

Observation only

Hive does not underwrite or settle SLA claims. This is observational data only. The shim does not hold custody, does not pay claims, and does not indemnify counterparties. The disclaimer rides every paid response and every breach record.

Surface

LayerEndpointDescription
MCPPOST /mcpJSON-RPC 2.0, Streamable-HTTP, protocol 2024-11-05.
DiscoveryGET /.well-known/mcp.jsonTool list and transport metadata.
RESTPOST /v1/sla/registerRegister an endpoint. 402 if no proof.
RESTGET /v1/sla/status/{id}Read observed uptime and p95. 402 if no proof.
RESTGET /v1/sla/breaches?monitor_id=…Read recent breach records. 402 if no proof.
RESTGET /v1/sla/todayUTC-day ledger snapshot. Free.
HealthGET /healthLiveness, pricing, recipient address.
RootGET /HTML for browsers, JSON for agents (Accept-header sniff).

Tools

NameTierCostDescription
sla_register1$0.01/probeRegister a public endpoint for probing.
sla_status1$0.01Read observed uptime and p95 over the rolling window.
sla_breach_history2$0.10Read recent breach records. Disclaimer rides every record.
sla_unregister0freeDeactivate a monitor.

Probe semantics

The scheduler scans active monitors every 60 seconds and issues a GET with an 8-second timeout. 2xx and 3xx count as up; 5xx and timeouts count as down. Probe rows are stored at /tmp/sla.db along with the monitor record and any breach records.

The breach evaluator runs after each probe. It looks at the rolling window (default 60 minutes), computes observed uptime and observed p95 latency, and records a breach if either target is missed. Repeated breaches inside half the window are de-bounced so a single bad window does not fan out.

The service caps active monitors at 100 (SLA_MAX_MONITORS) to keep probe fan-out deterministic.

x402 envelope

Every paid endpoint returns a 402 envelope on first hit:

{
  "error": "payment_required",
  "x402_version": 1,
  "disclaimer": "Hive does not underwrite or settle SLA claims. This is observational data only.",
  "payment": {
    "nonce": "…",
    "amount_usd": 0.01,
    "accept_min_usd": 0.007,
    "accepts": [{
      "chain": "base",
      "asset": "USDC",
      "contract": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
      "decimals": 6,
      "recipient": "0x15184bf50b3d3f52b60434f8942b7d52f2eb436e",
      "scheme": "exact"
    }],
    "tier": 1,
    "product": "sla_register",
    "floor_pct": 0.7
  }
}

Submit the proof inline via X-Payment header on the retry, or POST it to mint an access token used in X-Hive-Access.

Pricing inherits the hivemorph barter floor pattern: the envelope advertises both amount_usd (asking) and accept_min_usd (floor). A client may submit a proof whose on-chain paid amount is anywhere in [floor, asking] and the shim accepts it.

Settlement

USDC on Base L2 (0x833589fcd6edb6e08f4c7c32d4f71b54bda02913) to the recipient address above. Verification reads Transfer logs on the receipt against the configured Base RPC. Real chain reads, no mocks. A single tx_hash may only be redeemed once.

Environment

VariableDefaultNotes
PORT3000HTTP port.
ENABLEtrueWhen false, only /health and / respond.
WALLET_ADDRESS0x1518…436eUSDC recipient.
SLA_REGISTER_PRICE_USDC0.01Per registration.
SLA_BREACH_PRICE_USDC0.10Per breach-history read.
SLA_STATUS_PRICE_USDC0.01Per status read.
SLA_PROBE_INTERVAL_MS60000Probe loop interval.
SLA_PROBE_TIMEOUT_MS8000Per-probe HTTP timeout.
SLA_MAX_MONITORS100Active monitor cap.
BASE_RPC_URLhttps://mainnet.base.orgBase L2 JSON-RPC.
SLA_DB_PATH/tmp/sla.dbSQLite path.

Run

npm install
npm start
# → http://localhost:3000/health

License

MIT. Author: Steve Rotzin <steve@thehiveryiq.com>.

Hive Civilization Directory

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

Brand: #C08D23

Frequently asked questions

What is Hive Sla Monitor?

Service level agreement monitoring for the Hive agent fleet

How do I install Hive Sla Monitor?

It runs as a remote server. In Claude Code: claude mcp add --transport http hive-sla-monitor 'https://hive-mcp-sla-monitor.onrender.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Hive Sla Monitor need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Hive Sla Monitor open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Hive Sla Monitor?

It is published by srotzin. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.