Skip to main content
Glama
DavidFuchs

mcp-uptime-kuma

by DavidFuchs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-uptime-kuma

No user-submitted related servers found.

    Related Servers

    • exit1-mcp

      Mopra
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Exit1 uptime monitoring. Enables AI assistants to create and manage uptime checks, configure alerts, and query status via natural language.
      41 npm
      MIT
    • uptrack-mcp by Uptrack-App

      uptrack-mcpofficial

      Uptrack-App
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents like Claude, ChatGPT, and Cursor.
      5 npm
      MIT

    • stillonline-mcp

      shenwell
      A
      license
      A
      quality
      D
      maintenance
      MCP server for StillOnline uptime monitoring, enabling management of projects, checks, incidents, and public status pages through natural language.
      10
      26 npm
      1
      MIT
    • Drumbeats MCP by drumbeats-io

      Drumbeats MCPofficial

      drumbeats-io
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Drumbeats monitoring. Enables creating monitors, triaging incidents, and running HTTP/SSL/DNS checks using natural language from any AI client.
      16
      13 npm
      2
      Apache 2.0
    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

    A3.9/5.0

    Scored across 31 tools

    Disambiguation5/5

    Each tool maps clearly to a distinct resource and action, with descriptions explicitly separating status queries from configuration queries (getMonitorSummary vs listMonitors) and individual vs all-resource heartbeat reads (getHeartbeats vs listHeartbeats). Even similarly named tools have non-overlapping purposes.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern such as getMonitor, updateMonitor, listDockerHosts, and deleteStatusPage. However, creation verbs are split between create (createMonitor, createMaintenance, createStatusPage) and add (addNotification, addDockerHost, addTag), which is a minor but noticeable inconsistency.

    Tool Count2/5

    With 31 tools, this server exceeds the 25+ threshold and presents a large surface for agents to navigate. Each tool is individually justified by Uptime Kuma's resource model, but the overall count feels heavy for a single MCP server.

    Completeness3/5

    The core monitor, notification, docker host, and status page lifecycles are well covered, including create/read/update/delete where appropriate. However, maintenance windows can only be created and listed, not updated or deleted, and tags lack an update operation, leaving notable lifecycle gaps.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources