OutageDeck MCP MCP server

A remote MCP server operated by OutageDeck that provides AI agents with live status, incident details, and uptime history for 180+ cloud and SaaS vendors. It reads directly from official vendor status feeds to determine if services are operational, degraded, or down, allowing agents to verify infrastructure health before debugging code.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by OutageDeck Providers Inc.

MCP endpoint (Streamable HTTP)

https://outagedeck.com/api/mcp

Vendor documentation

What you can do with it

Check if a specific vendor like AWS or GitHub is currently down
Get a verdict on whether any of 12 tracked providers have problems
Read detailed incident timelines from official sources
Retrieve independent uptime history for a provider

Tools advertised by the last live check:

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

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http outagedeck-mcp https://outagedeck.com/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add outagedeck-mcp --url https://outagedeck.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable outagedeck-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "outagedeck-mcp": {
      "type": "streamableHttp",
      "url": "https://outagedeck.com/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start outagedeck-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http outagedeck-mcp https://outagedeck.com/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

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

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

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

See all 148

Do you run OutageDeck MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing