Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

QuickStatus

REMOTE · API.QUICKSTATUS.DEV

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

+3 this week 79 Trust /100

Last scanned (18 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability54
  • AI-judged instruction clarity (fair).Partial
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 45% of tool parameters carry a description.Partial
  • Structured output schemas are declared (18% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 35 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • The server changed its declared name: QuickStatus → QuickStatus.dev security
    • “create_check” reworded the description of “min_members” cosmetic
    • “update_check” reworded the description of “min_members” cosmetic
  • 18 Nov 26 +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.

  • 17 Nov 26 0
    • 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 security
    • Schema quality: 131 → 145 ▼ functional
    • “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” cosmetic
  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 13 Nov 26 0
    • 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 security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 0% → 42% ▲ functional
    • “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 cosmetic
  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.quickstatus.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.quickstatus.dev CN=Amazon RSA 2048 M04,O=Amazon,C=US 6 Nov 2026 22 May 2027 RSA 2048 SHA256-RSA a112220113a30f8e7fd433bd595de8a
SANs: api.quickstatus.dev, api.scaledpapers.com
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.quickstatus.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
quickstatus.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.quickstatus.dev/mcp Verified 200
http (plaintext) http://api.quickstatus.dev/mcp HTTPS enforced 301 https://api.quickstatus.dev:443/mcp
MCP tools · 34 exposed · ~4,857 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
approve_incident_proposal ~92

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.

NameTypeReqDescription
body–––
impact–––
proposal_idstringyes–
slugstringyes–
title–––

No output schema declared.

No examples provided.

cancel_maintenance_window ~56

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.

NameTypeReqDescription
notify_subscribers–––
window_idstringyes–

No output schema declared.

No examples provided.

create_check ~1,441

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.

NameTypeReqDescription
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…
kindstring–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).
namestringyesDisplay 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…
targetstring–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.

No output schema declared.

No examples provided.

create_component ~49

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

NameTypeReqDescription
namestringyes–
slugstringyes–
url–––

No output schema declared.

No examples provided.

create_incident ~132

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.

NameTypeReqDescription
bodystringyes–
component_ids–––
impactstringyes–
opened_at–––
resolved_at–––
slugstringyes–
statusstringyes–
titlestringyes–

No output schema declared.

No examples provided.

create_maintenance_window ~141

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.

NameTypeReqDescription
duration_secondsintegeryes–
endpoint_ids–––
namestringyes–
notify_subscribers–––
starts_atstringyes–
status_components–––
timezonestringyes–
weekdays–––

No output schema declared.

No examples provided.

create_status_page ~142

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.

NameTypeReqDescription
custom_domain–––
endpoint_ids–––
namestringyes–
password–––
slugstringyes–
url–––
visibility–––

No output schema declared.

No examples provided.

delete_check ~34

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

NameTypeReqDescription
endpoint_idstringyes–

No output schema declared.

No examples provided.

delete_component ~41

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

NameTypeReqDescription
component_idstringyes–
slugstringyes–

No output schema declared.

No examples provided.

delete_status_page ~38

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

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

dismiss_incident_proposal ~37

Dismiss a pending review draft. Nothing is published.

NameTypeReqDescription
proposal_idstringyes–
slugstringyes–

No output schema declared.

No examples provided.

get_check ~44

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

NameTypeReqDescription
endpoint_idstringyes–

No output schema declared.

No examples provided.

get_check_results ~201

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.

NameTypeReqDescription
endpoint_idstringyes–
hours–––
viewstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

get_incident ~32

One incident, including updates newest first.

NameTypeReqDescription
public_idstringyes–
slugstringyes–

No output schema declared.

No examples provided.

get_status_page ~51

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.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

list_alert_destinations ~36

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

list_checks ~34

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

list_incident_proposals ~43

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

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

list_maintenance_windows ~39

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

list_regions ~19

Enabled probe regions: id, name, and region.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

list_status_pages ~34

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

manage_component_group ~73

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.

NameTypeReqDescription
actionstringyes–
group_id–––
name–––
slugstringyes–

No output schema declared.

No examples provided.

page_alert_destinations ~58

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.

NameTypeReqDescription
destination_idsarrayyes–
slugstringyes–

No output schema declared.

No examples provided.

post_incident_update ~72

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.

NameTypeReqDescription
bodystringyes–
public_idstringyes–
slugstringyes–
statusstringyes–

No output schema declared.

No examples provided.

run_check ~60

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.

NameTypeReqDescription
endpoint_idstringyes–

No output schema declared.

No examples provided.

slack_connection ~66

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.

NameTypeReqDescription
actionstringyes–
slugstringyes–

No output schema declared.

No examples provided.

test_alert_destination ~38

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

NameTypeReqDescription
destination_idstringyes–

No output schema declared.

No examples provided.

update_check ~1,291

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.

NameTypeReqDescription
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_idstringyesCheck 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.

No output schema declared.

No examples provided.

update_component ~41

Rename a component or change its URL.

NameTypeReqDescription
component_idstringyes–
name–––
slugstringyes–
url–––

No output schema declared.

No examples provided.

update_incident ~113

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.

NameTypeReqDescription
body–––
component_ids–––
impact–––
public_idstringyes–
slugstringyes–
status–––
title–––
update_body–––
update_id–––

No output schema declared.

No examples provided.

update_maintenance_window ~96

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.

NameTypeReqDescription
duration_seconds–––
endpoint_ids–––
name–––
notify_subscribers–––
starts_at–––
status_components–––
timezone–––
weekdays–––
window_idstringyes–

No output schema declared.

No examples provided.

update_status_page ~113

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.

NameTypeReqDescription
custom_domain–––
name–––
password–––
show_auto_detected–––
slugstringyes–
url–––
visibility–––

No output schema declared.

No examples provided.

usage ~70

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

verify_custom_domain ~30

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

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

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.

remote · api.quickstatus.dev

# add to Claude Code
claude mcp add --transport http dev-quickstatus-quickstatus 'https://api.quickstatus.dev/mcp'
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.