Model Context Protocol server for Rollbar
Nothing to run from here
Instatus 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.
93/100
tool-list score
14
tools declared
remote
at its publisher
—
calls last 7d
What it does
Manage status pages: components, incidents and maintenances; set live component status.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http usefulapi-instatus-mcp https://instatus.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# instatus_list_pages, instatus_list_components, instatus_get_component and 11 more
Instatus 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 usefulapi-instatus-mcp https://instatus.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
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.
List all status pages on the account — each page's id, subdomain, name, status, url, custom domain, and timestamps. The page id is what every other tool takes as page_id. Instatus: GET /v2/pages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number to fetch (default 1). |
| per_page | integer | no | Items per page (default 50, max 100). |
List a status page's components — id, name, description, status, order, showUptime, grouped, archived. The component ids are what you set impact on. Instatus: GET /v2/{page_id}/components.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The status page's id (from list_pages). |
| page | integer | no | Page number to fetch (default 1). |
| per_page | integer | no | Items per page (default 50, max 100). |
Get a single component by id — its full state (name, description, status, order, showUptime, grouped, archived). Instatus: GET /v2/{page_id}/components/{component_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The status page's id. |
| component_id | string | yes | The component's id. |
List a status page's incidents, most recent first — optionally filtered by status. Each incident: id, name, status, impact, affected components, updates, timestamps. Instatus: GET /v1/{page_id}/incidents.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The status page's id. |
| status | string | no | Filter to incidents with this status (INVESTIGATING, IDENTIFIED, MONITORING, RESOLVED). |
| page | integer | no | Page number to fetch (default 1). |
| per_page | integer | no | Items per page (default 50, max 100). |
Get a single incident by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/incidents/{incident_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The status page's id. |
| incident_id | string | yes | The incident's id. |
List a status page's scheduled maintenances, most recent first — id, name, status, affected components, start/end, updates. Instatus: GET /v2/{page_id}/maintenances.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The status page's id. |
| page | integer | no | Page number to fetch (default 1). |
| per_page | integer | no | Items per page (default 50, max 100). |
Get a single scheduled maintenance by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/maintenances/{maintenance_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The status page's id. |
| maintenance_id | string | yes | The maintenance's id. |
UPDATES a component by id — this MODIFIES live status-page data. The key way to set a component's operational status (OPERATIONAL, UNDERMAINTENANCE, DEGRADEDPERFORMANCE, PARTIALOUTAGE, MAJOROUTAGE). Send only the fields you want to change. Instatus: PUT /v2/{page_id}/components/{component_id}. Returns the updated component.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The status page's id. |
| component_id | string | yes | The component's id to update. |
| name | string | no | Component name. |
| description | string | no | Free-form component description. |
| status | string | no | Operational status of the component. |
| order | integer | no | Display order of the component on the page. |
| showUptime | boolean | no | Whether to show the uptime graph for this component. |
| grouped | boolean | no | Whether the component is displayed within a group. |
| archived | boolean | no | Whether the component is archived (hidden). |
CREATES a new incident — this MODIFIES live status-page data and can notify subscribers. Provide name (required); optionally set the initial message, affected components, per-component impact via statuses, status, started, notify, and shouldPublish. Instatus: POST /v1/{page_id}/incidents. Returns the created incident.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The status page's id. |
| name | string | yes | Incident title (required). |
| message | string | no | Incident update message (Markdown supported). |
| components | array | no | Component ids affected by this incident. |
| started | string | no | ISO 8601 timestamp for when the incident started. |
| status | string | no | Incident status. |
| notify | boolean | no | Whether to notify subscribers about this update. |
| statuses | array | no | Per-component impact — set each listed component's status for this event. |
| shouldPublish | boolean | no | Whether the incident should be published to the status page. |
UPDATES an existing incident by id — this MODIFIES live status-page data and can notify subscribers (e.g. move it to MONITORING or RESOLVED). Send only the fields you want to change. Instatus: PUT /v1/{page_id}/incidents/{incident_id}. Returns the updated incident.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The status page's id. |
| incident_id | string | yes | The incident's id to update. |
| name | string | no | Incident title. |
| message | string | no | Incident update message (Markdown supported). |
| components | array | no | Component ids affected by this incident. |
| started | string | no | ISO 8601 timestamp for when the incident started. |
| status | string | no | Incident status. |
| notify | boolean | no | Whether to notify subscribers about this update. |
| statuses | array | no | Per-component impact — set each listed component's status for this event. |
| shouldPublish | boolean | no | Whether the incident should be published to the status page. |
PERMANENTLY DELETES an incident by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/incidents/{incident_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The status page's id. |
| incident_id | string | yes | The incident's id to delete. |
CREATES a new scheduled maintenance — this MODIFIES live status-page data and can notify subscribers. Provide name (required); optionally set message, affected components, per-component impact via statuses, status, start/end, duration, and notify. Instatus: POST /v1/{page_id}/maintenances. Returns the created maintenance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The status page's id. |
| name | string | yes | Maintenance title (required). |
| message | string | no | Maintenance update message (Markdown supported). |
| components | array | no | Component ids affected by this maintenance. |
| start | string | no | ISO 8601 timestamp for when the maintenance starts. |
| end | string | no | ISO 8601 timestamp for when the maintenance ends. |
| status | string | no | Maintenance status. |
| notify | boolean | no | Whether to notify subscribers about this update. |
| duration | integer | no | Maintenance duration in minutes. |
| statuses | array | no | Per-component impact — set each listed component's status for this event. |
UPDATES an existing scheduled maintenance by id — this MODIFIES live status-page data and can notify subscribers. Send only the fields you want to change. Instatus: PUT /v1/{page_id}/maintenances/{maintenance_id}. Returns the updated maintenance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The status page's id. |
| maintenance_id | string | yes | The maintenance's id to update. |
| name | string | no | Maintenance title. |
| message | string | no | Maintenance update message (Markdown supported). |
| components | array | no | Component ids affected by this maintenance. |
| start | string | no | ISO 8601 timestamp for when the maintenance starts. |
| end | string | no | ISO 8601 timestamp for when the maintenance ends. |
| status | string | no | Maintenance status. |
| notify | boolean | no | Whether to notify subscribers about this update. |
| duration | integer | no | Maintenance duration in minutes. |
| statuses | array | no | Per-component impact — set each listed component's status for this event. |
PERMANENTLY DELETES a scheduled maintenance by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/maintenances/{maintenance_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The status page's id. |
| maintenance_id | string | yes | The maintenance's id to delete. |
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 Instatus 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: —
ATool-list grade · score 93 / 100
Release 1.11.1 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest04258eb663c58d7a0813a27f97381ba9c28f422cd9d9337b195f3629eeb184f9
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| instatus_list_pages | no tags | |
| instatus_list_components | no tags | |
| instatus_get_component | no tags | |
| instatus_list_incidents | no tags | |
| instatus_get_incident | no tags | |
| instatus_list_maintenances | no tags | |
| instatus_get_maintenance | no tags | |
| instatus_update_component | state-write | state-write: declares destructiveHint: true |
| instatus_create_incident | state-write | state-write: declares destructiveHint: true |
| instatus_update_incident | state-write | state-write: declares destructiveHint: true |
| instatus_delete_incident | state-write | state-write: declares destructiveHint: true |
| instatus_create_maintenance | state-write | state-write: declares destructiveHint: true |
| instatus_update_maintenance | state-write | state-write: declares destructiveHint: true |
| instatus_delete_maintenance | state-write | state-write: declares destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest04258eb663c58d7a
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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.11.1.
1.11.1
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 Instatus 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.