OutageDeck
warningsoutagedeck.com
Live status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them?
https://outagedeck.com/api/mcpWebsiteOAuthMCP 2025-06-18v1.1.0last checked 24 Aug 2026spoke MCP on 3 of 3 checks (30 days)initialize in 183 msHow to authenticate
Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://outagedeck.com |
| Dynamic client registration | ✓Advertised (RFC 7591) |
| Client ID Metadata Document | ✕Not advertised |
| PKCE | ✓S256 |
| Grant types | authorization_code |
| Scopes | mcp |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Handshake succeeds; 14 tools listable |
| Credentials demanded in prose | ✕list_custom_providers, add_custom_provider, update_custom_provider, remove_custom_provider, watch_provider These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error. |
| Documentation | https://outagedeck.com/developers/mcp |
What the probe found
5 of the 14 tools listed anonymously say in their own descriptions that they need an account or a key (list_custom_providers, add_custom_provider, update_custom_provider, remove_custom_provider, watch_provider), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.
The server exposes a public surface before authorization: get_provider_status, check_my_stack, list_active_incidents, get_incident_details, get_uptime, get_outage_report, search_providers, list_custom_providers, add_custom_provider, update_custom_provider, remove_custom_provider, watch_provider, search, fetch.
Tools
Contract history
Get alerted when this contract changes
Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/outagedeck)Own this server?
Sign in to claim this listing by proving control of the endpoint.