Skip to content

Outages Live MCP server

io.github.boristane/outages-liveboristanestreamable-httpv1.0.0Scanned

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

5 tools: 1 do something that can't be undone, 2 change things and 2 only read.

Tools: 0 delete, 1 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Outages Live MCP server can do

The Outages Live MCP server is published by the GitHub account boristane. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_feedback) and create or change data (2 tools: report_affected and report_outage), but cannot delete data. 2 tools only read.

2 tools bring in text other people can write (report_affected and report_outage); 1 tool can send data out of your system (send_feedback).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Can't be undone 1Claude Code: ask
  • 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.Can send data outNo findings

    Why it is in this group

    • The name "send_feedback" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_feedback" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Send feedback to outages.live
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 2Claude Code: ask
  • report_affectedTell outages.live that an outage affects your user, as the "I'm affected" button on the outage page does.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Say an outage affects your user
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Report a provider outage
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • get_providerGet 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.l…No findings

    Why it is in this group

    • The name "get_provider" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a provider's status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_feedList incidents across providers, the most recently updated first.No findings

    Why it is in this group

    • The name "list_feed" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List provider incidents
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 4, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://outages.live/mcp: tools/list returned 5 tools to an anonymous client, including send_feedback (irreversible), report_affected (write), report_outage (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools5 changed.~5 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http outages-live https://outages.live/mcp
claude mcp add --transport http outages-live https://outages.live/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__outages-live__get_provider",
      "mcp__outages-live__list_feed"
    ],
    "ask": [
      "mcp__outages-live__send_feedback",
      "mcp__outages-live__report_affected",
      "mcp__outages-live__report_outage"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as outages-live. Review it before you use it.

Capability tags behind 3 rules
  • mcp__outages-live__send_feedback outbound
  • mcp__outages-live__report_affected untrusted-input
  • mcp__outages-live__report_outage untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.boristane/outages-live/verify?hash=e40cd419a3dd0317b63ddf9854db6f35e064a74e6d453f1e471c9969d1a3bc3c" | jq -e '.changed == false'

Pinned hash e40cd419a3dd, from Nov 17, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.boristane/outages-live/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.boristane/outages-live
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.boristane/outages-live.svg)](https://radar.anlyon.com/servers/io.github.boristane/outages-live)

Source: MCP Registry. Synced Nov 3, 2026, 18:17 UTC.

Outages Live MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Outages Live MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Outages Live MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Outages Live MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: send_feedback.

What tools does the Outages Live MCP server have?

5 tools: 1 irreversible, 2 write, 2 read. send_feedback, report_affected, report_outage, get_provider and list_feed.

Does the Outages Live MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Outages Live MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_feedback.

Has the Outages Live MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.