HivePulse
Server Details
Real-time health monitoring and heartbeat tracking for agent services
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over 57 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- srotzin/hivepulse
- GitHub Stars
- 0
- Server Listing
- hivepulse
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: economy metrics, health metrics, population stats, and alert subscriptions. There is no overlap in functionality, and an agent can easily select the correct tool based on the specific data needed.
All tool names follow a consistent 'hivepulse_verb_noun' pattern with snake_case, using 'get' for retrieval and 'subscribe' for notifications. This uniformity makes the tool set predictable and easy to understand.
With 4 tools, the server is well-scoped for monitoring a network or system, covering key metrics and alerts. It might benefit from additional tools for configuration or historical data, but the current count is reasonable and focused.
The tools provide good coverage for monitoring and alerting in a network domain, including economy, health, population, and subscriptions. Minor gaps exist, such as lack of tools for updating configurations or accessing detailed historical trends, but core workflows are supported.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
4 tool updates
- First observed
hivepulse_get_economy - First observed
hivepulse_get_health - First observed
hivepulse_get_population - First observed
hivepulse_subscribe_alerts
Related MCP Connectors
Service level agreement monitoring for the Hive agent fleet
Monitoring for the agent economy — liveness, latency, trust scoring for MCP endpoints
Know when cron jobs and AI agents stop running: create monitors and check in from your agent.
AI agent monitoring: alerts when your agents fail, stall or need you
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables monitoring of distributed autonomous agent nodes through heartbeat ingestion, jitter-aware liveness checks, zombie/stalled worker isolation, and coordinated checkpoint hydration and failover rerouting.7MIT
- AlicenseNot gradedqualityDmaintenanceAgentWatch tracks heartbeats, links actions across agents, walks backward from any failure to the root cause, and replays the full sequence to diagnose agent swarm failures.36 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables monitoring of distributed autonomous agent nodes through MCP tools, dynamically computing jitter-aware failover deadlines and isolating zombie or stalled workers. It also coordinates state checkpoint hydration and failover rerouting to maintain fleet liveness.7MIT
- AlicenseAqualityAmaintenanceRuntime governance for AI-agent fleets that continuously monitors agent health, confidence, and behavior through check-ins, and returns verdicts to enable self-correction before failures occur.135Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.