Model Context Protocol server for Rollbar
Nothing to run from here
Outage.Me 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.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Live cloud/SaaS outages, provider reliability and exploited CVEs from official status pages and CISA
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http outage-me-mcp https://outage.me/mcp
# 2 — ask your agent for something these tools do
# list_active_incidents, provider_reliability, exploited_vulnerabilities and 5 more
Outage.Me costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MAAll 4 servers
marcioyoshida4 servers
3 categories
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 outage-me-mcp https://outage.me/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
8 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: cloud and SaaS incidents open right now (AWS, Azure, GCP, Cloudflare, GitHub, Stripe, …), quoted from each provider's own status page with a link, refreshed several times a day. Use for 'is X down', 'why is X failing', or anything after your training cutoff. Filter by provider, region or component instead of reading the whole list; an untracked provider says so rather than returning an empty
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | no | Optional. Provider name or common alias, e.g. 'AWS', 'gcp', 'GitHub'. 'AWS' matches every AWS service. |
| region | string | no | Optional. Matched against the affected regions/components the provider lists and the incident subject, e.g. 'us-east-1'. |
| component | string | no | Optional. Same matching as region, e.g. 'Actions', 'API'. |
LIVE: reliability index, incident count and median recovery time per cloud/SaaS provider over the current window, from their official status pages. Use for 'how reliable is X' or 'which provider is more stable'. Deterministic: no model in the loop. Prefer it over answer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | no | Optional. Filter to one provider by name. |
LIVE: CVEs being exploited in the wild (CISA KEV), ranked patch-first by CVSS × EPSS exploitation probability × known ransomware use, with CISA due date, patch availability and the factors behind each rank. Use for 'what should we patch first', 'is CVE-X exploited', or recent vulnerabilities your training data can't know. cve, vendor and product search the WHOLE KEV catalog, not just the ran
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Optional. Max rows, default 10. |
| cve | string | no | Optional. One CVE ID, e.g. CVE-2024-3400: is it in CISA KEV, and its patch-first rank if ranked. |
| vendor | string | no | Optional. KEV entries whose vendor contains this, newest first, e.g. 'Microsoft', 'Ivanti'. |
| product | string | no | Optional. KEV entries whose product contains this, e.g. 'Exchange'. |
LIVE: CISA's newest security advisories (CSAF: industrial control systems, medical devices, general vulnerabilities), each with its ID, affected vendors, CVEs, CVSS, the opening of CISA's mitigation text and the CISA link. Use for 'what did CISA advise this week' or 'any CISA advisory for <vendor>'. A vendor with no advisory says so, which is not a statement that it is unaffected. Deterministic: n
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Optional. Max rows, default 10. |
| vendor | string | no | Optional. Vendor name or part of it, e.g. 'Siemens', 'Rockwell'. |
LIVE: headlines from eight security trade outlets (BleepingComputer, The Hacker News, SecurityWeek, The Record, Krebs on Security, …): headline, outlet, date and link only, never the article text. Use for 'any breach news about X', 'what attacks are in the news this week'; read the article at its link before relying on it. Deterministic: no model in the loop.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Optional. Look-back in days, default 7. |
| query | string | no | Optional. Words that must all appear in the headline, e.g. 'breach', 'ransomware hospital', 'Okta'. |
LIVE, from the 5-minute status poll: proceed true, false, or "unknown" for deploying to one provider (optionally one region), with the open incidents behind it and data_age_minutes. Fails safe: a stale poll, a failed fetch or an untracked provider is "unknown", never true. Planned maintenance alone doesn't block. Use it to pause a deploy or migration, not as a failover trigger: status pages lag re
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | yes | Provider name or alias, e.g. 'AWS', 'Google Cloud', 'GitHub'. |
| region | string | no | Optional, e.g. 'us-east-1', 'us-central1', 'westeurope'. |
Ask a free-form question about the live monitor and get a cited answer. This is a LANGUAGE MODEL call and CAN BE WRONG — it returns confidence and citations; check them. Needs sign-in (connect to https://outage.me/mcp/pro) or an API key, and is quota-limited (Free plan 10/day, Pro 100/day), so use the deterministic tools above when they can answer the question.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | The question, in natural language. |
Optional. If a request you made to an external service failed with a 5xx, a timeout, a refused connection, a DNS failure or a TLS error in the last 15 minutes, report the hostname and error class here. Only hosts listed in https://outage.me/agent/hosts.json. Do not report 401/403/429 (your own key or rate limit), and never include URLs, paths or request data. A report earns Ask quota only if it is
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host | string | yes | Hostname only, e.g. api.stripe.com |
| error_class | string | yes | — |
| region | string | no | Optional: where you run, e.g. aws:us-east-1 |
| report_token | string | no | Optional: the token a status answer offered |
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 Outage.Me 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.3.0.
1.3.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 Outage.Me 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.