com.outagedeck/outagedeck-status

Tools

• add_custom_provider

  Registers a vendor OutageDeck does not track by pointing at its Statuspage or Instatus status page, so it joins the caller's account with live status, incident history, and alerting. Requires an API key and a plan that includes custom providers. The feed is read live before anything is saved, and it must be reachable from the public internet. Feeds behind authentication are set up on the account page instead, so credentials never travel through a conversation.

  shallow
• check_my_stack

  One verdict across up to 12 providers: whether any vendor in the list is reporting a problem right now. Use before debugging an integration failure to answer "is it us or them?" in a single call. Returns a shareable status-board link and a prefilled alert setup link.

  shallow
• fetch

  Retrieve the full text of one search result by its id: a provider's current status with its services and open incidents, or an incident's complete timeline. Ids come from the search tool.

  shallow
• get_incident_details

  Full detail for one incident: the provider's own update timeline in chronological order, affected services, severity, and resolution state. Pass the incident slug returned by list_active_incidents or get_provider_status. Use to read what the vendor has actually said about an outage.

  shallow
• get_outage_report

  A reliability summary across every tracked provider over a trailing window (7-90 days, default 30): incident totals, severity and category breakdowns, the providers hit hardest by major outages, and the longest-running severe incidents. Use to answer "which vendors had outages recently?" or to compare vendor reliability.

  shallow
• get_provider_status

  Live status for one tracked provider: overall state, non-operational services, and open incidents, read from the vendor's official status feed. Accepts a slug, provider name, or product name (e.g., "claude" resolves to Anthropic). Use this first for any "is X down?" question.

  shallow
• get_uptime

  Independent uptime record for one provider over a trailing window (7-90 days, default 30), computed from OutageDeck's own observations of the vendor's official feed: share of time free of major outages, strict uptime with partial outages counted as downtime, and total impaired durations.

  shallow
• list_active_incidents

  Every incident currently open across all tracked providers, most severe first. Optionally filter by severity (critical, major, minor, maintenance). Use to answer "what is down right now?" across the whole cloud landscape.

  shallow
• list_custom_providers

  Lists the custom providers on the caller's own OutageDeck account: vendors they registered themselves by pointing at a status feed we do not track in the public catalog. Requires an API key, and only ever returns that key owner's providers.

  shallow
• remove_custom_provider

  Deletes one of the caller's custom providers and its stored incident history, freeing a slot on their plan. Requires an API key.

  shallow
• search

  Search everything OutageDeck tracks: cloud and SaaS providers, and their incident history. Returns citable results with stable ids for the fetch tool. Use for open questions like "who had outages last week" or "find the GitHub Actions incident"; use get_provider_status when the question is simply whether one named vendor is down right now.

  shallow
• search_providers

  Find tracked providers by name, product name, or fragment ("postgres", "auth", "claude"). Returns slugs to use with the other tools plus each match's current status. Use when a provider argument did not resolve or to discover what OutageDeck tracks.

  shallow
• update_custom_provider

  Renames one of the caller's custom providers, points it at a different status page, or pauses and resumes its checks. Requires an API key. A new address is read live before it is stored.

  shallow
• watch_provider

  Starts sending the caller outage alerts for one provider, either from the tracked catalog or from their own custom providers. Requires an API key. Alerts are emailed to the account address; the other channels (Slack, Teams, Discord, webhook) are set up on the account page, so no webhook URL ever has to be shared in a conversation.

  shallow

Embed this server’s score

Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.

[![Vouch score](https://vouch.tools/api/servers/c51a84c2-df44-4c68-9659-ad050372741a/badge.svg)](https://vouch.tools/servers/c51a84c2-df44-4c68-9659-ad050372741a)