outage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whats_downA | Check what services are having outages or incidents right now. Returns active incidents first, then recently resolved ones. |
| check_serviceA | Check the outage status and recent incident history of a specific service (e.g. cloudflare, github, aws, openai, stripe). |
| get_incidentA | Get full detail for one incident by its slug or numeric id, including the AI root-cause analysis when available. |
| outage_stats | Outage leaderboard and statistics: which services broke most this week, total incidents tracked, busiest day. |
| list_servicesA | List all services monitored for outages, with lifetime incident counts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct query: check_service for a specific service's history, get_incident for incident details, list_services for the service catalog, and whats_down for current active outages. There is no confusion.
Three tools follow verb_noun pattern (check_service, get_incident, list_services), but 'whats_down' breaks the pattern with informal phrasing and no underscore.
4 tools is well-scoped for an outage monitoring server, covering the essential operations without unnecessary bloat.
The server covers the main use cases: listing services, checking specific history, current outages, and incident details. However, it lacks a global incident list or ability to search incidents across services, which is a minor gap.