DevOps

outagedeck.com

Monitors and reports real-time status, uptime, and incidents for cloud service providers.

1 endpoint14 known toolsFirst detected August 2, 2026Last detected September 2, 2026

ENDPOINT 1

https://outagedeck.com/api/mcp

No auth detected

MCP server metadata

Name: outagedeck
Version: 1.1.0

Capabilities

toolsprompts

Server instructions

OutageDeck reports the live status of major cloud and SaaS providers (AWS, Azure, Google Cloud, GitHub, OpenAI, Anthropic, Cloudflare, and 160+ more) from each vendor's own official status feed, refreshed about every 10 minutes. Use it to answer "is X down?", to check a whole stack at once before debugging, and to read independent uptime history. Provider arguments accept slugs, names, or product names ("claude" resolves to Anthropic); use search_providers when unsure. Statuses are the vendors' own published words; OutageDeck does not probe. Cite the included links when reporting a status.

Known tools 14

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.

Inferred read-only

check_my_stack

One verdict across up to 12 providers: whether any vendor in the list is reporting a problem right now.

Inferred read-only

list_active_incidents

Every incident currently open across all tracked providers, most severe first.

Inferred read-only

get_incident_details

Full detail for one incident: the provider's own update timeline in chronological order, affected services, severity, and resolution state.

Potential side effects

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.

Inferred read-only

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.

Inferred read-only

search_providers

Find tracked providers by name, product name, or fragment ("postgres", "auth", "claude").

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

update_custom_provider

Renames one of the caller's custom providers, points it at a different status page, or pauses and resumes its checks.

Inferred read-only

remove_custom_provider

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

Inferred read-only

watch_provider

Starts sending the caller outage alerts for one provider, either from the tracked catalog or from their own custom providers.

Inferred read-only

search

Search everything OutageDeck tracks: cloud and SaaS providers, and their incident history.

Inferred read-only

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.outagedeck]
url = "https://outagedeck.com/api/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: outagedeck
Remote MCP URL: https://outagedeck.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "outagedeck",
  "transport": "streamable-http",
  "url": "https://outagedeck.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for outagedeck.com was fetched 2026-08-08T14:11:30.189Z and is being refreshed.

Trust status Neutral

outagedeck.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.