Skip to main content
Glama
84emllc

UptimeRobot MCP Server

by 84emllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to UptimeRobot MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-uptime-kuma

      DavidFuchs
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Uptime Kuma that enables monitoring and management of uptime monitors, heartbeats, notifications, tags, and maintenance windows via natural language.
      31
      310 npm
      54
      MIT

    • 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

    • Vigilo

      temmeik
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients such as Claude to check current uptime status, inspect monitors and incidents, trigger fresh checks, and retrieve status summaries from a self-hosted monitoring service.
      6 npm
      2
      MIT

    • thruk-mcp

      k9fr4n
      A
      license
      C
      quality
      B
      maintenance
      Enables natural language interaction with Thruk monitoring systems, allowing users to query hosts/services, schedule downtimes, acknowledge problems, and more via MCP-compatible clients.
      65
      2
      MIT

    • uptime-kuma-mcp-server

      mehbul
      A
      license
      A
      quality
      B
      maintenance
      Enables managing Uptime Kuma monitoring through natural language, including creating, editing, pausing, and deleting monitors, plus retrieving heartbeats, status, metrics, notifications, and status pages.
      12
      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

    A3.6/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool maps to a distinct resource and action, such as monitors, alert contacts, and maintenance windows. The separation between list, get, create, edit, delete, and specialized operations like reset or logs is clear.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern, using plural nouns for list operations and singular nouns for single-item operations. The naming is uniform across all three resource types.

    Tool Count4/5

    At 16 tools, the set is slightly above the ideal 3-15 range but still well-scoped for the domain. Each tool addresses a meaningful operation, and the count feels justified rather than bloated.

    Completeness4/5

    The tool surface covers full CRUD for monitors, alert contacts, and maintenance windows, plus useful extras like monitor logs and account details. Minor gaps exist (e.g., single alert contact retrieval, monitor pause/resume), but core workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources