QuickStatus

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

• Conexión: Se ejecuta en la nube
• Transporte: Streamable HTTP
• Categoría: Web y navegadores
• Debes completar: Authorization

Instalación

Elige la app de IA que usas y copia la configuración.

Necesitas

• Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet

¿Qué app usas?

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

{
  "mcpServers": {
    "quickstatus": {
      "url": "https://api.quickstatus.dev/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "quickstatus": {
      "type": "http",
      "url": "https://api.quickstatus.dev/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

• Authorization secreto obligatorio HTTP header
  Bearer followed by your sp_ API key from the QuickStatus console (API Keys).

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 7 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

• usage

  Plan caps for this workspace: plan, period, probe_count, monthly_probe_quota, endpoints_used, max_endpoints, max_regions, min_interval_seconds, sample_retention_days, max_status_pages. Call this before creating anything. Stop when a cap is reached.

• list_regions

  Enabled probe regions: id, name, and region.

• list_checks

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

• get_check

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

• get_check_results

  Check results. view is status, history, or outages. history uses hours (default 24) and returns status, status_code, latency_ms, dns_ms, connect_ms, location_name, location_region, and observed_at. Sample metadata is omitted.

• create_check

  Create a check. kind is http, api, dns, or tcp. Defaults: GET, status 200, 10s timeout, email alerts on, interval_seconds from the plan minimum, and one region. DNS defaults to an A record over UDP. TCP requires port. Pass regions only when you want more than the default, and onl

• update_check

  Update a check. Pass only the fields to change. enabled false pauses and true resumes. Linking requires site_id, site_slug, and component_id together, plus optional incident_mode (off, auto, or review: review stores a draft a person approves before it is published), incident_auto

• delete_check

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

• run_check

  Queue a probe for one check from each of its live regions (the same regions a scheduled run uses). Returns job_id and regions. Call get_check_results with view status for the result; it is not included here.

• list_status_pages

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

• get_status_page

  One status page: components with ids, groups, incidents with public ids, Slack connection state, and alert-destination ids. has_password is returned; the password is not.

• create_status_page

  Create a public status page. visibility internal requires Pro and a password of at least 8 characters that the user typed; never invent a password or repeat it. custom_domain is a hostname such as status.acme.com and requires Pro. With endpoint_ids, each check becomes a component

• update_status_page

  Update a status page. Fields: name, url, visibility, password, custom_domain, show_auto_detected (label incidents a check opened itself as detected automatically). custom_domain null removes it. visibility internal needs a password of at least 8 characters that the user typed. Ne

• delete_status_page

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

• verify_custom_domain

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

• create_component

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

• update_component

  Rename a component or change its URL.

• delete_component

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

• manage_component_group

  Create, update, or delete a component group. action is create, update, or delete. create and update need name. update and delete need group_id. Delete only when the user asked.

• slack_connection

  Slack connection for a status page. action start returns a URL for the user to open; do not complete OAuth. action disconnect removes the connection. Disconnect only when the user asked. Connection state is on get_status_page.

• page_alert_destinations

  Replace the alert destinations attached to a status page with these existing destination ids. Use list_alert_destinations for the ids. An empty list detaches all of them.

• list_incident_proposals

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

• approve_incident_proposal

  Publish a pending review draft as a status incident. This emails subscribers and posts to Slack. Run only when the user asked to publish it in this conversation. Optional title, body, and impact (minor, major, or critical) replace the draft text.

• dismiss_incident_proposal

  Dismiss a pending review draft. Nothing is published.

• create_incident

  Open an incident. This emails subscribers and posts to Slack the same way the console does. Run only when the user asked to publish this incident in this conversation. status is investigating, identified, monitoring, or resolved. impact is minor, major, or critical. component_ids

• get_incident

  One incident, including updates newest first.

• update_incident

  Edit an incident's title or impact. Run only when the user asked. With update_id and update_body, rewrite that posted update's message (no new notification). To change status, post a message, or resolve, use post_incident_update instead.

• post_incident_update

  Post an incident update. This emails subscribers and posts to Slack. Run only when the user asked to publish this update in this conversation. status resolved closes the incident.

• list_maintenance_windows

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

• create_maintenance_window

  Schedule a maintenance window. duration_seconds is 60 through 7 days. Pass both the check (endpoint_ids) and its public component (status_components) so probes pause and the page shows Under maintenance. notify_subscribers defaults to false. Set it true only when the user asked t

• update_maintenance_window

  Update a maintenance window. notify_subscribers defaults to false unless you set it. This can email subscribers. Run only when the user asked to change this window.

• cancel_maintenance_window

  Cancel a maintenance window. notify_subscribers defaults to false. This can email subscribers. Run only when the user asked to cancel this window in this conversation.

• list_alert_destinations

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

• test_alert_destination

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

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026

• ! Precaución

  El creador coincide con el repo

  El registro no indica ningún repo de código fuente, así que no podemos relacionar a quien lo publicó (quickstatus.dev) con el código

• … Aún sin revisar

  Sigue en mantenimiento

  Todavía no hemos leído este repo en GitHub

• … Aún sin revisar

  Tiene licencia

  Todavía no hemos leído este repo en GitHub

• ✓ Superada

  El endpoint responde

  Respondió en 228 ms (HTTP 200)

• – No aplica

  Inicio de sesión con OAuth

  No hace falta iniciar sesión

• ✓ Superada

  Sin instrucciones ocultas en las descripciones de herramientas

  Leímos 34 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Comparado con otros en Web y navegadoresi

• Más estrellas que el 0% de los otros 1378 servidores de esta categoría
• Publicado en el registro más recientemente que el 97% de los otros 1378 servidores de esta categoría
• Revisiones básicas iguales o mejores que el 43% de los otros 1378 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

README del creador

No se encontró un README en el repo