_ registry / mcp streamable-http · checked 1h ago

outagedeck

https://outagedeck.com

Registry code: a1de8ebd7a046d36

api record

OutageDeck reports the live status of major cloud and SaaS providers (AWS, Azure, Google Cloud, GitHub, OpenAI, Anthropic, Cloudflare, and 160+ more) from the official status source that publishes each one, refreshed about every 10 minutes. Use it to answer "is X down?", to check a whole stack at once before debugging, and to read independent uptime history. Provider arguments accept slugs, names, or product names ("claude" resolves to Anthropic); use search_providers when unsure. Every status here is read from the official source that publishes it: usually the provider's own status page, and…

endpoint
https://outagedeck.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is outagedeck live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is outagedeck free to use?
Yes — the hub reached it with no key and no payment.
What tools does outagedeck have?
14 tools: get_provider_status, add_custom_provider, update_custom_provider, search, watch_provider, search_providers, remove_custom_provider, get_incident_details, ….
Is outagedeck safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.5%· all time 99.5%

latency
968ms

last good check

priced tools
0

of 14 tools

_ answered our checks, 90 days 407 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • check if a cloud provider is down
  • check a whole stack's status
  • get provider uptime history
  • list active incidents
  • watch a provider for outages
takes → gives
text → data
tools
10 reads4 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 14 tools
6 open 8 never probed 6 of 14 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_outage_report reads open 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 90,
          "minimum": 7,
          "description": "Trailing window in days (default 30)."
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
  • fetch reads open 12h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "A document id returned by search, e.g., \"provider:aws\" or \"incident:github-actions-delays-2026-07-31\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • list_active_incidents reads open 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "severity": {
          "enum": [
            "minor",
            "major",
            "critical",
            "maintenance"
          ],
          "type": "string",
          "description": "Only incidents of this severity."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • list_custom_providers reads open 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • check_my_stack reads open 12h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "providers"
      ],
      "properties": {
        "providers": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 12,
          "minItems": 1,
          "description": "Provider slugs, names, or product names, one per vendor the stack depends on."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_uptime reads open 12h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "provider"
      ],
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 90,
          "minimum": 7,
          "description": "Trailing window in days (default 30)."
        },
        "provider": {
          "type": "string",
          "description": "Provider slug, name, or product name."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • get_provider_status reads unknown 5h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "provider"
      ],
      "properties": {
        "provider": {
          "type": "string",
          "description": "Provider slug, name, or product name, e.g., \"aws\", \"GitHub\", \"chatgpt\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • add_custom_provider changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "The vendor's status page address, for example https://status.yourvendor.com."
        },
        "name": {
          "type": "string",
          "description": "Optional display name. Defaults to the name the status page publishes."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • update_custom_provider changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "provider"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "New status page address."
        },
        "name": {
          "type": "string",
          "description": "New display name."
        },
        "state": {
          "enum": [
            "active",
            "paused"
          ],
          "type": "string",
          "description": "Resume or pause reading it. An active feed is read about every 10 minutes."
        },
        "provider": {
          "type": "string",
          "description": "The custom provider's name or id."
        }
      },
      "additionalProperties": false
    }
    arguments 29 lines
  • search reads unknown 5h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "What to look for: a vendor name, a product, or words from an incident title, e.g., \"cloudflare\", \"elevated error rates\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • watch_provider changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "provider"
      ],
      "properties": {
        "provider": {
          "type": "string",
          "description": "A tracked provider (slug, name, or product name) or one of the caller's own custom providers."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • search_providers reads unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Free-text search over provider names and aliases."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • remove_custom_provider changes data unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "provider"
      ],
      "properties": {
        "provider": {
          "type": "string",
          "description": "The custom provider's name or id."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_incident_details reads unknown 5h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "incident"
      ],
      "properties": {
        "incident": {
          "type": "string",
          "description": "Incident slug, e.g., from an earlier list_active_incidents result."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a1de8ebd7a046d36.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a1de8ebd7a046d36/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a1de8ebd7a046d36/badge.svg)](https://brick.blue/agent/a1de8ebd7a046d36?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.