Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "outagedeck-status": {
      "type": "http",
      "url": "https://outagedeck.com/api/mcp"
    }
  }
}

claude mcp add --transport http outagedeck-status https://outagedeck.com/api/mcp

[mcp_servers.outagedeck-status]
url = "https://outagedeck.com/api/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "outagedeck-status": {
      "type": "remote",
      "url": "https://outagedeck.com/api/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "outagedeck-status": {
      "type": "http",
      "url": "https://outagedeck.com/api/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=outagedeck-status&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vb3V0YWdlZGVjay5jb20vYXBpL21jcCJ9"
}

{
  "servers": {
    "outagedeck-status": {
      "type": "http",
      "url": "https://outagedeck.com/api/mcp"
    }
  }
}

{
  "mcpServers": {
    "outagedeck-status": {
      "httpUrl": "https://outagedeck.com/api/mcp"
    }
  }
}

extensions:
  "outagedeck-status":
    enabled: true
    name: "outagedeck-status"
    type: streamable_http
    uri: "https://outagedeck.com/api/mcp"
    timeout: 300

Quality 80 / 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.annotations14 of 14 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
pass
tools.token_costabout 2,246 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability50 · weight 15

pass
stability.changes3 tool changes in 30 days
fail
stability.rug_pull1 tools kept their name but changed most of their description in 30 days; review before trusting them

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

14 tools, about 2,246 tokens to load them all · tool set e839603c6f9e · tools last changed 2026-10-12 · checked 2026-10-19 10:52 UTC

Tool changes

2026-10-12watch_providerchangeddescriptionmeaning changed
before
Starts sending the caller outage alerts for one provider, either from the tracked catalog or from their own custom providers. Requires an API key. Alerts are emailed to the account address; the other channels (Slack, Teams, Discord, webhook) are set up on the account page, so no webhook URL ever has to be shared in a conversation.
after · 42% of words in common
Starts sending the caller outage alerts for one provider, either from the tracked catalog or from their own custom providers. Requires an API key. A new watch is added to the owner's email alert. An existing alert counts only when delivery is allowed; otherwise a new owner-email watch is added or the request is refused with an explanation. A successful result always means delivery is allowed and reports the alert's channel. Other channels are set up on the account page; their destination URLs are never returned.
2026-10-12get_uptimechangeddescription
before
Independent uptime record for one provider over a trailing window (7-90 days, default 30), computed from OutageDeck's own observations of the vendor's official feed: share of time free of major outages, strict uptime with partial outages counted as downtime, and total impaired durations.
after · 80% of words in common
Independent uptime record for one provider over a trailing window (7-90 days, default 30), computed from OutageDeck's readings of the official source that publishes the provider's status: share of time free of major outages, strict uptime with partial outages counted as downtime, and total impaired durations.
2026-10-12get_provider_statuschangeddescription
before
Live status for one tracked provider: overall state, non-operational services, and open incidents, read from the vendor's official status feed. Accepts a slug, provider name, or product name (e.g., "claude" resolves to Anthropic). Use this first for any "is X down?" question.
after · 58% of words in common
Live status for one tracked provider: overall state, non-operational services, and open incidents, read from the vendor's official status feed. Accepts a slug, provider name, or product name (e.g., "claude" resolves to Anthropic). Use this first for any "is X down?" question. When regions are present, reportedCodes lists published codes; notOperational lists impaired rows. If those rows are truncated, notOperationalCodes lists every impaired code. For an inventory feed, a reported code absent from the complete impaired list is operational; an unreported code has no published status. Withdrawn readings omit these lists.

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 80 / 100

no-repository

provenance55

liveness100

freshness85

hygiene80

+dns-namespace +website +reachable +uptime-100% ~updated-78d-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

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://outagedeck.com/api/mcp` streamable-http	none	yes	100%	311 ms	2025-06-18	2026-10-19

Tools (14)

