# QuickStatus (remote · api.quickstatus.dev)

Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.quickstatus.dev`: 79/100 (this document), [markdown](https://verifymcp.io/servers/dev-quickstatus-quickstatus/api.md), [page](https://verifymcp.io/servers/dev-quickstatus-quickstatus/api)

## Channel facts

- Endpoint: `https://api.quickstatus.dev/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 4948 tokens (~145/item across 34 items; 34 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% of tool parameters carry a description.
  - Structured output schemas are declared (18% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 35 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the QuickStatus MCP server?

QuickStatus is a hosted endpoint at https://api.quickstatus.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-quickstatus-quickstatus 'https://api.quickstatus.dev/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.dev-quickstatus-quickstatus]
url = "https://api.quickstatus.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-quickstatus-quickstatus": {
      "type": "remote",
      "url": "https://api.quickstatus.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-quickstatus-quickstatus --url 'https://api.quickstatus.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-quickstatus-quickstatus:
    url: "https://api.quickstatus.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-quickstatus-quickstatus": {
      "Transport": "http",
      "Url": "https://api.quickstatus.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-quickstatus-quickstatus -t streamable-http -u 'https://api.quickstatus.dev/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 79, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] The server changed its declared name: QuickStatus → QuickStatus.dev
- [cosmetic] “create_check” reworded the description of “min_members”
- [cosmetic] “update_check” reworded the description of “min_members”

### 2026-11-18 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 77, 0)

- [security] Tool “create_check” rewrote its description, which is the text the model reads
- [security] Tool “get_check_results” rewrote its description, which is the text the model reads
- [security] Tool “usage” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 131 → 145
- [cosmetic] “create_check” added an optional parameter “alert_on_lost”
- [cosmetic] “create_check” added an optional parameter “group_grace_seconds”
- [cosmetic] “create_check” added an optional parameter “min_members”
- [cosmetic] “update_check” added an optional parameter “alert_on_lost”
- [cosmetic] “update_check” added an optional parameter “group_grace_seconds”
- [cosmetic] “update_check” added an optional parameter “min_members”
- [cosmetic] “create_check” reworded the description of “interval_seconds”
- [cosmetic] “create_check” reworded the description of “kind”
- [cosmetic] “create_check” reworded the description of “regions”
- [cosmetic] “create_check” reworded the description of “target”
- [cosmetic] “update_check” reworded the description of “interval_seconds”
- [cosmetic] “update_check” reworded the description of “regions”
- [cosmetic] “update_check” reworded the description of “target”

### 2026-11-16 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 75, 0)

- [security] Tool “create_check” rewrote its description, which is the text the model reads
- [security] Tool “get_check_results” rewrote its description, which is the text the model reads
- [security] Tool “update_check” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 0% → 42%
- [cosmetic] “create_check” added an optional parameter “cert_warn_days”
- [cosmetic] “create_check” added an optional parameter “heartbeat_grace_seconds”
- [cosmetic] “create_check” added an optional parameter “mcp_expected_tools”
- [cosmetic] “create_check” added an optional parameter “slow_metric”
- [cosmetic] “create_check” added an optional parameter “slow_threshold_ms”
- [cosmetic] “update_check” added an optional parameter “cert_warn_days”
- [cosmetic] “update_check” added an optional parameter “heartbeat_grace_seconds”
- [cosmetic] “update_check” added an optional parameter “mcp_expected_tools”
- [cosmetic] “update_check” added an optional parameter “slow_metric”
- [cosmetic] “update_check” added an optional parameter “slow_threshold_ms”
- [cosmetic] “create_check” reworded the description of “alert_destination_ids”
- [cosmetic] “create_check” reworded the description of “alert_email_enabled”
- [cosmetic] “create_check” reworded the description of “alert_incident_enabled”
- [cosmetic] “create_check” reworded the description of “body_contains”
- [cosmetic] “create_check” reworded the description of “component_id”
- [cosmetic] “create_check” reworded the description of “display_metrics”
- [cosmetic] “create_check” reworded the description of “dns_expected_values”
- [cosmetic] “create_check” reworded the description of “dns_protocol”
- [cosmetic] “create_check” reworded the description of “dns_record_type”
- [cosmetic] “create_check” reworded the description of “dns_server”
- [cosmetic] “create_check” reworded the description of “expected_status_codes”
- [cosmetic] “create_check” reworded the description of “follow_redirects”
- [cosmetic] “create_check” reworded the description of “http_method”
- [cosmetic] “create_check” reworded the description of “incident_auto_resolve”
- [cosmetic] “create_check” reworded the description of “incident_mode”
- [cosmetic] “create_check” reworded the description of “interval_seconds”
- [cosmetic] “create_check” reworded the description of “kind”
- [cosmetic] “create_check” reworded the description of “name”
- [cosmetic] “create_check” reworded the description of “port”
- [cosmetic] “create_check” reworded the description of “regions”
- [cosmetic] “create_check” reworded the description of “site_id”
- [cosmetic] “create_check” reworded the description of “site_slug”
- [cosmetic] “create_check” reworded the description of “target”
- [cosmetic] “create_check” reworded the description of “tcp_expected_outcome”
- [cosmetic] “create_check” reworded the description of “tcp_ip_family”
- [cosmetic] “create_check” reworded the description of “tcp_payload”
- [cosmetic] “create_check” reworded the description of “timeout_seconds”
- [cosmetic] “create_check” reworded the description of “verify_ssl”
- [cosmetic] “update_check” reworded the description of “alert_destination_ids”
- [cosmetic] “update_check” reworded the description of “alert_email_enabled”
- [cosmetic] “update_check” reworded the description of “alert_incident_enabled”
- [cosmetic] “update_check” reworded the description of “body_contains”
- [cosmetic] “update_check” reworded the description of “component_id”
- [cosmetic] “update_check” reworded the description of “display_metrics”
- [cosmetic] “update_check” reworded the description of “dns_expected_values”
- [cosmetic] “update_check” reworded the description of “dns_protocol”
- [cosmetic] “update_check” reworded the description of “dns_record_type”
- [cosmetic] “update_check” reworded the description of “dns_server”
- [cosmetic] “update_check” reworded the description of “enabled”
- [cosmetic] “update_check” reworded the description of “endpoint_id”
- [cosmetic] “update_check” reworded the description of “expected_status_codes”
- [cosmetic] “update_check” reworded the description of “follow_redirects”
- [cosmetic] “update_check” reworded the description of “http_method”
- [cosmetic] “update_check” reworded the description of “incident_auto_resolve”
- [cosmetic] “update_check” reworded the description of “incident_mode”
- [cosmetic] “update_check” reworded the description of “interval_seconds”
- [cosmetic] “update_check” reworded the description of “name”
- [cosmetic] “update_check” reworded the description of “port”
- [cosmetic] “update_check” reworded the description of “regions”
- [cosmetic] “update_check” reworded the description of “site_id”
- [cosmetic] “update_check” reworded the description of “site_slug”
- [cosmetic] “update_check” reworded the description of “target”
- [cosmetic] “update_check” reworded the description of “tcp_expected_outcome”
- [cosmetic] “update_check” reworded the description of “tcp_ip_family”
- [cosmetic] “update_check” reworded the description of “tcp_payload”
- [cosmetic] “update_check” reworded the description of “timeout_seconds”
- [cosmetic] “update_check” reworded the description of “verify_ssl”
- [cosmetic] “create_check” made “kind” optional
- [cosmetic] “create_check” made “target” optional

### 2026-11-12 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (34)

### `usage` (~70 tokens)

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, max_server_members (machines per server check). Call this before creating anything. Stop when a cap is reached.

### `list_regions` (~19 tokens)

Enabled probe regions: id, name, and region.

Output parameters:

- `result` (array)

### `list_checks` (~34 tokens)

Checks in this workspace. Use this before create_check so you do not add a second check for a URL that is already watched.

Output parameters:

- `result` (array)

### `get_check` (~44 tokens)

One check, including assertion, DNS, and TCP fields. Secrets such as request headers, request body, and HTTP auth are not returned.

Input parameters:

- `endpoint_id` (string, required)

### `get_check_results` (~201 tokens)

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, latency_ms, ttfb_ms (time to first byte), dns_ms, connect_ms, location_name, location_region, and observed_at. Sample metadata is omitted. servers returns each machine (state active, left, or lost; last_seen; agent_version and outdated; the latest cpu, mem, disks, net, and procs) and the alert rules with alert_open and alert_detail (which servers breach). metrics uses hours (1, 6, 24, 48, 168, or 720; default 24; Free keeps 7 days) and returns points with cpu, mem, disk, load, and network averages and maxima across the fleet.

Input parameters:

- `endpoint_id` (string, required)
- `hours`
- `view` (string, required)

Output parameters:

- `result`

### `create_check` (~1441 tokens)

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 checks the plan allows). Up rules: kind http with expected_status_codes [200] (the default) counts any response below 500 as up, so a 404 or a bot-protection 403 is up; kind api, or any other list of codes, must match exactly. heartbeat takes no target or regions; the result has ping_url, shown only this once, for the job to call with curl -fsS when it finishes (append /fail to report a failure). server (Linux machines with the QuickStatus.dev server agent) takes no target or regions; the result has install_command, shown only this once: run it as root on each Linux server to enroll it. It holds the enrollment token, so do not paste it into files or chat logs. A new server check has rules for CPU and memory above 90% for 10 minutes and any disk above 90%; rules are edited in the console. mcp runs initialize and tools/list against an MCP server URL. Each parameter's description gives its allowed values and default. Request headers, request body, and HTTP auth stay in the console.

Input parameters:

- `alert_destination_ids`: Alert destination ids from list_alert_destinations (Slack, webhook, and so on).
- `alert_email_enabled`: Email the workspace owner on down and recovery. Default true. Heartbeats alert after 1 missed or failed ping; other kinds after 3 failed runs in a row, and recover after 1 success.
- `alert_incident_enabled`: For a linked check: open one status incident per outage (or flapping period).
- `alert_on_lost`: server only: also warn for each machine that stops reporting without leaving cleanly. Default false.
- `body_contains`: Text that must appear in the response body (first 64 KB). http and api only.
- `cert_warn_days`: 7, 14, or 30: warn that many days before an https certificate expires, then once more at each smaller step (14 warns at 14, 7, and 1 day). 0 turns it off. create_check defaults to 14 for https target…
- `component_id`: Status page component to link. Pass with site_id and site_slug.
- `display_metrics`: For a linked check: show response time on the public status page.
- `dns_expected_values`: Answers that must be present, for example an IP for A or '10 mail.example.com' for MX. dns only.
- `dns_protocol`: udp (default) or tcp. dns only.
- `dns_record_type`: A (default), AAAA, CNAME, TXT, MX, NS, or CAA. dns only.
- `dns_server`: Resolver host or IP, optionally with :port. Empty uses the default resolver. dns only.
- `expected_status_codes`: Status codes that count as up. Default [200]. For kind http, exactly [200] means any response below 500 is up; any other list, such as [200, 201], must match exactly. Kind api always matches exactly.
- `follow_redirects`: Follow redirects. Default true. http and api only.
- `group_grace_seconds`: server only: seconds the check may stay below min_members before it goes down, so a reboot or rolling deploy does not alert. Default 300; 0 means at once.
- `heartbeat_grace_seconds`: heartbeat only: extra seconds after the expected ping before it counts as missed. 0 means no grace; up to 86400. Default: the same as interval_seconds.
- `http_method`: GET (default), POST, PUT, PATCH, DELETE, or HEAD. http and api only.
- `incident_auto_resolve`: For a linked check: resolve the incident when the check recovers.
- `incident_mode`: For a linked check: off, auto (publish incidents), or review (store a draft a person approves before it is published).
- `interval_seconds`: Seconds between runs (heartbeat: how often the job pings; server: how often each machine reports, at least 60). At least the plan minimum (min_interval_seconds from usage, for example 300 on Free) an…
- `kind` (string): http, api, dns, tcp, heartbeat, mcp, or server.
- `mcp_expected_tools`: mcp only: tool names that must appear in tools/list. Tools are listed, never called.
- `min_members`: server only: the check goes down when fewer machines than this are reporting. Default 1. At most max_server_members from usage (Free 1, Pro 25, Scale 100).
- `name` (string, required): Display name. Blank comes from the target; a blank heartbeat is named Heartbeat, so pass a name that says which job it watches.
- `port`: TCP port (1 to 65535). Required for kind tcp; other kinds reject it.
- `regions`: Region codes from list_regions, for example us-west-1. Omit for the default region. At most max_regions from usage. heartbeat and server take none.
- `site_id`: Status page id for linking. Pass with site_slug and component_id.
- `site_slug`: Status page slug for linking. Pass with site_id and component_id.
- `slow_metric`: total (default: the whole response) or ttfb (time to first byte).
- `slow_threshold_ms`: http, api, and mcp: a successful run slower than this many ms marks the check slow. The check stays current_status up with degraded_since set, sends a slow alert, and does not count as downtime. 0 tu…
- `target` (string): http/api/mcp: a full URL (https://...). dns: a domain name. tcp: a hostname or IP only, no scheme or port (pass port separately). heartbeat and server: leave empty.
- `tcp_expected_outcome`: connect (default: up when the port accepts) or fail (up when it refuses). tcp only.
- `tcp_ip_family`: ipv4 (default) or ipv6. tcp only.
- `tcp_payload`: Text to send after connecting. tcp only.
- `timeout_seconds`: Seconds to wait for a response, 1 to 60. Default 10.
- `verify_ssl`: Fail the check when the TLS certificate is invalid or expired. Default true.

### `update_check` (~1291 tokens)

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 site_id, site_slug, and component_id together. 0 turns off slow_threshold_ms and cert_warn_days. Changing the target to http:// clears cert_warn_days and the stored certificate; changing back to https:// sets it to 14 unless you pass cert_warn_days. The kind cannot change except between http and api. Request headers, request body, and HTTP auth stay in the console.

Input parameters:

- `alert_destination_ids`: Alert destination ids from list_alert_destinations (Slack, webhook, and so on).
- `alert_email_enabled`: Email the workspace owner on down and recovery. Default true. Heartbeats alert after 1 missed or failed ping; other kinds after 3 failed runs in a row, and recover after 1 success.
- `alert_incident_enabled`: For a linked check: open one status incident per outage (or flapping period).
- `alert_on_lost`: server only: also warn for each machine that stops reporting without leaving cleanly. Default false.
- `body_contains`: Text that must appear in the response body (first 64 KB). http and api only.
- `cert_warn_days`: 7, 14, or 30: warn that many days before an https certificate expires, then once more at each smaller step (14 warns at 14, 7, and 1 day). 0 turns it off. create_check defaults to 14 for https target…
- `component_id`: Status page component to link. Pass with site_id and site_slug.
- `display_metrics`: For a linked check: show response time on the public status page.
- `dns_expected_values`: Answers that must be present, for example an IP for A or '10 mail.example.com' for MX. dns only.
- `dns_protocol`: udp (default) or tcp. dns only.
- `dns_record_type`: A (default), AAAA, CNAME, TXT, MX, NS, or CAA. dns only.
- `dns_server`: Resolver host or IP, optionally with :port. Empty uses the default resolver. dns only.
- `enabled`: false pauses the check; true resumes it (counts toward max_endpoints).
- `endpoint_id` (string, required): Check id from list_checks or create_check.
- `expected_status_codes`: Status codes that count as up. Default [200]. For kind http, exactly [200] means any response below 500 is up; any other list, such as [200, 201], must match exactly. Kind api always matches exactly.
- `follow_redirects`: Follow redirects. Default true. http and api only.
- `group_grace_seconds`: server only: seconds the check may stay below min_members before it goes down, so a reboot or rolling deploy does not alert. Default 300; 0 means at once.
- `heartbeat_grace_seconds`: heartbeat only: extra seconds after the expected ping before it counts as missed. 0 means no grace; up to 86400. Default: the same as interval_seconds.
- `http_method`: GET (default), POST, PUT, PATCH, DELETE, or HEAD. http and api only.
- `incident_auto_resolve`: For a linked check: resolve the incident when the check recovers.
- `incident_mode`: For a linked check: off, auto (publish incidents), or review (store a draft a person approves before it is published).
- `interval_seconds`: Seconds between runs (heartbeat: how often the job pings; server: how often each machine reports, at least 60). At least the plan minimum (min_interval_seconds from usage, for example 300 on Free) an…
- `mcp_expected_tools`: mcp only: tool names that must appear in tools/list. Tools are listed, never called.
- `min_members`: server only: the check goes down when fewer machines than this are reporting. Default 1. At most max_server_members from usage (Free 1, Pro 25, Scale 100).
- `name`: Display name. Blank comes from the target; a blank heartbeat is named Heartbeat, so pass a name that says which job it watches.
- `port`: TCP port (1 to 65535). Required for kind tcp; other kinds reject it.
- `regions`: Region codes from list_regions, for example us-west-1. Omit for the default region. At most max_regions from usage. heartbeat and server take none.
- `site_id`: Status page id for linking. Pass with site_slug and component_id.
- `site_slug`: Status page slug for linking. Pass with site_id and component_id.
- `slow_metric`: total (default: the whole response) or ttfb (time to first byte).
- `slow_threshold_ms`: http, api, and mcp: a successful run slower than this many ms marks the check slow. The check stays current_status up with degraded_since set, sends a slow alert, and does not count as downtime. 0 tu…
- `target`: http/api/mcp: a full URL (https://...). dns: a domain name. tcp: a hostname or IP only, no scheme or port (pass port separately). heartbeat and server: leave empty.
- `tcp_expected_outcome`: connect (default: up when the port accepts) or fail (up when it refuses). tcp only.
- `tcp_ip_family`: ipv4 (default) or ipv6. tcp only.
- `tcp_payload`: Text to send after connecting. tcp only.
- `timeout_seconds`: Seconds to wait for a response, 1 to 60. Default 10.
- `verify_ssl`: Fail the check when the TLS certificate is invalid or expired. Default true.

### `delete_check` (~34 tokens)

Delete a check. Run only when the user asked to delete this check in this conversation.

Input parameters:

- `endpoint_id` (string, required)

### `run_check` (~60 tokens)

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.

Input parameters:

- `endpoint_id` (string, required)

### `list_status_pages` (~34 tokens)

Status pages in this workspace: slug, name, visibility, publicUrl, custom domain, and the worst open incident status.

Output parameters:

- `result` (array)

### `get_status_page` (~51 tokens)

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.

Input parameters:

- `slug` (string, required)

### `create_status_page` (~142 tokens)

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 a later step fails, the new page is deleted.

Input parameters:

- `custom_domain`
- `endpoint_ids`
- `name` (string, required)
- `password`
- `slug` (string, required)
- `url`
- `visibility`

### `update_status_page` (~113 tokens)

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.

Input parameters:

- `custom_domain`
- `name`
- `password`
- `show_auto_detected`
- `slug` (string, required)
- `url`
- `visibility`

### `delete_status_page` (~38 tokens)

Delete a status page and its components. Run only when the user asked to delete this page in this conversation.

Input parameters:

- `slug` (string, required)

### `verify_custom_domain` (~30 tokens)

Check the CNAME and TXT records for a status page custom domain.

Input parameters:

- `slug` (string, required)

### `create_component` (~49 tokens)

Add a component to an existing status page. Returns its id so update_check can link a check to it.

Input parameters:

- `name` (string, required)
- `slug` (string, required)
- `url`

### `update_component` (~41 tokens)

Rename a component or change its URL.

Input parameters:

- `component_id` (string, required)
- `name`
- `slug` (string, required)
- `url`

### `delete_component` (~41 tokens)

Delete a component. Run only when the user asked to delete this component in this conversation.

Input parameters:

- `component_id` (string, required)
- `slug` (string, required)

### `manage_component_group` (~73 tokens)

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.

Input parameters:

- `action` (string, required)
- `group_id`
- `name`
- `slug` (string, required)

### `slack_connection` (~66 tokens)

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.

Input parameters:

- `action` (string, required)
- `slug` (string, required)

### `page_alert_destinations` (~58 tokens)

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.

Input parameters:

- `destination_ids` (array, required)
- `slug` (string, required)

### `list_incident_proposals` (~43 tokens)

Drafts waiting for review from checks in incident_mode review, pending first. Approving one publishes it as a status incident.

Input parameters:

- `slug` (string, required)

### `approve_incident_proposal` (~92 tokens)

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.

Input parameters:

- `body`
- `impact`
- `proposal_id` (string, required)
- `slug` (string, required)
- `title`

### `dismiss_incident_proposal` (~37 tokens)

Dismiss a pending review draft. Nothing is published.

Input parameters:

- `proposal_id` (string, required)
- `slug` (string, required)

### `create_incident` (~132 tokens)

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.

Input parameters:

- `body` (string, required)
- `component_ids`
- `impact` (string, required)
- `opened_at`
- `resolved_at`
- `slug` (string, required)
- `status` (string, required)
- `title` (string, required)

### `get_incident` (~32 tokens)

One incident, including updates newest first.

Input parameters:

- `public_id` (string, required)
- `slug` (string, required)

### `update_incident` (~113 tokens)

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.

Input parameters:

- `body`
- `component_ids`
- `impact`
- `public_id` (string, required)
- `slug` (string, required)
- `status`
- `title`
- `update_body`
- `update_id`

### `post_incident_update` (~72 tokens)

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.

Input parameters:

- `body` (string, required)
- `public_id` (string, required)
- `slug` (string, required)
- `status` (string, required)

### `list_maintenance_windows` (~39 tokens)

Maintenance windows: id, name, starts_at, duration_seconds, timezone, recurrence, weekdays, ends_at, notify_subscribers, and items.

Output parameters:

- `result` (array)

### `create_maintenance_window` (~141 tokens)

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.

Input parameters:

- `duration_seconds` (integer, required)
- `endpoint_ids`
- `name` (string, required)
- `notify_subscribers`
- `starts_at` (string, required)
- `status_components`
- `timezone` (string, required)
- `weekdays`

### `update_maintenance_window` (~96 tokens)

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.

Input parameters:

- `duration_seconds`
- `endpoint_ids`
- `name`
- `notify_subscribers`
- `starts_at`
- `status_components`
- `timezone`
- `weekdays`
- `window_id` (string, required)

### `cancel_maintenance_window` (~56 tokens)

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.

Input parameters:

- `notify_subscribers`
- `window_id` (string, required)

### `list_alert_destinations` (~36 tokens)

Existing alert destinations: id, kind, name, and hint. Secrets are not returned. Creating a destination stays in the console.

Output parameters:

- `result` (array)

### `test_alert_destination` (~38 tokens)

Send a real test alert to an existing destination. Run only when the user asked to send the test.

Input parameters:

- `destination_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-quickstatus-quickstatus/api#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 79
- 2026-11-19: 78
- 2026-11-18: 78
- 2026-11-17: 77
- 2026-11-16: 77
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 75
- 2026-11-12: 75
- 2026-11-11: 74
- 2026-11-10: 74
- 2026-11-09: 73
- 2026-11-08: 73
- 2026-11-07: 73
- 2026-11-06: 72

## Common questions

### What is the QuickStatus MCP server?

QuickStatus is an MCP server listed in the public MCP registry as dev.quickstatus/quickstatus. Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP. This page covers its hosted endpoint (https://api.quickstatus.dev/mcp).

### Is the QuickStatus MCP server safe to use?

QuickStatus scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the QuickStatus MCP server expose?

QuickStatus exposes 34 tools: usage, list_regions, list_checks, get_check, get_check_results, and 29 more. Their descriptions and schemas cost roughly 4,857 tokens of context every time the server is loaded.

### Does the QuickStatus MCP server require authentication?

Yes. QuickStatus asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the QuickStatus MCP server still maintained?

QuickStatus is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the QuickStatus MCP server?

VerifyMCP ran 13 checks on QuickStatus, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.quickstatus.dev/mcp
- Authorisation metadata: https://api.quickstatus.dev/.well-known/oauth-protected-resource/mcp
- Website: https://quickstatus.dev/docs/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/dev-quickstatus-quickstatus/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-quickstatus-quickstatus/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-quickstatus-quickstatus/api.json
- HTML version of this page: https://verifymcp.io/servers/dev-quickstatus-quickstatus/api
