protogrid

Search / io.github.boristane/outages-live

Outages Live

R0· no sign-in

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

v1.0.0 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality88good
Trust79of 100
Uptime, 30 days98%
Latency p50377 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "outages-live": {
      "type": "http",
      "url": "https://outages.live/mcp"
    }
  }
}
claude mcp add --transport http outages-live https://outages.live/mcp
[mcp_servers.outages-live]
url = "https://outages.live/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "outages-live": {
      "type": "remote",
      "url": "https://outages.live/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "outages-live": {
      "type": "http",
      "url": "https://outages.live/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=outages-live&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vb3V0YWdlcy5saXZlL21jcCJ9"
}
{
  "servers": {
    "outages-live": {
      "type": "http",
      "url": "https://outages.live/mcp"
    }
  }
}
{
  "mcpServers": {
    "outages-live": {
      "httpUrl": "https://outages.live/mcp"
    }
  }
}
extensions:
  "outages-live":
    enabled: true
    name: "outages-live"
    type: streamable_http
    uri: "https://outages.live/mcp"
    timeout: 300

Quality 88 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene100 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • pass
    tools.annotations5 of 5 tools declare readOnlyHint or destructiveHint
  • pass
    tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
  • pass
    tools.token_costabout 1,263 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
  • pass
    tools.hidden_textno hidden text in tool names, descriptions, schemas or annotations
stability83 · weight 15
  • warn
    stability.changes6 tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
  • pass
    stability.new_linksno tool change named a new site
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

5 tools, about 1,263 tokens to load them all · tool set 2085a0b3f749 · tools last changed 2026-11-06 · checked 2026-11-14 07:03 UTC

Tool changes

  • list_feedchangeddescription
    before

    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.

    after · 72% of words in common

    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. When the server URL sets filters, they apply to each argument you do not give.

  • report_outagechangedannotations
  • report_affectedchangedannotations
  • send_feedbackchangedannotations
  • list_feedchangedannotations
  • get_providerchangedannotations

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 79 / 100

no-repository
provenance45
liveness99
freshness100
hygiene80

+website +reachable +uptime-98% +updated-11d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://outages.live/mcp streamable-httpnoneyes98%377 ms2025-06-182026-11-14

Tools (5)

get_providerread-onlyGet 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.
list_feedread-onlyList 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. When the server URL sets filters, they apply to each argument you do not give.
report_affectedTell 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.
report_outageReport 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.
send_feedbackSend 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.

Schemas: list_tools.

Similar MCP servers

More from io.github.boristane

Official server.json
{
  "name": "io.github.boristane/outages-live",
  "icons": [
    {
      "src": "https://outages.live/icon-512.png",
      "sizes": [
        "512x512"
      ],
      "mimeType": "image/png"
    }
  ],
  "title": "Outages Live",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://outages.live/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "websiteUrl": "https://outages.live",
  "description": "Is it down? Live status and outages of 259 cloud, AI and developer providers, from status pages."
}