Allows for the management of Statuspage incidents and scheduled maintenance, including creating maintenance windows, updating incident statuses, and listing components.
Enables 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.
9
MIT
Why this server?
Supports status pages hosted on Atlassian Statuspage, enabling incident lookup and discovery of JSON/RSS/Atom feed URLs for vendors using that platform.
Enables querying the current state, incident history, resolution times, and feed URLs for over 1,100 SaaS/cloud vendor status pages.
7
MIT
Why this server?
Exposes an API-compatible replica of the Statuspage surface as part of the simulated olympus-labs data set, so agents can exercise Statuspage-shaped requests read-only without a test account.
Enables AI agents to read realistic, coherent data—repos, pull requests, issues, commits, users—through API-compatible, read-only replicas of 21 developer platforms including GitHub, Jira, Linear, Slack, Sentry and Salesforce, all preloaded with one simulated company so integrations can be built and tested with no accounts, credentials, rate-limit worry, or cleanup.
10
239 npm
MIT
Why this server?
Allows querying the Atlassian Statuspage v2 API to retrieve current status, component status, incidents, and maintenance for any service using a Statuspage host.
MCP server that answers service status and uptime questions by reading Atlassian Statuspage feeds from hundreds of vendors, with keyless access and tools for checking status, incidents, and vendor listings.
199 npm
MIT
Why this server?
Allows management of incidents, components, and subscribers on a Statuspage instance, including creating, updating, and resolving incidents, managing component statuses, and handling subscriber subscriptions.
Enables AI agents to check the live operational status of hundreds of cloud, SaaS and AI providers, returning current state, affected components and active incidents for a named stack so agents can tell a vendor outage apart from their own broken code. It answers from a continuously polled local database, so agents can query stacks, list degraded providers, and review incident history without calling vendor status pages.
