# Outages Live (remote · outages.live)

Is it down? Live status and outages of 259 cloud, AI and developer providers, from status pages.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `outages.live`: 64/100 (this document), [markdown](https://verifymcp.io/servers/boristane-outages-live/outages.md), [page](https://verifymcp.io/servers/boristane-outages-live/outages)

## Channel facts

- Endpoint: `https://outages.live/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 918 tokens (~183/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Outages Live MCP server?

Outages Live is a hosted endpoint at https://outages.live/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http boristane-outages-live 'https://outages.live/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "boristane-outages-live": {
      "url": "https://outages.live/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "boristane-outages-live": {
      "type": "http",
      "url": "https://outages.live/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.boristane-outages-live]
url = "https://outages.live/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "boristane-outages-live": {
      "type": "remote",
      "url": "https://outages.live/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add boristane-outages-live --url 'https://outages.live/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  boristane-outages-live:
    url: "https://outages.live/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "boristane-outages-live": {
      "Transport": "http",
      "Url": "https://outages.live/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add boristane-outages-live -t streamable-http -u 'https://outages.live/mcp'
```

### Other

```json
{
  "mcpServers": {
    "boristane-outages-live": {
      "type": "http",
      "url": "https://outages.live/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-11-04 (score 64, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 63)

First indexed and scored.

## MCP tools (5)

### `get_provider` (~202 tokens)

Get a provider's status

Get one provider (for example GitHub, AWS, Vercel, OpenAI): a one-line verdict on whether it reports a problem now, its active incidents, what people reported about it on outages.live in the last 24 hours (reviewed reports only, with a spike flag when many arrive in an hour), maintenance in progress, its last 10 incidents, and 90 days of daily history. Give region or component to keep only active incidents that name it, for example us-east-1 or Actions. Call it when a request to the provider fails, before you change code. An unknown name returns every tracked id.

Input parameters:

- `component` (string): Optional component or product to match, for example Actions, S3, Chat Completions
- `provider` (string, required): Provider id or name, for example github, aws, Google Cloud, openai
- `region` (string): Optional region to match, for example us-east-1

### `list_feed` (~143 tokens)

List provider incidents

List incidents across providers, the most recently updated first. By default only incidents that are open now. Narrow it with providers, category, and a minimum impact; set state to recent to add incidents resolved in the last days.

Input parameters:

- `category` (string)
- `days` (integer): Window for state recent
- `impact` (string): Minimum impact: partial_outage keeps partial and major outages
- `include_maintenance` (boolean)
- `limit` (integer)
- `providers` (array): Provider ids or names, for example github, vercel
- `state` (string): active: open now. recent: everything updated in the last days.

### `send_feedback` (~121 tokens)

Send feedback to outages.live

Send feedback to the outages.live team: a provider to add, data that looks wrong (a status that does not match the provider's own page, a missing or stale incident), or an idea. The team reads every message. Send only what the user agreed to share.

Input parameters:

- `kind` (string, required): missing_provider, wrong_data, idea, or other
- `message` (string, required): What to add, what looks wrong and where, or the idea
- `provider` (string): Optional provider the feedback is about, tracked or not, for example stripe

### `report_affected` (~118 tokens)

Say an outage affects your user

Tell outages.live that an outage affects your user, as the "I'm affected" button on the outage page does. Call it only when your user says that the outage affects them, never on your own. Give the outage id that get_provider or list_feed returns. The count shows on the outage page at once, and each user counts once for each outage, so a second call changes nothing. Returns the new affected count.

Input parameters:

- `outage_id` (string, required): The outage id from get_provider or list_feed, for example github-abc123

### `report_outage` (~166 tokens)

Report a provider outage

Report that a provider does not work for your user, as "Report an outage" on outages.live does, also when its status page shows no problem. Call it only when your user asks you to report it, never on your own. The outages.live team reviews each report, and only approved reports show on outages.live, in the API, and in get_provider. One report for each provider each hour.

Input parameters:

- `kind` (string, required): What does not work: api (an API or service), website (the website or dashboard), sign_in, or other
- `note` (string): Optional short note from your user about what they see, for example Pushes time out
- `provider` (string, required): Provider id or name, for example github, aws, openai

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/boristane-outages-live/outages#diagnostics

## Score history

- 2026-11-05: 64
- 2026-11-04: 64
- 2026-11-03: 63

## Common questions

### What is the Outages Live MCP server?

Outages Live is an MCP server listed in the public MCP registry as io.github.boristane/outages-live. Is it down? Live status and outages of 259 cloud, AI and developer providers, from status pages. This page covers its hosted endpoint (https://outages.live/mcp).

### Is the Outages Live MCP server safe to use?

Outages Live scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Outages Live MCP server expose?

Outages Live exposes 5 tools: get_provider, list_feed, send_feedback, report_affected, report_outage. Their descriptions and schemas cost roughly 750 tokens of context every time the server is loaded.

### Does the Outages Live MCP server require authentication?

No. We connected to Outages Live without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Outages Live MCP server still maintained?

Outages Live is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://outages.live/mcp
- Website: https://outages.live/
- Changelog RSS feed: https://verifymcp.io/servers/boristane-outages-live/outages.xml
- Changelog JSON feed: https://verifymcp.io/servers/boristane-outages-live/outages.json
- HTML version of this page: https://verifymcp.io/servers/boristane-outages-live/outages