Skip to main content
Glama
Sign In
OpenUptime

OpenUptime

by becoolme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to OpenUptime

No user-submitted related servers found.

    Related Servers

    • Hyperping

      Hyperpingofficial

      hyperping
      A
      license
      Not graded
      quality
      D
      maintenance
      Official Hyperping MCP server for uptime, API, cron and server monitoring. 26 tools covering monitors, outages and timelines, uptime, response time, MTTR and MTTA, on-call schedules and escalation policies, over a remote Streamable HTTP endpoint with Bearer token auth and no install.
      1
      MIT
    • uptrack-mcp

      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.
      13 npm
      MIT

    • health-monitor-mcp

      oaslananka
      A
      license
      A
      quality
      F
      maintenance
      MCP server for monitoring health of MCP servers, GitHub Actions, GitLab pipelines, and HTTP endpoints with health history, TLS expiry, assertions, diagnostics, and alerts.
      22
      141 npm
      2
      MIT
    • uptimepage

      uptimepageofficial

      uptimepage
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Uptimepage uptime monitoring. An LLM client can read your monitors and incidents, run a check on demand, and post incident updates. Writes need an OAuth login and a scoped token, and each one is logged.
      54
      AGPL 3.0
    • EZO Watcher

      EZO Watcherofficial

      ezolabs
      A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted monitoring that your coding agent sets up and runs over MCP: it adds checks from the repo, proves each one can fail, then reads incidents and closes them with a recheck once the fix ships. One Node process plus SQLite, no account. MIT licensed.
      324 npm
      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

    A4.2/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools have clearly separated purposes, especially monitor lifecycle, incident lifecycle, and public vs private status-page reads. A few boundaries could still be confused, such as update_incident versus post_incident_update, or list_incidents versus list_public_status_page_incidents, but descriptions explicitly clarify them.

    Naming Consistency5/5

    Names are consistently snake_case and generally follow a verb_noun pattern: list_monitors, get_monitor, create_monitor, update_monitor, pause_monitor, resume_monitor, delete_monitor. Public and private variants are named predictably, with no mixed casing or chaotic verb styles.

    Tool Count3/5

    The domain is broad—workspaces, projects, monitors, incidents, status pages, maintenance, channels, and regions—so many operations are justified. However, 26 tools is heavy and includes several public/private read variants, making the surface borderline overgrown.

    Completeness3/5

    Core monitor and incident workflows are well covered, but several resources are only partially managed: maintenance windows and alert channels are list-only, and projects/workspaces/status pages lack full CRUD. These gaps are notable because agents cannot schedule maintenance or configure channels through this MCP server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources