Skip to main content
Glama
OfirOhan

Instatus MCP Server

by OfirOhan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Instatus MCP Server

No user-submitted related servers found.

    Related Servers

    • ops-mcp

      Sydney-Robotics-Academy
      A
      license
      B
      quality
      D
      maintenance
      Enables unified management of maintenance windows and incidents across Atlassian Statuspage and Uptime Kuma. It allows AI assistants to schedule maintenance, update service statuses, and list monitors through a single MCP-compatible interface.
      9
      MIT

    • APIzone

      HappyMealSteak
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to check real-time status, uptime, and incidents for 200+ popular APIs (Stripe, OpenAI, AWS, GitHub, Twilio, etc.) through read-only, no-authentication tools.
      MIT
    • Statuser MCP Server by statuser-cloud

      Statuser MCP Serverofficial

      statuser-cloud
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to manage a Statuser account directly, including monitoring servers, handling incidents, publishing status page updates, and configuring notifications.
      87
      168 npm
      24
      MIT

    • prismix-status-mcp

      Prismor
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables checking real-time operational status of 75+ AI services (OpenAI, Anthropic, Cursor, etc.) through tools like check_ai_status and list_ai_services.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: user/page/component/incident/maintenance operations are separated by resource and action. The main mild ambiguity is between post_incident_update and resolve_incident, since both can update incident wording/status, but resolve_incident's one-step RESOLVED + component-reset behavior makes it distinguishable.

    Naming Consistency5/5

    All tool names are snake_case and consistently lead with a verb: get_, list_, set_, create_, post_, resolve_, delete_, schedule_. The pattern is predictable across every tool, with no mixing of conventions.

    Tool Count5/5

    14 tools is well-scoped for a status-page operations server. The set covers user context, page viewing, component status, incident lifecycle, and maintenance without obvious bloat.

    Completeness4/5

    Incident lifecycle coverage is strong: list/get/create/update/resolve/delete. Component and maintenance surfaces are thinner (no create/update/delete component, no update/cancel maintenance), but the core public status-page workflows are covered and these gaps are likely administrative or out of scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources