← outagedeck.com

INDIVIDUAL MCP TOOL

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.

outagedeck.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://outagedeck.com/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for list_custom_providers and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

outagedeck.com

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.

Related tools

  • 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.
  • check_my_stack — One verdict across up to 12 providers: whether any vendor in the list is reporting a problem right now.
  • list_active_incidents — Every incident currently open across all tracked providers, most severe first.
  • get_incident_details — Full detail for one incident: the provider's own update timeline in chronological order, affected services, severity, and resolution state.
  • 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.
  • 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.
  • search_providers — Find tracked providers by name, product name, or fragment ("postgres", "auth", "claude").
  • 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.