Skip to main content
Glama
reshadat

outage-mcp

by reshadat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to outage-mcp

No user-submitted related servers found.

    Related Servers

    • API Status Check MCP Server

      shibley
      A
      license
      C
      quality
      B
      maintenance
      Monitor the real-time status of 200+ popular APIs and services. Check if services like GitHub, Stripe, AWS, and Slack are experiencing outages or degraded performance directly from your AI assistant.
      5
      8 npm
      1
      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

    • StatusCraft

      jabbawocky
      A
      license
      A
      quality
      C
      maintenance
      Live operational status for 2,400+ major software services — AWS, GitHub, Stripe, OpenAI, Cloudflare, and more — pulled from each provider's official status page and returned as a normalised up / degraded / down result for any service you ask about.
      5
      1
      MIT

    • downdetector-mcp

      domdomegg
      A
      license
      A
      quality
      B
      maintenance
      This server enables checking real-time service status and outage information from Downdetector for various services and regions.
      1
      44 npm
      2
      MIT

    • vendor-status

      APVentureEngine
      A
      license
      A
      quality
      B
      maintenance
      Enables querying the current state, incident history, resolution times, and feed URLs for over 1,100 SaaS/cloud vendor status pages.
      7
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct query: check_service for a specific service's history, get_incident for incident details, list_services for the service catalog, and whats_down for current active outages. There is no confusion.

    Naming Consistency3/5

    Three tools follow verb_noun pattern (check_service, get_incident, list_services), but 'whats_down' breaks the pattern with informal phrasing and no underscore.

    Tool Count5/5

    4 tools is well-scoped for an outage monitoring server, covering the essential operations without unnecessary bloat.

    Completeness4/5

    The server covers the main use cases: listing services, checking specific history, current outages, and incident details. However, it lacks a global incident list or ability to search incidents across services, which is a minor gap.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources