Model Context Protocol server for Rollbar
Nothing to run from here
Status.io MCP by usefulapi 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.
20
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read Status.io components, incidents, maintenance; post incidents, schedule maintenance, set status.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http status-io-mcp-by-usefulapi https://status-io.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# statusio_get_status_summary, statusio_list_components, statusio_list_incidents and 17 more
Status.io MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 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 status-io-mcp-by-usefulapi https://status-io.usefulapi.io/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
20 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.
The current state of the status page in one call: overall status, every component and container with its status code and last update, open incidents and active/upcoming maintenance. Start here. GET /status/summary/{statuspage_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
List the components of the status page and the containers (data centers / locations) attached to each, with ids. Component and container ids are needed to update a status or to say what an incident affects ('<component_id>-<container_id>'). GET /component/list/{statuspage_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
The ids of all active and resolved incidents (ids only, no details): a quick way to see which incidents exist. Fetch one with statusio_get_incident. GET /incidents/{statuspage_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
Active (unresolved) incidents with their messages and affected components. GET /incident/list/active/{statuspage_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
| page | integer | no | Page number, from 1 (default 1). Status.io reports no totals: ask for the next page until a page comes back empty. |
Resolved incidents (history) with their messages and affected components. GET /incident/list/resolved/{statuspage_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
| page | integer | no | Page number, from 1 (default 1). Status.io reports no totals: ask for the next page until a page comes back empty. |
One incident in full: components, containers, infrastructure affected and all its messages. GET /incident/{statuspage_id}/{incident_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| incident_id | string | yes | Incident id (from statusio_list_incidents or the active/resolved lists). |
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
One message (update) of an incident: text, state, status, time and the user who posted it. GET /incident/message/{statuspage_id}/{message_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message_id | string | yes | Incident message id (from statusio_get_incident). |
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
The ids of all active, closed and upcoming maintenance events (ids only). Fetch one with statusio_get_maintenance. GET /maintenances/{statuspage_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
Maintenance events in one state, with messages and affected components: pending (scheduled, not started), active (in progress) or closed (finished). GET /maintenance/list/{pending|active|closed}/{statuspage_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | pending = scheduled and not started, active = in progress, closed = finished. |
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
| page | integer | no | Page number, from 1 (default 1). Status.io reports no totals: ask for the next page until a page comes back empty. |
One maintenance event in full, with all messages and the infrastructure affected. GET /maintenance/{statuspage_id}/{maintenance_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| maintenance_id | string | yes | Maintenance id (from statusio_list_maintenance_ids or statusio_list_maintenance). |
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
One message of a maintenance event. GET /maintenance/message/{statuspage_id}/{message_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message_id | string | yes | Maintenance message id (from statusio_get_maintenance). |
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
List the people and endpoints subscribed to the status page (email addresses, phone numbers, webhook hosts) with ids and their granular preferences. This is personal data of your subscribers. Webhook URLs are shortened to their host, because they can carry secrets. GET /subscriber/list/{statuspage_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
WRITE: change the PUBLIC status of one component/container pair (for example to degraded_performance) without creating an incident. It changes what visitors of your status page see right away. Set it back to operational when done. Ids from statusio_list_components. POST /component/status/update.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| component_id | string | yes | Component id. |
| container_id | string | yes | Container id; it must be attached to that component. |
| status | string | yes | New status level. |
| details | string | yes | Short message shown with the status change. |
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
WRITE: open a new incident on the PUBLIC status page. It is visible to every visitor immediately and sets the status of the affected components. No subscriber, Slack, Teams, IRC or Twitter notification is sent unless you switch it on (notify_*). Returns the new incident id. Say what is affected with all_infrastructure_affected or infrastructure_affected pairs. POST /incident/create.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Short incident title. |
| details | string | yes | Message describing the incident. |
| status | string | yes | Status the affected components get. |
| state | string | no | Incident state (default investigating). |
| all_infrastructure_affected | boolean | no | true = every component and container is affected. Otherwise give infrastructure_affected. |
| infrastructure_affected | array | no | Affected pairs, each '<component_id>-<container_id>' (ids from statusio_list_components). |
| notify_email | boolean | no | Also email your email subscribers (default false). |
| notify_sms | boolean | no | Also text your SMS subscribers (default false). |
| notify_webhook | boolean | no | Also call your webhook subscribers (default false). |
| notify_slack | boolean | no | Also post to your connected Slack channels (default false). |
| notify_msteams | boolean | no | Also post to your connected Microsoft Teams channels (default false). |
| notify_irc | boolean | no | Also post to your connected IRC channel (default false). |
| post_to_twitter | boolean | no | Also post to your connected Twitter/X account (default false). |
| message_subject | string | no | Subject line for the email notification. |
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
WRITE: post a new update message on an existing incident and set its state and component status. The message is public at once. No subscriber or channel notification is sent unless you switch it on (notify_*). To close an incident use statusio_resolve_incident. POST /incident/update.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| incident_id | string | yes | Incident id. |
| details | string | yes | Message describing this update. |
| status | string | yes | Status the affected components get now. |
| state | string | yes | Incident state now. |
| notify_email | boolean | no | Also email your email subscribers (default false). |
| notify_sms | boolean | no | Also text your SMS subscribers (default false). |
| notify_webhook | boolean | no | Also call your webhook subscribers (default false). |
| notify_slack | boolean | no | Also post to your connected Slack channels (default false). |
| notify_msteams | boolean | no | Also post to your connected Microsoft Teams channels (default false). |
| notify_irc | boolean | no | Also post to your connected IRC channel (default false). |
| post_to_twitter | boolean | no | Also post to your connected Twitter/X account (default false). |
| message_subject | string | no | Subject line for the email notification. |
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
WRITE: resolve an incident with a closing message. The affected components return to operational and the incident moves to history. No notification is sent unless you switch it on (notify_*). POST /incident/resolve.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| incident_id | string | yes | Incident id. |
| details | string | yes | Message describing the resolution. |
| notify_email | boolean | no | Also email your email subscribers (default false). |
| notify_sms | boolean | no | Also text your SMS subscribers (default false). |
| notify_webhook | boolean | no | Also call your webhook subscribers (default false). |
| notify_slack | boolean | no | Also post to your connected Slack channels (default false). |
| notify_msteams | boolean | no | Also post to your connected Microsoft Teams channels (default false). |
| notify_irc | boolean | no | Also post to your connected IRC channel (default false). |
| post_to_twitter | boolean | no | Also post to your connected Twitter/X account (default false). |
| message_subject | string | no | Subject line for the email notification. |
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
WRITE: schedule a planned maintenance on the PUBLIC status page. It is visible to visitors as upcoming maintenance. Subscribers are told only if you switch on notify_now / notify_72_hr / notify_24_hr / notify_1_hr (all default off). With automation true Status.io starts and ends it by itself at the planned times. Returns the maintenance id. POST /maintenance/schedule.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Short maintenance title. |
| details | string | yes | Message describing the maintenance. |
| start | string | yes | Planned start, 'YYYY-MM-DD HH:mm' (24-hour). Status.io's reference does not state the time zone of this input: check the scheduled time in your dashboard. |
| end | string | yes | Planned end, 'YYYY-MM-DD HH:mm' (24-hour); after the start. |
| all_infrastructure_affected | boolean | no | true = every component and container is affected. Otherwise give infrastructure_affected. |
| infrastructure_affected | array | no | Affected pairs, each '<component_id>-<container_id>' (ids from statusio_list_components). |
| notify_now | boolean | no | Tell subscribers right away (default false). |
| notify_72_hr | boolean | no | Remind subscribers 72 hours before the start (default false). |
| notify_24_hr | boolean | no | Remind subscribers 24 hours before the start (default false). |
| notify_1_hr | boolean | no | Remind subscribers 1 hour before the start (default false). |
| automation | boolean | no | Start and end the maintenance automatically at the planned times (default false). |
| automation_start_text | string | no | Message posted when the maintenance starts (with automation). |
| automation_stop_text | string | no | Message posted when the maintenance ends (with automation). |
| message_subject | string | no | Subject line for the email notifications. |
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
WRITE: start a scheduled maintenance now; it moves from pending to active and the affected components show planned maintenance. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/start.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| maintenance_id | string | yes | Maintenance id. |
| details | string | yes | Message describing this maintenance update. |
| notify_email | boolean | no | Also email your email subscribers (default false). |
| notify_sms | boolean | no | Also text your SMS subscribers (default false). |
| notify_webhook | boolean | no | Also call your webhook subscribers (default false). |
| notify_slack | boolean | no | Also post to your connected Slack channels (default false). |
| notify_msteams | boolean | no | Also post to your connected Microsoft Teams channels (default false). |
| notify_irc | boolean | no | Also post to your connected IRC channel (default false). |
| post_to_twitter | boolean | no | Also post to your connected Twitter/X account (default false). |
| message_subject | string | no | Subject line for the email notification. |
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
WRITE: post a new status message on an active maintenance event. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/update.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| maintenance_id | string | yes | Maintenance id. |
| details | string | yes | Message describing this maintenance update. |
| notify_email | boolean | no | Also email your email subscribers (default false). |
| notify_sms | boolean | no | Also text your SMS subscribers (default false). |
| notify_webhook | boolean | no | Also call your webhook subscribers (default false). |
| notify_slack | boolean | no | Also post to your connected Slack channels (default false). |
| notify_msteams | boolean | no | Also post to your connected Microsoft Teams channels (default false). |
| notify_irc | boolean | no | Also post to your connected IRC channel (default false). |
| post_to_twitter | boolean | no | Also post to your connected Twitter/X account (default false). |
| message_subject | string | no | Subject line for the email notification. |
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
WRITE: finish an active maintenance event; it moves to history and the affected components return to operational. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/finish.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| maintenance_id | string | yes | Maintenance id. |
| details | string | yes | Message describing this maintenance update. |
| notify_email | boolean | no | Also email your email subscribers (default false). |
| notify_sms | boolean | no | Also text your SMS subscribers (default false). |
| notify_webhook | boolean | no | Also call your webhook subscribers (default false). |
| notify_slack | boolean | no | Also post to your connected Slack channels (default false). |
| notify_msteams | boolean | no | Also post to your connected Microsoft Teams channels (default false). |
| notify_irc | boolean | no | Also post to your connected IRC channel (default false). |
| post_to_twitter | boolean | no | Also post to your connected Twitter/X account (default false). |
| message_subject | string | no | Subject line for the email notification. |
| statuspage_id | string | no | Status page id. Defaults to the status page chosen when you connected. |
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 Status.io MCP by usefulapi 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: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. 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.0.0.
1.0.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 Status.io MCP by usefulapi 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.