Skip to main content
Glama
weiseer

status-aggregator-mcp

by weiseer

Related Servers

Alternatives to status-aggregator-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that answers service status and uptime questions by reading Atlassian Statuspage feeds from hundreds of vendors, with keyless access and tools for checking status, incidents, and vendor listings.
      211 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query and monitor service status, latency, and performance through configurable checks (HTTP, TCP, SSL, keyword, JSON-path) and exposes tools for listing services, retrieving metrics, and running on-demand checks.
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Uptime monitoring from your AI agent: create and diagnose checks (40 types: HTTP, TCP, DNS, SSL, ICMP, databases, message queues and more), read results and incidents, and manage status pages and maintenance windows. Built into the self-hostable SolidPing server, served over streamable HTTP at /api/v1/mcp.
      42
      12
      AGPL 3.0
    • 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

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing services, getting detailed status, fetching incidents, and aggregate summary. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_services, get_status, get_incidents_today, check_all). The pattern is uniform and predictable.

    Tool Count5/5

    With 4 tools, the surface is well-scoped for a status aggregator. Each tool covers a necessary operation without redundancy.

    Completeness4/5

    Core operations are present: listing, detail, incidents, and summary. Missing historical incident queries or subscription capabilities, but reasonable for a basic aggregator.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues