# com.outagedeck/outagedeck-status Live status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them? - **Type:** MCP server - **Trust:** 60/100 (B), scored on the content rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 1.1.0 - **Author:** com.outagedeck - **License:** Unknown - **Endpoints:** streamable-http https://outagedeck.com/api/mcp - **Source:** https://outagedeck.com/developers/mcp - **Endpoint health:** reachable (last checked 2026-09-20T11:49:41.860Z, 5 samples) — uptime is not a security property and is not part of the trust score - **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport) ## Trust 60/100 (B), scored on the content rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: clean - Obfuscation scan: clean - Evidence age: 1 day ## Security scan - **Status:** clean - **Scanned:** 2026-09-20T11:49:41.860Z - **Version scanned:** live - **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it. **Findings** - injection-shaped content (note) in the `add_custom_provider` tool: Links to undeclared domain: status.yourvendor.com ## Tools 14 declared. Observed from a live `tools/list` probe. - `get_provider_status` — 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, - `check_my_stack` — 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 - `list_active_incidents` — Every incident currently open across all tracked providers, most severe first. Optionally filter by severity (critical, major, minor, maintenance). Use to answe - `get_incident_details` — Full detail for one incident: updates from the official incident source in chronological order, the services OutageDeck matched to it, severity, and resolution - `get_uptime` — 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 - `get_outage_report` — A reliability summary across every tracked provider over a trailing window (7-90 days, default 30): incident totals, severity and category breakdowns, the provi - `search_providers` — 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 st - `list_custom_providers` — 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 - `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 - `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 - `remove_custom_provider` — Deletes one of the caller's custom providers and its stored incident history, freeing a slot on their plan. Requires an API key. - `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. Alerts are em - `search` — Search everything OutageDeck tracks: cloud and SaaS providers, and their incident history. Returns citable results with stable ids for the fetch tool. Use for o - `fetch` — 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 ## Install **Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it. **Cautions** (coverage gaps and advisories — never blocking) - No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it. - No publisher has proved control of this listing; it is indexed, not vouched for. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"outagedeck-status\": {\n \"type\": \"http\",\n \"url\": \"https://outagedeck.com/api/mcp\"\n }\n }\n}" ``` ## Blast radius Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on someone else's infrastructure. - Floor 32, ceiling 56 (tier: unknown) - `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low. - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/com.outagedeck%2Foutagedeck-status - Install plan: https://forgeregistry.com/api/v1/packages/com.outagedeck%2Foutagedeck-status/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/com.outagedeck%2Foutagedeck-status - HTML page: https://forgeregistry.com/registry/com.outagedeck%2Foutagedeck-status - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.