Skip to main content
Glama
UptimeScout MCP server

UptimeScout MCP server

Official
by jsonscraper

Related Servers

Alternatives to UptimeScout MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables agents to retrieve structured, pre-published readings of the current geopolitical-risk picture, with in-band freshness and staleness metadata, through a no-auth read-only endpoint.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-speaking agents to query read-only summaries, failures, and dashboard cards covering machine health, services, routines, websites, Git activity, and custom JSON metrics.
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables MCP-capable clients to query verified physical context through location sensing, operability checks, and domain listing, while preserving evidence provenance and explicitly reporting unavailable inputs.
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Read-only MCP server that exposes governed operational records with provenance and validity windows so clients can check which evidence is still current before answering. It lets agents reconcile freshness, schedule state, and evidence specificity to determine whether scheduled automations are actually healthy, rather than trusting an expired dashboard summary.
      4
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query a locally cached, read-only view of a personal Zalo account, including connection status, conversations, bounded message history, cached text search, incremental events, and coverage, without sending, deleting, reacting, or marking messages read.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables querying the current state, incident history, resolution times, and feed URLs for over 1,100 SaaS/cloud vendor status pages.
      7
      MIT

    TDQS

    B3.1/5.0

    Scored across 7 tools

    Disambiguation4/5

    The tools are mostly distinct: single status vs. batch status, catalog search, history, stats, summary, and incidents have different targeting. Some overlap remains between services/status and summary/stats because they all expose availability-related views, though the descriptions provide enough distinction.

    Naming Consistency4/5

    All tool names share the same uptimescout_ prefix and use lowercase snake_case, which is predictable. The names are noun-based rather than action-based, and status/statuses are close but still intentionally distinguishable.

    Tool Count5/5

    Seven tools is a well-scoped size for a read-only observability server covering catalog lookup, status retrieval, history, stats, summaries, and incidents. Each tool appears to earn its place without excessive surface area.

    Completeness4/5

    The toolset covers the core read-only lifecycle for uptime monitoring: service catalog, single and batch status, summaries, historical aggregates, statistics, and incident signals. Minor gaps may exist around additional catalog metadata or richer incident detail, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues