Instatus MCP Server
Related Servers
Alternatives to Instatus MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to read monitors and incidents and to create, update, and resolve incidents on Kener v4 status pages, with read-only tools marked safe and write operations available when permitted.6MIT
- AlicenseBqualityDmaintenanceEnables unified management of maintenance windows and incidents across Atlassian Statuspage and Uptime Kuma. It allows AI assistants to schedule maintenance, update service statuses, and list monitors through a single MCP-compatible interface.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to check real-time status, uptime, and incidents for 200+ popular APIs (Stripe, OpenAI, AWS, GitHub, Twilio, etc.) through read-only, no-authentication tools.MIT
- AlicenseAqualityBmaintenanceEnables agents to inspect app status, uptime, response times, incidents, and certificate/domain expiry; set up and manage monitors and status pages; and draft incident updates through authenticated MCP tools.1133Functional Source , Version 1.1, MIT Future

Uptimy MCP serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to inspect uptime monitoring, incidents, status pages, alerts, dependencies, and reports. It also supports related changes such as opening incidents, posting updates, scheduling maintenance, adding monitors, and configuring alerts and reports.Apache 2.0
GetMonitor MCP Serverofficial
AlicenseCqualityCmaintenanceConnects AI assistants to GetMonitor status pages, monitors, incidents, and maintenance schedules via read-only tools.10015 npmApache 2.0
TDQS
Scored across 14 tools
Most tools have clearly distinct purposes: user/page/component/incident/maintenance operations are separated by resource and action. The main mild ambiguity is between post_incident_update and resolve_incident, since both can update incident wording/status, but resolve_incident's one-step RESOLVED + component-reset behavior makes it distinguishable.
All tool names are snake_case and consistently lead with a verb: get_, list_, set_, create_, post_, resolve_, delete_, schedule_. The pattern is predictable across every tool, with no mixing of conventions.
14 tools is well-scoped for a status-page operations server. The set covers user context, page viewing, component status, incident lifecycle, and maintenance without obvious bloat.
Incident lifecycle coverage is strong: list/get/create/update/resolve/delete. Component and maintenance surfaces are thinner (no create/update/delete component, no update/cancel maintenance), but the core public status-page workflows are covered and these gaps are likely administrative or out of scope.