hive-mcp-sla-monitor
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hive-mcp-sla-monitorregister https://api.example.com/health for SLA monitoring"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: chiark-mcp
Surface
Layer | Endpoint | Description |
MCP |
| JSON-RPC 2.0, Streamable-HTTP, protocol |
Discovery |
| Tool list and transport metadata. |
REST |
| Register an endpoint. 402 if no proof. |
REST |
| Read observed uptime and p95. 402 if no proof. |
REST |
| Read recent breach records. 402 if no proof. |
REST |
| UTC-day ledger snapshot. Free. |
Health |
| Liveness, pricing, recipient address. |
Root |
| HTML for browsers, JSON for agents (Accept-header sniff). |
Tools
Name | Tier | Cost | Description |
| 1 | $0.01/probe | Register a public endpoint for probing. |
| 1 | $0.01 | Read observed uptime and p95 over the rolling window. |
| 2 | $0.10 | Read recent breach records. Disclaimer rides every record. |
| 0 | free | Deactivate 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
Variable | Default | Notes |
|
| HTTP port. |
|
| When false, only |
|
| USDC recipient. |
|
| Per registration. |
|
| Per breach-history read. |
|
| Per status read. |
|
| Probe loop interval. |
|
| Per-probe HTTP timeout. |
|
| Active monitor cap. |
|
| Base L2 JSON-RPC. |
|
| SQLite path. |
Run
npm install
npm start
# → http://localhost:3000/healthLicense
MIT. Author: Steve Rotzin steve@thehiveryiq.com.
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
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceProvides a unified registry for discovering and managing agents that implement the A2A (Agent-to-Agent) protocol, enabling registration, querying, and CRUD operations on agent metadata through both REST API and MCP tools.Last updated183MIT
- AlicenseAqualityFmaintenanceFind the most reliable AI agent for any task. Search 2,000+ agents across A2A and MCP with quality filters — min uptime, max latency, score thresholds. Check if an agent is alive before routing to it. Like Artificial Analysis, but for agent services.Last updated5MIT
- Alicense-qualityDmaintenanceMCP server for agent network monitoring. Aggregates real-time population counts, transaction volume, and health metrics across multi-service agent infrastructure.Last updatedMIT
- Alicense-qualityBmaintenanceMCP server for cross-platform agent onboarding. Registers external agents, translates intents from LangChain, CrewAI, AutoGen, and A2A formats, and proxies cross-ecosystem transactions.Last updatedMIT
Related MCP Connectors
Usage metering + SLA accounting for agent services (the meter behind x402 micropayments).
Real-time health monitoring and heartbeat tracking for agent services
Single entry point for the GOSCE portfolio: routes orchestrators to verified agents by capability, w
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/srotzin/hive-mcp-sla-monitor'
If you have feedback or need assistance with the MCP directory API, please join our Discord server