Skip to main content
Glama

Hive Sla Monitor

by io.github.srotzin
OverviewDiscussionsAdmin

Server Details

Service level agreement monitoring for the Hive agent fleet

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
srotzin/hive-mcp-sla-monitor
GitHub Stars
0
Server Listing
hive-mcp-sla-monitor

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a distinct purpose: register adds a monitor, unregister removes it, status shows current metrics, and breach_history provides past records. No overlap or ambiguity.

Naming Consistency5/5

All tools follow the consistent pattern 'sla_' followed by a descriptive noun in snake_case (register, unregister, status, breach_history), making naming predictable.

Tool Count5/5

Four tools cover the core lifecycle of an SLA monitor (create, read status, read history, delete) without unnecessary extras, fitting the domain well.

Completeness4/5

The set covers registration, status, breach history, and unregistration, but lacks a tool to list all registered monitors or update monitor parameters, which are minor gaps.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updates
    • First observedsla_breach_history
    • First observedsla_register
    • First observedsla_status
    • First observedsla_unregister

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources