uptybots-mcp-server
OfficialRelated Servers
Alternatives to uptybots-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceOfficial Hyperping MCP server for uptime, API, cron and server monitoring. 26 tools covering monitors, outages and timelines, uptime, response time, MTTR and MTTA, on-call schedules and escalation policies, over a remote Streamable HTTP endpoint with Bearer token auth and no install.1MIT
- AlicenseNot gradedqualityCmaintenanceUptime monitoring your AI agent can set up: create HTTP, SSL, ping, TCP and DNS monitors checked from multiple regions, run checks on demand, read and acknowledge incidents, manage cron heartbeats, maintenance windows and status page updates.49229 npmMIT
- FlicenseNot gradedqualityCmaintenanceUptime, SSL, DNS and domain monitoring you can talk to: check, create and manage monitors for all your client sites from Claude, ChatGPT, or any MCP client.1-
- AlicenseAqualityBmaintenanceWebsite monitoring for AI assistants. Visual Sentinel catches pages that look broken even when the site is up. DNS, SSL, speed and website checks need no account; monitors, incidents and alerts need an API key (Business and Agency plans).16236 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude to check current uptime status, inspect monitors and incidents, trigger fresh checks, and retrieve status summaries from a self-hosted monitoring service.4 npm2MIT
- AlicenseAqualityAmaintenanceUptime monitoring from your AI agent: create and diagnose checks (40 types: HTTP, TCP, DNS, SSL, ICMP, databases, message queues and more), read results and incidents, and manage status pages and maintenance windows. Built into the self-hostable SolidPing server, served over streamable HTTP at /api/v1/mcp.2322AGPL 3.0
TDQS
Scored across 15 tools
Each tool targets a distinct resource and action: listing, reading, creating various monitor types (HTTP, API, ping, port, SSL, domain), pausing/resuming, deleting, and querying incidents/stats/notifications. No two tools overlap in purpose; the create_* variants are clearly differentiated by check type.
All tools follow a consistent verb_noun snake_case pattern: list_, get_, create_<type>_monitor, pause_, resume_, delete_, get_incidents, get_stats_hourly/daily, get_notifications. The pattern is predictable and aids agent selection.
15 tools is within the ideal 3-15 range and matches the domain's needs: comprehensive monitoring coverage without redundancy. Each tool serves a distinct purpose in the uptime monitoring workflow.
The set covers the full monitoring lifecycle: create (six types), read, pause/resume, delete, incidents, stats, and notifications. The only minor gap is the lack of an explicit update/edit tool for existing monitors, but most configuration changes would be done via create/delete, and the current set handles core workflows effectively.