# OutageDeck (remote · outagedeck.com)

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

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `outagedeck.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-outagedeck-outagedeck-status/api-mcp.md), [page](https://verifymcp.io/servers/com-outagedeck-outagedeck-status/api-mcp)

## Channel facts

- Endpoint: `https://outagedeck.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (remove_custom_provider).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 88/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1386 tokens (~99/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (14% of tools); any adoption earns full credit.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.com-outagedeck-outagedeck-status]
url = "https://outagedeck.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-outagedeck-outagedeck-status": {
      "type": "remote",
      "url": "https://outagedeck.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-outagedeck-outagedeck-status --url https://outagedeck.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-outagedeck-outagedeck-status:
    url: "https://outagedeck.com/api/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-02 (score 66)

First indexed and scored.

## MCP tools (14)

### `get_provider_status` (~103 tokens)

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.

Input parameters:

- `provider` (string, required): Provider slug, name, or product name, e.g., "aws", "GitHub", "chatgpt".

### `check_my_stack` (~83 tokens)

Check a whole 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.

Input parameters:

- `providers` (array, required): Provider slugs, names, or product names, one per vendor the stack depends on.

### `list_active_incidents` (~65 tokens)

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.

Input parameters:

- `severity` (string): Only incidents of this severity.

### `get_incident_details` (~84 tokens)

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.

Input parameters:

- `incident` (string, required): Incident slug, e.g., from an earlier list_active_incidents result.

### `get_uptime` (~97 tokens)

Get uptime history

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.

Input parameters:

- `days` (integer): Trailing window in days (default 30).
- `provider` (string, required): Provider slug, name, or product name.

### `get_outage_report` (~87 tokens)

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.

Input parameters:

- `days` (integer): Trailing window in days (default 30).

### `search_providers` (~78 tokens)

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.

Input parameters:

- `query` (string, required): Free-text search over provider names and aliases.

### `list_custom_providers` (~57 tokens)

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.

### `add_custom_provider` (~143 tokens)

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.

Input parameters:

- `name` (string): Optional display name. Defaults to the name the status page publishes.
- `url` (string, required): The vendor's status page address, for example https://status.yourvendor.com.

### `update_custom_provider` (~100 tokens)

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

Input parameters:

- `name` (string): New display name.
- `provider` (string, required): The custom provider's name or id.
- `state` (string): Resume or pause its 10-minute checks.
- `url` (string): New status page address.

### `remove_custom_provider` (~49 tokens)

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.

Input parameters:

- `provider` (string, required): The custom provider's name or id.

### `watch_provider` (~104 tokens)

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

Input parameters:

- `provider` (string, required): A tracked provider (slug, name, or product name) or one of the caller's own custom providers.

### `search` (~115 tokens)

Search OutageDeck

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.

Input parameters:

- `query` (string, required): What to look for: a vendor name, a product, or words from an incident title, e.g., "cloudflare", "elevated error rates".

Output parameters:

- `results` (array)

### `fetch` (~83 tokens)

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.

Input parameters:

- `id` (string, required): A document id returned by search, e.g., "provider:aws" or "incident:github-actions-delays-2026-07-31".

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-outagedeck-outagedeck-status/api-mcp#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 66

## Links

- Remote endpoint: https://outagedeck.com/api/mcp
- Website: https://outagedeck.com/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-outagedeck-outagedeck-status/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-outagedeck-outagedeck-status/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-outagedeck-outagedeck-status/api-mcp