Model Context Protocol server for Rollbar
Nothing to run from here
OutageDeck is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
14
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Live status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them?
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http outagedeck-mcp https://outagedeck.com/api/mcp
# 2 — ask your agent for something these tools do
# get_provider_status, check_my_stack, list_active_incidents and 11 more
OutageDeck costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
OUAll 1 server
outagedeck1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http outagedeck-mcp https://outagedeck.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 trunca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | yes | Provider slug, name, or product name, e.g., "aws", "GitHub", "chatgpt". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| providers | array | yes | Provider slugs, names, or product names, one per vendor the stack depends on. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| severity | string | no | Only incidents of this severity. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| incident | string | yes | Incident slug, e.g., from an earlier list_active_incidents result. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | yes | Provider slug, name, or product name. |
| days | integer | no | Trailing window in days (default 30). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Trailing window in days (default 30). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text search over provider names and aliases. |
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.
No parameter schema on file.
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 p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The vendor's status page address, for example https://status.yourvendor.com. |
| name | string | no | Optional display name. Defaults to the name the status page publishes. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | yes | The custom provider's name or id. |
| name | string | no | New display name. |
| url | string | no | New status page address. |
| state | string | no | Resume or pause its checks, which run about every 10 minutes. |
Deletes one of the caller's custom providers and its stored incident history, freeing a slot on their plan. Requires an API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | yes | The custom provider's name or id. |
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 r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | yes | A tracked provider (slug, name, or product name) or one of the caller's own custom providers. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to look for: a vendor name, a product, or words from an incident title, e.g., "cloudflare", "elevated error rates". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | A document id returned by search, e.g., "provider:aws" or "incident:github-actions-delays-2026-07-31". |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install OutageDeck or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish OutageDeck can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.