`add_custom_provider`	Registers a vendor OutageDeck does not track by pointing at its Statuspage or Instatus status page, so it joins the caller's account with live status, incident history, and alerting. Requires an API key and a plan that includes custom providers. The feed is read live before anything is saved, and it must be reachable from the public internet. Feeds behind authentication are set up on the account page instead, so credentials never travel through a conversation.
`check_my_stack`read-only	One verdict across up to 12 providers: whether any vendor in the list is reported as having a problem right now. Use before debugging an integration failure to answer "is it us or them?" in a single call. Returns a shareable status-board link and a prefilled alert setup link.
`fetch`read-only	Retrieve the full text of one search result by its id: a provider's current status with its services and open incidents, or an incident's complete timeline. Ids come from the search tool.
`get_incident_details`read-only	Full detail for one incident: updates from the official incident source in chronological order, the services OutageDeck matched to it, severity, and resolution state. Pass the incident slug returned by list_active_incidents or get_provider_status. Use to read what the official source has actually said about an outage.
`get_outage_report`read-only	A reliability summary across every tracked provider over a trailing window (7-90 days, default 30): incident totals, severity and category breakdowns, the providers hit hardest by major outages, and the longest-running severe incidents. Use to answer "which vendors had outages recently?" or to compare vendor reliability.
`get_provider_status`read-only	Live status for one tracked provider: overall state, non-operational services, and open incidents, read from the vendor's official status feed. Accepts a slug, provider name, or product name (e.g., "claude" resolves to Anthropic). Use this first for any "is X down?" question. When regions are present, reportedCodes lists published codes; notOperational lists impaired rows. If those rows are truncated, notOperationalCodes lists every impaired code. For an inventory feed, a reported code absent from the complete impaired list is operational; an unreported code has no published status. Withdrawn readings omit these lists.
`get_uptime`read-only	Independent uptime record for one provider over a trailing window (7-90 days, default 30), computed from OutageDeck's readings of the official source that publishes the provider's status: share of time free of major outages, strict uptime with partial outages counted as downtime, and total impaired durations.
`list_active_incidents`read-only	Every incident currently open across all tracked providers, most severe first. Optionally filter by severity (critical, major, minor, maintenance). Use to answer "what is down right now?" across the whole cloud landscape.
`list_custom_providers`read-only	Lists the custom providers on the caller's own OutageDeck account: vendors they registered themselves by pointing at a status feed we do not track in the public catalog. Requires an API key, and only ever returns that key owner's providers.
`remove_custom_provider`destructive	Deletes one of the caller's custom providers and its stored incident history, freeing a slot on their plan. Requires an API key.
`search`read-only	Search everything OutageDeck tracks: cloud and SaaS providers, and their incident history. Returns citable results with stable ids for the fetch tool. Use for open questions like "who had outages last week" or "find the GitHub Actions incident"; use get_provider_status when the question is simply whether one named vendor is down right now.
`search_providers`read-only	Find tracked providers by name, product name, or fragment ("postgres", "auth", "claude"). Returns slugs to use with the other tools plus each match's current status. Use when a provider argument did not resolve or to discover what OutageDeck tracks.
`update_custom_provider`	Renames one of the caller's custom providers, points it at a different status page, or pauses and resumes its checks. Requires an API key. A new address is read live before it is stored.
`watch_provider`	Starts sending the caller outage alerts for one provider, either from the tracked catalog or from their own custom providers. Requires an API key. A new watch is added to the owner's email alert. An existing alert counts only when delivery is allowed; otherwise a new owner-email watch is added or the request is refused with an explanation. A successful result always means delivery is allowed and reports the alert's channel. Other channels are set up on the account page; their destination URLs are never returned.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "com.outagedeck/outagedeck-status",
  "title": "OutageDeck",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://outagedeck.com/api/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.1.0",
  "websiteUrl": "https://outagedeck.com/developers/mcp",
  "description": "Live status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them?"
}