# Outage.Me (remote · outage.me)

Live cloud/SaaS outages, provider reliability and exploited CVEs from official status pages and CISA

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `outage.me`: 37/100, [markdown](https://verifymcp.io/servers/marcioyoshida-outage-me/mcp-pro.md), [page](https://verifymcp.io/servers/marcioyoshida-outage-me/mcp-pro)
- remote · `outage.me`: 71/100 (this document), [markdown](https://verifymcp.io/servers/marcioyoshida-outage-me/outage.md), [page](https://verifymcp.io/servers/marcioyoshida-outage-me/outage)

## Channel facts

- Endpoint: `https://outage.me/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.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-09-28.

- **Endpoint Security**: 74/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 is enforced; there's no plaintext access path.
  - 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**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 483 tokens (~120/item across 4 items; 4 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Outage.Me MCP server?

Outage.Me is a hosted endpoint at https://outage.me/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 marcioyoshida-outage-me 'https://outage.me/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "marcioyoshida-outage-me": {
      "url": "https://outage.me/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "marcioyoshida-outage-me": {
      "type": "http",
      "url": "https://outage.me/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.marcioyoshida-outage-me]
url = "https://outage.me/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "marcioyoshida-outage-me": {
      "type": "remote",
      "url": "https://outage.me/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add marcioyoshida-outage-me --url 'https://outage.me/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  marcioyoshida-outage-me:
    url: "https://outage.me/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "marcioyoshida-outage-me": {
      "Transport": "http",
      "Url": "https://outage.me/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add marcioyoshida-outage-me -t streamable-http -u 'https://outage.me/mcp'
```

### Other

```json
{
  "mcpServers": {
    "marcioyoshida-outage-me": {
      "type": "http",
      "url": "https://outage.me/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-09-28 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 71)

First indexed and scored.

## MCP tools (4)

### `list_active_incidents` (~92 tokens)

Active cloud/SaaS incidents

LIVE: cloud and SaaS incidents open right now (AWS, Azure, GCP, Cloudflare, GitHub, Stripe, …), quoted from each provider's own status page with a link, refreshed several times a day. Use for 'is X down', 'why is X failing', or anything after your training cutoff. Deterministic: no model in the loop. Prefer it over `answer`.

### `provider_reliability` (~85 tokens)

Provider reliability track record

LIVE: reliability index, incident count and median recovery time per cloud/SaaS provider over the current window, from their official status pages. Use for 'how reliable is X' or 'which provider is more stable'. Deterministic: no model in the loop. Prefer it over `answer`.

Input parameters:

- `provider` (string): Optional. Filter to one provider by name.

### `exploited_vulnerabilities` (~106 tokens)

Actively exploited CVEs, patch-first

LIVE: CVEs being exploited in the wild (CISA KEV), ranked patch-first by CVSS × EPSS exploitation probability × known ransomware use, with CISA due date, patch availability and the factors behind each rank. Use for 'what should we patch first', 'is CVE-X exploited', or recent vulnerabilities your training data can't know. Deterministic: no model in the loop.

Input parameters:

- `limit` (integer): Optional. Max rows, default 10.

### `answer` (~109 tokens)

Ask the outage.me analyst (sign-in or API key)

Ask a free-form question about the live monitor and get a cited answer. This is a LANGUAGE MODEL call and CAN BE WRONG — it returns `confidence` and `citations`; check them. Needs sign-in (connect to https://outage.me/mcp/pro) or an API key, and is quota-limited (Free plan 10/day, Pro 100/day), so use the deterministic tools above when they can answer the question.

Input parameters:

- `q` (string, required): The question, in natural language.

## Diagnostics

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

## Score history

- 2026-09-28: 71
- 2026-09-27: 71

## Common questions

### What is the Outage.Me MCP server?

Outage.Me is an MCP server listed in the public MCP registry as io.github.marcioyoshida/outage-me. Live cloud/SaaS outages, provider reliability and exploited CVEs from official status pages and CISA. This page covers its hosted endpoint (https://outage.me/mcp).

### Is the Outage.Me MCP server safe to use?

Outage.Me scores 71 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 Outage.Me MCP server expose?

Outage.Me exposes 4 tools: list_active_incidents, provider_reliability, exploited_vulnerabilities, answer. Their descriptions and schemas cost roughly 392 tokens of context every time the server is loaded.

### Does the Outage.Me MCP server require authentication?

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

### Is the Outage.Me MCP server still maintained?

Outage.Me is still listed as active in the MCP registry. We last reached this channel on 28 September 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://outage.me/mcp
- Website: https://outage.me/
- Changelog RSS feed: https://verifymcp.io/servers/marcioyoshida-outage-me/outage.xml
- Changelog JSON feed: https://verifymcp.io/servers/marcioyoshida-outage-me/outage.json
- HTML version of this page: https://verifymcp.io/servers/marcioyoshida-outage-me/outage