Skip to main content
Glama
810,608 tools. Updated 2026-11-20 06:24

"Instatus" matching MCP tools:

  • Retrieve the Instatus user profile linked to your API key, including ID, name, and email. Use it to identify the authenticated account for status page operations.
    MIT
  • Return the TypeScript-style contract of one Instatus REST operation: path parameters, query parameters, request body and response, ready to pass to instatus_read_api or instatus_write_api. Read-only.
    ConnectorOAuth
  • Call one GET operation of the Instatus REST API that no dedicated tool covers (metrics, templates, monitors, on-call…). Read-only: it never changes Instatus data. Get the operation id from instatus_search_api and its parameters from instatus_describe_api first.
    ConnectorOAuth
  • Check a service's public status page to determine if it is up, degraded, or in outage, and see open incidents and scheduled maintenance.
    MIT

Matching MCP Connectors

  • Status pages, incidents, maintenance, components and subscribers on Instatus.

  • Manage status pages: components, incidents and maintenances; set live component status.

  • Find a SaaS/cloud vendor by name, slug, or status-page domain and get its status page URL, platform, feed availability, and latest poll state. Use when the exact slug is unknown.
    MIT
  • Permanently removes an incident and its history from a status page. This action is irreversible, so confirm before deletion.
    MIT
    Destructive
  • Announce a planned maintenance window on an Instatus status page, with optional auto-start and auto-end so affected components show UNDERMAINTENANCE during the window.
    MIT
  • Retrieve a component's description, status, group, and uptime settings from a status page using its page and component IDs. Use to check component health and configuration.
    MIT
  • Retrieve an incident's full update timeline and affected components. Use this to review incident details on a status page.
    MIT
  • Retrieve incidents from a status page, newest first, including updates and affected components. Filter by status to see open incidents or exclude resolved ones.
    MIT
  • List incidents on one status page, newest first. Read-only. By default returns only unresolved incidents; set include_resolved to see history, and since to limit it to a period such as this month. When next_cursor is not null there are more: pass it back as cursor. Each item carries the exact incident id, title, status, public URL, start and resolve times, duration_minutes once resolved, ongoing_minutes while open, impact and the latest update. For the full update timeline of one incident use instatus_get_incident.
    ConnectorOAuth
  • Reschedule or reword a maintenance that has not finished: change its title, times, affected components or the text of its first message. The change is public immediately and subscribers are not notified. Times keep the same length unless both are sent. To post a new progress message use instatus_add_maintenance_update.
    Connector
    Destructive
    OAuth
  • Change the displayed status of one or more components directly, without creating an incident or posting any message. The new status is public immediately and subscribers are not notified. For customer-facing communication open an incident with instatus_create_incident, or for planned work schedule one with instatus_schedule_maintenance. Check open incidents first: this overwrites what they show. Components change one at a time, so a failure part way leaves the earlier ones changed: components lists those, failed says whether that one changed, and not_attempted lists the rest. Returns previous_status for each, and still_covered_by lists any open incident or running maintenance that says otherwise, which stay public until they are resolved or completed.
    ConnectorOAuth