Skip to main content
Glama
Sign In
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
      A
      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.
      15
      78 npm
      MIT
    • uptrack-mcp by Uptrack-App

      uptrack-mcpofficial

      Uptrack-App
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents like Claude, ChatGPT, and Cursor.
      4 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
      25 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.
      19
      614 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

    A4/5.0

    Scored across 35 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear separation between get/list/summary variants for monitors, heartbeats, status pages, and maintenance. The descriptions explicitly guide agents away from common confusions, such as using getMonitorSummary for status overviews versus listMonitors for configuration.

    Naming Consistency4/5

    Mostly consistent camelCase verb_noun naming across resources. Minor deviations exist (addNotification vs createMonitor, getMaintenanceWindows vs listMaintenanceWindows) but remain predictable and readable.

    Tool Count3/5

    35 tools is heavy and may overwhelm agents compared with the typical 3-15 range. The breadth of Uptime Kuma administration (monitors, notifications, Docker hosts, tags, maintenance, status pages) justifies many tools, but the surface is still large enough to feel borderline.

    Completeness4/5

    Core CRUD coverage is strong for monitors, notifications, Docker hosts, maintenance windows, and status pages. Minor gaps remain, such as updateSettings, updateTag, and a notification-test operation, but most workflows are supported.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources