Skip to content

QuickStatus MCP server

dev.quickstatus/quickstatusquickstatus.devstreamable-httpv1.1.0Scanned

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

34 tools: 12 can delete or cancel things, 1 do something that can't be undone, 11 change things and 10 only read.

Tools: 12 delete, 1 irreversible, 11 write, 10 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 6
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

12 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the QuickStatus MCP server can do

The QuickStatus MCP server is published by quickstatus.dev, a domain the MCP Registry verified. It has 34 tools. It can delete or cancel things (12 tools: delete_check, delete_status_page, delete_component, manage_component_group and 8 more), do things that cannot be undone, such as sending, paying or publishing (test_alert_destination) and create or change data (11 tools: usage, create_check, update_check, run_check and 7 more). 10 tools only read.

2 tools bring in text other people can write (list_status_pages and list_incident_proposals); 6 tools can send data out of your system (create_status_page, update_status_page, create_component and 3 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

34 tools

Deletes or cancels 12Claude Code: deny
  • approve_incident_proposalPublish a pending review draft as a status incident.No findings

    Why it is in this group

    • The name "approve_incident_proposal" says "approve": a word for a change.
    • The description's first verb is "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • readOnlyHint: false
  • cancel_maintenance_windowCancel a maintenance window.No findings

    Why it is in this group

    • The name "cancel_maintenance_window" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • readOnlyHint: false
  • create_incidentOpen an incident.No findings

    Why it is in this group

    • The name "create_incident" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • readOnlyHint: false
  • create_maintenance_windowSchedule a maintenance window.No findings

    Why it is in this group

    • The name "create_maintenance_window" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • readOnlyHint: false
  • delete_checkDelete a check.No findings

    Why it is in this group

    • The name "delete_check" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a check. Run only when the user asked to delete this check in this conversation.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • readOnlyHint: false
  • delete_componentDelete a component.No findings

    Why it is in this group

    • The name "delete_component" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a component. Run only when the user asked to delete this component in this conversation.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • readOnlyHint: false
  • delete_status_pageDelete a status page and its components.No findings

    Why it is in this group

    • The name "delete_status_page" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a status page and its components. Run only when the user asked to delete this page in this conversation.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • readOnlyHint: false
  • manage_component_groupCreate, update, or delete a component group.No findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • readOnlyHint: false
  • post_incident_updatePost an incident update.Can send data outNo findings

    Why it is in this group

    • The name "post_incident_update" says "post": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "post_incident_update" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • readOnlyHint: false
  • slack_connectionSlack connection for a status page.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • readOnlyHint: false
  • update_incidentEdit an incident's title or impact.No findings

    Why it is in this group

    • The name "update_incident" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • readOnlyHint: false
  • update_maintenance_windowUpdate a maintenance window.No findings

    Why it is in this group

    • The name "update_maintenance_window" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • readOnlyHint: false
Can't be undone 1Claude Code: ask
  • test_alert_destinationSend a real test alert to an existing destination.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe description's first verb is "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Send a real test alert to an existing destination. Run only when the user asked to send the test.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • readOnlyHint: false
Changes things 11Claude Code: ask
  • create_checkCreate a check.No findings

    Why it is in this group

    • The name "create_check" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • readOnlyHint: false
  • create_componentAdd a component to an existing status page.Can send data outNo findings

    Why it is in this group

    • The name "create_component" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Add a component to an existing status page. Returns its id so update_check can link a check to it.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • readOnlyHint: false
  • create_status_pageCreate a public status page.Can send data outNo findings

    Why it is in this group

    • The name "create_status_page" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • readOnlyHint: false
  • dismiss_incident_proposalDismiss a pending review draft.No findings

    Why it is in this group

    • The name "dismiss_incident_proposal" says "dismiss": a word for a change.
    Description, as the server wrote it
    Dismiss a pending review draft. Nothing is published.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: false
  • page_alert_destinationsReplace the alert destinations attached to a status page with these existing destination ids.No findings

    Why it is in this group

    • The description's first verb is "replace": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: false
  • run_checkQueue a probe for one check from each of its live regions (the same regions a scheduled run uses).No findings

    Why it is in this group

    • The name "run_check" says "run": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • readOnlyHint: false
  • update_checkUpdate a check.No findings

    Why it is in this group

    • The name "update_check" says "update": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: false
  • update_componentRename a component or change its URL.Can send data outNo findings

    Why it is in this group

    • The name "update_component" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Rename a component or change its URL.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: false
  • update_status_pageUpdate a status page.Can send data outNo findings

    Why it is in this group

    • The name "update_status_page" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: false
  • usagePlan 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_pa…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: true
  • verify_custom_domainCheck the CNAME and TXT records for a status page custom domain.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check the CNAME and TXT records for a status page custom domain.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • readOnlyHint: false
Only reads 10Show 10 read-only tools
  • get_checkOne check, including assertion, DNS, and TCP fields.No findings

    Why it is in this group

    • The name "get_check" says "get": a word for reading.
    Description, as the server wrote it
    One check, including assertion, DNS, and TCP fields. Secrets such as request headers, request body, and HTTP auth are not returned.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: true
  • get_check_resultsCheck results.No findings

    Why it is in this group

    • The name "get_check_results" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: true
  • get_incidentOne incident, including updates newest first.No findings

    Why it is in this group

    • The name "get_incident" says "get": a word for reading.
    Description, as the server wrote it
    One incident, including updates newest first.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: true
  • get_status_pageOne status page: components with ids, groups, incidents with public ids, Slack connection state, and alert-destination ids.No findings

    Why it is in this group

    • The name "get_status_page" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: true
  • list_alert_destinationsExisting alert destinations: id, kind, name, and hint.No findings

    Why it is in this group

    • The name "list_alert_destinations" says "list": a word for reading.
    Description, as the server wrote it
    Existing alert destinations: id, kind, name, and hint. Secrets are not returned. Creating a destination stays in the console.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: true
  • list_checksChecks in this workspace.No findings

    Why it is in this group

    • The name "list_checks" says "list": a word for reading.
    Description, as the server wrote it
    Checks in this workspace. Use this before create_check so you do not add a second check for a URL that is already watched.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: true
  • list_incident_proposalsDrafts waiting for review from checks in incident_mode review, pending first.Reads text others writeNo findings

    Why it is in this group

    • The name "list_incident_proposals" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
    Description, as the server wrote it
    Drafts waiting for review from checks in incident_mode review, pending first. Approving one publishes it as a status incident.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: true
  • list_maintenance_windowsMaintenance windows: id, name, starts_at, duration_seconds, timezone, recurrence, weekdays, ends_at, notify_subscribers, and items.No findings

    Why it is in this group

    • The name "list_maintenance_windows" says "list": a word for reading.
    Description, as the server wrote it
    Maintenance windows: id, name, starts_at, duration_seconds, timezone, recurrence, weekdays, ends_at, notify_subscribers, and items.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: true
  • list_regionsEnabled probe regions: id, name, and region.No findings

    Why it is in this group

    • The name "list_regions" says "list": a word for reading.
    Description, as the server wrote it
    Enabled probe regions: id, name, and region.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: true
  • list_status_pagesStatus pages in this workspace: slug, name, visibility, publicUrl, custom domain, and the worst open incident status.Reads text others writeNo findings

    Why it is in this group

    • The name "list_status_pages" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "status" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Status pages in this workspace: slug, name, visibility, publicUrl, custom domain, and the worst open incident status.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out6
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:22 UTC, unchanged since Nov 7, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
24
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 24 tools that change things (12 destructive, 1 irreversible, 11 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.quickstatus.dev/mcp: tools/list returned 34 tools to an anonymous client, including delete_check (destructive), delete_status_page (destructive), delete_component (destructive), manage_component_group (destructive), slack_connection (destructive) and 19 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools4 changed.~4 changedView diff

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http quickstatus https://api.quickstatus.dev/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http quickstatus https://api.quickstatus.dev/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__quickstatus__list_regions",
      "mcp__quickstatus__list_checks",
      "mcp__quickstatus__get_check",
      "mcp__quickstatus__get_check_results",
      "mcp__quickstatus__list_status_pages",
      "mcp__quickstatus__get_status_page",
      "mcp__quickstatus__list_incident_proposals",
      "mcp__quickstatus__get_incident",
      "mcp__quickstatus__list_maintenance_windows",
      "mcp__quickstatus__list_alert_destinations"
    ],
    "ask": [
      "mcp__quickstatus__usage",
      "mcp__quickstatus__create_check",
      "mcp__quickstatus__update_check",
      "mcp__quickstatus__run_check",
      "mcp__quickstatus__create_status_page",
      "mcp__quickstatus__update_status_page",
      "mcp__quickstatus__verify_custom_domain",
      "mcp__quickstatus__create_component",
      "mcp__quickstatus__update_component",
      "mcp__quickstatus__page_alert_destinations",
      "mcp__quickstatus__dismiss_incident_proposal",
      "mcp__quickstatus__test_alert_destination"
    ],
    "deny": [
      "mcp__quickstatus__delete_check",
      "mcp__quickstatus__delete_status_page",
      "mcp__quickstatus__delete_component",
      "mcp__quickstatus__manage_component_group",
      "mcp__quickstatus__slack_connection",
      "mcp__quickstatus__approve_incident_proposal",
      "mcp__quickstatus__create_incident",
      "mcp__quickstatus__update_incident",
      "mcp__quickstatus__post_incident_update",
      "mcp__quickstatus__create_maintenance_window",
      "mcp__quickstatus__update_maintenance_window",
      "mcp__quickstatus__cancel_maintenance_window"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as quickstatus. Review it before you use it.

Capability tags behind 8 rules
  • mcp__quickstatus__list_status_pages untrusted-input
  • mcp__quickstatus__create_status_page outbound
  • mcp__quickstatus__update_status_page outbound
  • mcp__quickstatus__create_component outbound
  • mcp__quickstatus__update_component outbound
  • mcp__quickstatus__list_incident_proposals untrusted-input
  • mcp__quickstatus__post_incident_update outbound
  • mcp__quickstatus__test_alert_destination outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.quickstatus/quickstatus/verify?hash=4ed60219ffec31b25906a0d8a995af645d4dd5633b7db11017b41370c1f412dc" | jq -e '.changed == false'

Pinned hash 4ed60219ffec, from Nov 20, 2026, 22:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.quickstatus/quickstatus/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.quickstatus/quickstatus
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.quickstatus/quickstatus.svg)](https://radar.anlyon.com/servers/dev.quickstatus/quickstatus)

Source: MCP Registry. Synced Nov 6, 2026, 20:17 UTC.

QuickStatus MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the QuickStatus MCP server safe?

No scan can promise that. What its definitions show: 34 tools, 24 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the QuickStatus MCP server delete data?

Yes. 12 tools can delete, cancel or revoke something: delete_check, delete_status_page, delete_component, manage_component_group, slack_connection, approve_incident_proposal and 6 more.

Can the QuickStatus MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: test_alert_destination.

What tools does the QuickStatus MCP server have?

34 tools: 12 destructive, 1 irreversible, 11 write, 10 read. delete_check, delete_status_page, delete_component, manage_component_group, slack_connection, approve_incident_proposal, create_incident, update_incident and 26 more.

Does the QuickStatus MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the QuickStatus MCP server send data to outside services?

6 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_status_page, update_status_page, create_component, update_component, post_incident_update and test_alert_destination.

Has the QuickStatus MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.