OutageDeck

com.outagedeckPublished by outagedeck.comOfficial publisherv1.1.0Updated Oct 25, 2026

Live status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them?

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

OutageDeck gives an assistant live status, incidents and uptime for 172 cloud and SaaS vendors, read from their official status feeds.

What you can do
Check whether one provider is down, with its overall state, non-operational services and open incidents, and resolve providers by slug, name or product name (for example claude to Anthropic). Get one verdict across up to 12 providers to tell whether a problem is yours or a vendor's. List every open incident across all tracked providers, filtered by severity, and read one incident's full timeline and resolution state. Look up independent uptime over 7 to 90 days and a reliability summary of recent outages across all providers. Search everything tracked and fetch the full text of a result, or manage custom providers and outage alerts on your own account.
When to use it
Use it when debugging an integration failure and you need to know whether a vendor is having an outage, or when answering questions about current or recent cloud and SaaS incidents and vendor reliability.
Requirements
A remote streamable HTTP endpoint; no local runtime or package. The public status, incident, uptime, search and fetch tools need no credentials. The custom provider tools and watch_provider require an OutageDeck API key, and add_custom_provider also needs a plan that includes custom providers.
Before you install
Tools that need an API key act on your own OutageDeck account: add, update and remove custom providers, and start outage alerts. Removing a custom provider deletes its stored incident history. watch_provider adds an email alert to the key owner's address. Status data comes from third-party vendor feeds and may lag or be incomplete.

Installation

In SourceWeft

  1. Open OutageDeck in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.outagedeck%2Foutagedeck-status/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "outagedeck": {
      "type": "http",
      "url": "https://outagedeck.com/api/mcp"
    }
  }
}

Tools

14

get_provider_status

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. When regions are present, reportedCodes lists published codes; notOperational lists impaired rows. If those rows are truncated, notOperationalCodes lists every impaired code. For an inventory feed, a reported code absent from the complete impaired list is operational; an unreported code has no published status. Withdrawn readings omit these lists.

Parametersproviderrequired

check_my_stack

Check a whole stack

One verdict across up to 12 providers: whether any vendor in the list is reported as having 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.

Parametersprovidersrequired

list_active_incidents

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.

Parametersseverity

get_incident_details

Get incident details

Full detail for one incident: updates from the official incident source in chronological order, the services OutageDeck matched to it, severity, and resolution state. Pass the incident slug returned by list_active_incidents or get_provider_status. Use to read what the official source has actually said about an outage.

Parametersincidentrequired

get_uptime

Get uptime history

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

Parametersdaysproviderrequired

get_outage_report

Get the cross-vendor 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.

Parametersdays

search_providers

Search tracked 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.

Parametersqueryrequired

list_custom_providers

List my 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.

Takes no parameters.

add_custom_provider

Add a 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.

Parametersurlrequiredname

update_custom_provider

Update a custom provider

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

Parametersurlnamestateproviderrequired

remove_custom_provider

Remove a 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.

Parametersproviderrequired

watch_provider

Watch a 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. A new watch is added to the owner's email alert. An existing alert counts only when delivery is allowed; otherwise a new owner-email watch is added or the request is refused with an explanation. A successful result always means delivery is allowed and reports the alert's channel. Other channels are set up on the account page; their destination URLs are never returned.

Parametersproviderrequired

fetch

Fetch an OutageDeck document

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.

Parametersidrequired

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.