# Quickstatus MCP server

Source: https://glimind.com/server/mcp-registry%2Fdev.quickstatus%2Fquickstatus
Registry id: `mcp-registry/dev.quickstatus/quickstatus`
Status: live (checked 2026-11-22T15:36:13.036Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 891
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "quickstatus-mcp-server": {
      "type": "http",
      "url": "https://api.quickstatus.dev/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http quickstatus-mcp-server https://api.quickstatus.dev/mcp
```

## Tools (34)

- `approve_incident_proposal`: 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
- `cancel_maintenance_window`: 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 conver
- `create_check`: Create a check. kind is http, api, dns, tcp, heartbeat, or mcp. Call usage first: it gives min_interval_seconds, max_regions, and max_endpoints (how many active
- `create_component`: Add a component to an existing status page. Returns its id so update_check can link a check to it.
- `create_incident`: 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 conver
- `create_maintenance_window`: 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 
- `create_status_page`: 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.
- `delete_check`: Delete a check. Run only when the user asked to delete this check in this conversation.
- `delete_component`: Delete a component. Run only when the user asked to delete this component in this conversation.
- `delete_status_page`: Delete a status page and its components. Run only when the user asked to delete this page in this conversation.
- `dismiss_incident_proposal`: Dismiss a pending review draft. Nothing is published.
- `get_check`: One check, including assertion, DNS, and TCP fields. Secrets such as request headers, request body, and HTTP auth are not returned.
- `get_check_results`: Check results. view is status, history, or outages; server checks also take servers and metrics. history uses hours (default 24) and returns status, status_code
- `get_incident`: One incident, including updates newest first.
- `get_status_page`: One status page: components with ids, groups, incidents with public ids, Slack connection state, and alert-destination ids. has_password is returned; the passwo
- `list_alert_destinations`: Existing alert destinations: id, kind, name, and hint. Secrets are not returned. Creating a destination stays in the console.
- `list_checks`: Checks in this workspace. Use this before create_check so you do not add a second check for a URL that is already watched.
- `list_incident_proposals`: Drafts waiting for review from checks in incident_mode review, pending first. Approving one publishes it as a status incident.
- `list_maintenance_windows`: Maintenance windows: id, name, starts_at, duration_seconds, timezone, recurrence, weekdays, ends_at, notify_subscribers, and items.
- `list_regions`: Enabled probe regions: id, name, and region.
- `list_status_pages`: Status pages in this workspace: slug, name, visibility, publicUrl, custom domain, and the worst open incident status.
- `manage_component_group`: 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
- `page_alert_destinations`: 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 al
- `post_incident_update`: 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 c
- `run_check`: 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 
- `slack_connection`: 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
- `test_alert_destination`: Send a real test alert to an existing destination. Run only when the user asked to send the test.
- `update_check`: Update a check. Pass only the fields to change; each parameter's description gives its allowed values. enabled false pauses and true resumes. Linking requires s
- `update_component`: Rename a component or change its URL.
- `update_incident`: 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
- `update_maintenance_window`: 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 win
- `update_status_page`: Update a status page. Fields: name, url, visibility, password, custom_domain, show_auto_detected (label incidents a check opened itself as detected automaticall
- `usage`: Plan caps for this workspace: plan, period, probe_count, monthly_probe_quota, endpoints_used, max_endpoints, max_regions, min_interval_seconds, sample_retention
- `verify_custom_domain`: Check the CNAME and TXT records for a status page custom domain.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
