Model Context Protocol server for Rollbar
Nothing to run from here
QuickStatus 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
34
tools declared
remote
at its publisher
—
calls last 7d
What it does
Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http quickstatus-mcp https://api.quickstatus.dev/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'
# 2 — ask your agent for something these tools do
# usage, list_regions, list_checks and 31 more
It needs AUTHORIZATION (Bearer followed by your sp_ API key from the QuickStatus console (API Keys)): this sends it in the Authorization header from your environment, so export it first — its endpoint answers 401 without it.
QuickStatus costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
QUAll 1 server
quickstatus1 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 Code reads AUTHORIZATION (Bearer followed by your sp_ API key from the QuickStatus console (API Keys)) from your environment each time it connects and sends it in the Authorization header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx AUTHORIZATION … and open a new terminal (Windows).
claude mcp add --scope user --transport http quickstatus-mcp https://api.quickstatus.dev/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'Reconnect, 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 — but its publisher asks for a key of their own on every call.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: Authorization header — Bearer followed by your sp_ API key from the QuickStatus console (API Keys).. You set it in your own client’s config, on your machine — this marketplace never holds it.
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
34 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.
Plan caps for this workspace: plan, period, probe_count, monthly_probe_quota, endpoints_used, max_endpoints, max_regions, min_interval_seconds, sample_retention_days, max_status_pages. Call this before creating anything. Stop when a cap is reached.
No parameter schema on file.
Enabled probe regions: id, name, and region.
No parameter schema on file.
Checks in this workspace. Use this before create_check so you do not add a second check for a URL that is already watched.
No parameter schema on file.
One check, including assertion, DNS, and TCP fields. Secrets such as request headers, request body, and HTTP auth are not returned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint_id | string | yes | — |
Check results. view is status, history, or outages. history uses hours (default 24) and returns status, status_code, latency_ms, dns_ms, connect_ms, location_name, location_region, and observed_at. Sample metadata is omitted.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint_id | string | yes | — |
| view | string | yes | — |
| hours | no | — |
Create a check. kind is http, api, dns, or tcp. Defaults: GET, status 200, 10s timeout, email alerts on, interval_seconds from the plan minimum, and one region. DNS defaults to an A record over UDP. TCP requires port. Pass regions only when you want more than the default, and only within max_regions from usage. Request headers, request body, and HTTP auth stay in the console. To link a status page
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| target | string | yes | — |
| kind | string | yes | — |
| port | no | — | |
| regions | no | — | |
| interval_seconds | no | — | |
| http_method | no | — | |
| expected_status_codes | no | — | |
| body_contains | no | — | |
| timeout_seconds | no | — | |
| follow_redirects | no | — | |
| verify_ssl | no | — | |
| dns_record_type | no | — | |
| dns_protocol | no | — | |
| dns_server | no | — | |
| dns_expected_values | no | — | |
| tcp_ip_family | no | — | |
| tcp_payload | no | — | |
| tcp_expected_outcome | no | — | |
| alert_email_enabled | no | — |
Update a check. Pass only the fields to change. enabled false pauses and true resumes. Linking requires site_id, site_slug, and component_id together, plus optional incident_mode (off, auto, or review: review stores a draft a person approves before it is published), incident_auto_resolve, and display_metrics. Request headers, request body, and HTTP auth stay in the console.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint_id | string | yes | — |
| name | no | — | |
| target | no | — | |
| enabled | no | — | |
| interval_seconds | no | — | |
| regions | no | — | |
| http_method | no | — | |
| expected_status_codes | no | — | |
| body_contains | no | — | |
| timeout_seconds | no | — | |
| follow_redirects | no | — | |
| verify_ssl | no | — | |
| dns_record_type | no | — | |
| dns_protocol | no | — | |
| dns_server | no | — | |
| dns_expected_values | no | — | |
| port | no | — | |
| tcp_ip_family | no | — | |
| tcp_payload | no | — | |
| tcp_expected_outcome | no | — |
Delete a check. Run only when the user asked to delete this check in this conversation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint_id | string | yes | — |
Queue a probe for one check from each of its live regions (the same regions a scheduled run uses). Returns job_id and regions. Call get_check_results with view status for the result; it is not included here.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint_id | string | yes | — |
Status pages in this workspace: slug, name, visibility, publicUrl, custom domain, and the worst open incident status.
No parameter schema on file.
One status page: components with ids, groups, incidents with public ids, Slack connection state, and alert-destination ids. has_password is returned; the password is not.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
Create a public status page. visibility internal requires Pro and a password of at least 8 characters that the user typed; never invent a password or repeat it. custom_domain is a hostname such as status.acme.com and requires Pro. With endpoint_ids, each check becomes a component linked to the page with incidents and latency enabled. Returns slug, publicUrl, component ids, and linked check ids. If
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| slug | string | yes | — |
| endpoint_ids | no | — | |
| visibility | no | — | |
| password | no | — | |
| url | no | — | |
| custom_domain | no | — |
Update a status page. Fields: name, url, visibility, password, custom_domain, show_auto_detected (label incidents a check opened itself as detected automatically). custom_domain null removes it. visibility internal needs a password of at least 8 characters that the user typed. Never invent a password or repeat it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| name | no | — | |
| url | no | — | |
| visibility | no | — | |
| password | no | — | |
| custom_domain | no | — | |
| show_auto_detected | no | — |
Delete a status page and its components. Run only when the user asked to delete this page in this conversation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
Check the CNAME and TXT records for a status page custom domain.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
Add a component to an existing status page. Returns its id so update_check can link a check to it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| name | string | yes | — |
| url | no | — |
Rename a component or change its URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| component_id | string | yes | — |
| name | no | — | |
| url | no | — |
Delete a component. Run only when the user asked to delete this component in this conversation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| component_id | string | yes | — |
Create, update, or delete a component group. action is create, update, or delete. create and update need name. update and delete need group_id. Delete only when the user asked.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| action | string | yes | — |
| group_id | no | — | |
| name | no | — |
Slack connection for a status page. action start returns a URL for the user to open; do not complete OAuth. action disconnect removes the connection. Disconnect only when the user asked. Connection state is on get_status_page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| action | string | yes | — |
Replace the alert destinations attached to a status page with these existing destination ids. Use list_alert_destinations for the ids. An empty list detaches all of them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| destination_ids | array | yes | — |
Drafts waiting for review from checks in incident_mode review, pending first. Approving one publishes it as a status incident.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
Publish a pending review draft as a status incident. This emails subscribers and posts to Slack. Run only when the user asked to publish it in this conversation. Optional title, body, and impact (minor, major, or critical) replace the draft text.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| proposal_id | string | yes | — |
| title | no | — | |
| body | no | — | |
| impact | no | — |
Dismiss a pending review draft. Nothing is published.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| proposal_id | string | yes | — |
Open an incident. This emails subscribers and posts to Slack the same way the console does. Run only when the user asked to publish this incident in this conversation. status is investigating, identified, monitoring, or resolved. impact is minor, major, or critical. component_ids are component public ids. opened_at with resolved_at backfills a past incident.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| title | string | yes | — |
| body | string | yes | — |
| status | string | yes | — |
| impact | string | yes | — |
| component_ids | no | — | |
| opened_at | no | — | |
| resolved_at | no | — |
One incident, including updates newest first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| public_id | string | yes | — |
Edit an incident's title or impact. Run only when the user asked. With update_id and update_body, rewrite that posted update's message (no new notification). To change status, post a message, or resolve, use post_incident_update instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| public_id | string | yes | — |
| title | no | — | |
| body | no | — | |
| status | no | — | |
| impact | no | — | |
| component_ids | no | — | |
| update_id | no | — | |
| update_body | no | — |
Post an incident update. This emails subscribers and posts to Slack. Run only when the user asked to publish this update in this conversation. status resolved closes the incident.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| public_id | string | yes | — |
| status | string | yes | — |
| body | string | yes | — |
Maintenance windows: id, name, starts_at, duration_seconds, timezone, recurrence, weekdays, ends_at, notify_subscribers, and items.
No parameter schema on file.
Schedule a maintenance window. duration_seconds is 60 through 7 days. Pass both the check (endpoint_ids) and its public component (status_components) so probes pause and the page shows Under maintenance. notify_subscribers defaults to false. Set it true only when the user asked to email subscribers. This can email subscribers, so run only when the user asked to schedule this window.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| starts_at | string | yes | — |
| duration_seconds | integer | yes | — |
| timezone | string | yes | — |
| endpoint_ids | no | — | |
| status_components | no | — | |
| weekdays | no | — | |
| notify_subscribers | no | — |
Update a maintenance window. notify_subscribers defaults to false unless you set it. This can email subscribers. Run only when the user asked to change this window.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| window_id | string | yes | — |
| name | no | — | |
| starts_at | no | — | |
| duration_seconds | no | — | |
| timezone | no | — | |
| weekdays | no | — | |
| endpoint_ids | no | — | |
| status_components | no | — | |
| notify_subscribers | no | — |
Cancel a maintenance window. notify_subscribers defaults to false. This can email subscribers. Run only when the user asked to cancel this window in this conversation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| window_id | string | yes | — |
| notify_subscribers | no | — |
Existing alert destinations: id, kind, name, and hint. Secrets are not returned. Creating a destination stays in the console.
No parameter schema on file.
Send a real test alert to an existing destination. Run only when the user asked to send the test.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination_id | string | yes | — |
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 QuickStatus 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.1.0 · scanned 7 Nov 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 digestc1aae0b2a17bff4cf48c285fdb0a1a2cbc30b1a647e58e9323ac428471a4aa66
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 |
|---|---|---|
| usage | no tags | |
| list_regions | no tags | |
| list_checks | no tags | |
| get_check | no tags | |
| get_check_results | no tags | |
| create_check | state-write | state-write: declares readOnlyHint: false |
| update_check | state-write | state-write: declares readOnlyHint: false |
| delete_check | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| run_check | state-write | state-write: declares readOnlyHint: false |
| list_status_pages | no tags | |
| get_status_page | no tags | |
| create_status_page | state-write | state-write: declares readOnlyHint: false |
| update_status_page | state-write | state-write: declares readOnlyHint: false |
| delete_status_page | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| verify_custom_domain | state-write | state-write: declares readOnlyHint: false |
| create_component | state-write | state-write: declares readOnlyHint: false |
| update_component | state-write | state-write: declares readOnlyHint: false |
| delete_component | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| manage_component_group | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| slack_connection | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| page_alert_destinations | state-write | state-write: declares readOnlyHint: false |
| list_incident_proposals | no tags | |
| approve_incident_proposal | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| dismiss_incident_proposal | state-write | state-write: declares readOnlyHint: false |
| create_incident | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_incident | no tags | |
| update_incident | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| post_incident_update | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_maintenance_windows | no tags | |
| create_maintenance_window | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| update_maintenance_window | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| cancel_maintenance_window | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_alert_destinations | no tags | |
| test_alert_destination | state-write | state-write: declares readOnlyHint: false |
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 digestc1aae0b2a17bff4c
Scanned2026-11-07
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.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 QuickStatus 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.