Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

OutageDeck

REMOTE · OUTAGEDECK.COM

Live status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them?

Available components

+1 this week 82 Trust /100

Last scanned (10 minutes ago)

Scores higher than 81% of remote servers

Reachable. Last reached 22 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security66
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1596 tokens (~114/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (14% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Nov 26 +1
    • DNSSEC: fail → pass ▲ security
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Tool “get_provider_status” rewrote its description, which is the text the model reads security
    • Stability: pass → 0.97 functional
    • Server version: 1.1.3 → 1.2.0 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Oct 26 0
    • Tool “update_custom_provider” rewrote its description, which is the text the model reads security
    • Server version: 1.1.2 → 1.1.3 functional
    • “update_custom_provider” reworded the description of “state” cosmetic
  • 13 Oct 26 0
    • Tool “get_provider_status” rewrote its description, which is the text the model reads security
    • Tool “get_uptime” rewrote its description, which is the text the model reads security
    • Tool “watch_provider” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Nov 2026 · Probed https://outagedeck.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=outagedeck.com CN=YE1,O=Let's Encrypt,C=US 18 Nov 2026 16 Feb 2027 ECDSA 256 ECDSA-SHA384 6d9ed7e94ad3a8e94d7fdb96cbeb4f6d16d
SANs: *.outagedeck.com, outagedeck.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of outagedeck.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
outagedeck.com. DS published 2371 13 Verified
outagedeck.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy base-uri 'self'; object-src 'none'; frame-ancestors 'self'; upgrade-insecure-requests; form-action 'self'; script-src 'self' 'unsafe-inline' https://cdn.paddle.com https://public.profitwell.com; script-src-attr 'none'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://outagedeck.com/api/mcp Verified 200
http (plaintext) http://outagedeck.com/api/mcp HTTPS enforced 301 https://outagedeck.com/api/mcp
MCP tools · 14 exposed · ~1,414 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_custom_provider ~143

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.

NameTypeReqDescription
namestring–Optional display name. Defaults to the name the status page publishes.
urlstringyesThe vendor's status page address, for example https://status.yourvendor.com.

No output schema declared.

No examples provided.

check_my_stack ~92

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.

NameTypeReqDescription
providersarrayyesProvider slugs, names, or product names, one per vendor the stack depends on.

No output schema declared.

No examples provided.

fetch ~83

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.

NameTypeReqDescription
idstringyesA document id returned by search, e.g., "provider:aws" or "incident:github-actions-delays-2026-07-31".
NameTypeReqDescription
idstringyes–
metadataobject––
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

get_incident_details ~91

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.

NameTypeReqDescription
incidentstringyesIncident slug, e.g., from an earlier list_active_incidents result.

No output schema declared.

No examples provided.

get_outage_report ~87

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.

NameTypeReqDescription
daysinteger–Trailing window in days (default 30).

No output schema declared.

No examples provided.

get_provider_status ~210

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. When only some services sit behind a feed OutageDeck could not re-read, services.notOperationalCount is null, confirmedNotOperationalCount counts the impaired services it could read, and unconfirmedServices names the rest.

NameTypeReqDescription
providerstringyesProvider slug, name, or product name, e.g., "aws", "GitHub", "chatgpt".

No output schema declared.

No examples provided.

get_uptime ~100

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.

NameTypeReqDescription
daysinteger–Trailing window in days (default 30).
providerstringyesProvider slug, name, or product name.

No output schema declared.

No examples provided.

list_active_incidents ~65

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.

NameTypeReqDescription
severitystring–Only incidents of this severity.

No output schema declared.

No examples provided.

list_custom_providers ~57

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

remove_custom_provider ~49

Deletes one of the caller's custom providers and its stored incident history, freeing a slot on their plan. Requires an API key.

NameTypeReqDescription
providerstringyesThe custom provider's name or id.

No output schema declared.

No examples provided.

search ~115

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.

NameTypeReqDescription
querystringyesWhat to look for: a vendor name, a product, or words from an incident title, e.g., "cloudflare", "elevated error rates".
NameTypeReqDescription
resultsarrayyes–

No examples provided.

search_providers ~78

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.

NameTypeReqDescription
querystringyesFree-text search over provider names and aliases.

No output schema declared.

No examples provided.

update_custom_provider ~111

Renames one of the caller's custom providers, points it at a different status page, or pauses and resumes OutageDeck reading it. Requires an API key. A new address is read live before it is stored.

NameTypeReqDescription
namestring–New display name.
providerstringyesThe custom provider's name or id.
statestring–Resume or pause reading it. An active feed is read about every 10 minutes.
urlstring–New status page address.

No output schema declared.

No examples provided.

watch_provider ~133

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.

NameTypeReqDescription
providerstringyesA tracked provider (slug, name, or product name) or one of the caller's own custom providers.

No output schema declared.

No examples provided.

Install

How do I install the OutageDeck MCP server?

OutageDeck is a hosted endpoint at https://outagedeck.com/api/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.

remote · outagedeck.com

# add to Claude Code
claude mcp add --transport http com-outagedeck-outagedeck-status 'https://outagedeck.com/api/mcp'
Common questions

What is the OutageDeck MCP server?

OutageDeck is an MCP server listed in the public MCP registry as com.outagedeck/outagedeck-status. Live status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them? This page covers its hosted endpoint (https://outagedeck.com/api/mcp).

Is the OutageDeck MCP server safe to use?

OutageDeck scores 82 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 OutageDeck MCP server expose?

OutageDeck exposes 14 tools: get_provider_status, check_my_stack, list_active_incidents, get_incident_details, get_uptime, and 9 more. Their descriptions and schemas cost roughly 1,414 tokens of context every time the server is loaded.

Does the OutageDeck MCP server require authentication?

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

Is the OutageDeck MCP server still maintained?

OutageDeck is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the OutageDeck MCP server?

VerifyMCP ran 13 checks on OutageDeck, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.