Skip to main content
Glama

Related Servers

Alternatives to uptybots-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Uptime monitoring your AI agent can set up: create HTTP, SSL, ping, TCP and DNS monitors checked from multiple regions, run checks on demand, read and acknowledge incidents, manage cron heartbeats, maintenance windows and status page updates.
      49
      229 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Website monitoring for AI assistants. Visual Sentinel catches pages that look broken even when the site is up. DNS, SSL, speed and website checks need no account; monitors, incidents and alerts need an API key (Business and Agency plans).
      16
      236 npm
      1
      MIT
    • 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.
      4 npm
      2
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Uptime monitoring from your AI agent: create and diagnose checks (40 types: HTTP, TCP, DNS, SSL, ICMP, databases, message queues and more), read results and incidents, and manage status pages and maintenance windows. Built into the self-hostable SolidPing server, served over streamable HTTP at /api/v1/mcp.
      23
      22
      AGPL 3.0

    TDQS

    A4.5/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: listing, reading, creating various monitor types (HTTP, API, ping, port, SSL, domain), pausing/resuming, deleting, and querying incidents/stats/notifications. No two tools overlap in purpose; the create_* variants are clearly differentiated by check type.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern: list_, get_, create_<type>_monitor, pause_, resume_, delete_, get_incidents, get_stats_hourly/daily, get_notifications. The pattern is predictable and aids agent selection.

    Tool Count5/5

    15 tools is within the ideal 3-15 range and matches the domain's needs: comprehensive monitoring coverage without redundancy. Each tool serves a distinct purpose in the uptime monitoring workflow.

    Completeness4/5

    The set covers the full monitoring lifecycle: create (six types), read, pause/resume, delete, incidents, stats, and notifications. The only minor gap is the lack of an explicit update/edit tool for existing monitors, but most configuration changes would be done via create/delete, and the current set handles core workflows effectively.

    Maintenance

    ActivityStale
    ResponsivenessNo issues