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.
      22 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.
      10 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
      35 npm
      1
      MIT
    • Drumbeats MCP by drumbeats-io

      Drumbeats MCPofficial

      drumbeats-io
      A
      license
      A
      quality
      B
      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
      28 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 targets a clearly distinct resource and action: monitor config (getMonitor/listMonitors), status overview (getMonitorSummary), per-monitor history (getHeartbeats), and all-monitor history (listHeartbeats) are explicitly differentiated in descriptions. Notification, docker host, tag, maintenance, and status page tools likewise map cleanly to separate resources.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun camelCase pattern (listMonitors, createMonitor, deleteMonitor, getMonitorSummary). There are minor deviations in verb choice (addTag/addDockerHost/addNotification vs createMonitor/createStatusPage/createMaintenance) and plural/singular inconsistency (getMaintenanceWindows vs getStatusPage, listTags vs listMonitors).

    Tool Count3/5

    With 31 tools, the set is on the heavy side, which is borderline per the rubric. However, the breadth is justified by the server covering several distinct resource families (monitors, heartbeats, notifications, docker hosts, tags, maintenance, status pages, settings), so most tools earn their place.

    Completeness3/5

    Most resource families have solid CRUD coverage (monitors, notifications, docker hosts, status pages are complete; heartbeats and monitor types are read-only by design). Notable gaps exist: maintenance windows support only list/create with no update or delete, settings are read-only, and tags lack an update operation.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources