Developer · Remote MCP server
Outage.Me
Live cloud/SaaS outages, provider reliability and exploited CVEs from official status pages and CISA.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.marcioyoshida/outage-me- Version
- 1.3.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-27
- Updated
- 2026-09-27
- Publisher
- marcioyoshida (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/marcioyoshida) · how
- Website
- outage.me
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://outage.me/mcp | None |
| Streamable HTTP | https://outage.me/mcp/pro | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://outage.me/mcp(HTTP)- Reachable
- Yes (HTTP 200)
- Handshake
- tarantula-outage-me 1.3.0 · protocol 2025-06-18
- Tools discovered
- 6:
list_active_incidents,provider_reliability,exploited_vulnerabilities,deploy_check,answer,report_observation - Checked on
- 2026-10-05
- Endpoint
https://outage.me/mcp/pro(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Outage.Me
Outage.Me is a remote MCP server: there is nothing to install. Its endpoints are https://outage.me/mcp and https://outage.me/mcp/pro, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from marcioyoshida (GitHub)
| Server | Runs |
|---|---|
| Onça - Brazil financial competitive & regulatory intelligenceBrazilian financial institutions: entity registry, sourced regulatory signals, cited Q&A. | Remote · HTTPLive check: sign-in required |
More developer servers
| Server | Runs |
|---|---|
| Ot Security MCPOT security standards: IEC 62443, NIST 800-82/53, MITRE ATT&CK for ICS. | Local · stdio |
| OTC Pricing MCPMCP server for the Open Telekom Cloud Price Calculator API (eu-de, eu-nl, eu-ch2). | Local · stdio |
| Otel Collector Drift LintFinds the removed components and renamed attributes in an OpenTelemetry Collector config before the. | Local · stdio |
| OtterkitTunnels and webhooks for AI agents: capture, await, verify, replay, and send signed test events. | Local · stdio |
| OutageDeckLive status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them? | Remote · HTTPLive check: ✓ handshake |
| OuterSpace ApizrPython capability compiler: local read-only analysis and explicit MCP/REST exposure planning. | Local · stdio |
| Outflow MCPMCP server exposing an Outflow workspace's live architecture graph as context for AI coding agents. | Local · stdio |
| OutSlideCreative workspace. Public MCP: outline previews for Codex and Claude Code; media in the web app. | Remote · HTTPLive check: ✓ handshake |