Skip to main content
Glama
bartekrutkowski

watchgoose-mcp

Related Servers

Alternatives to watchgoose-mcp

  • A
    license
    A
    quality
    B
    maintenance
    MCP server for CronAlert uptime monitoring — manage monitors, check results, and incidents from any MCP-compatible AI client.
    9
    131 npm
    MIT

Related Servers

  • 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.
    10 npm
    1
    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.
    42
    12
    AGPL 3.0
  • A
    license
    Not graded
    quality
    A
    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.
    42
    AGPL 3.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    MCP server for KEEPitALIVE monitoring, enabling AI agents to read and manage monitors, incidents, triggers, and notification routing via the v1 API, with scope-based tool filtering and safety modes.
    5 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables LLM clients to manage Uptime Kuma HTTP(S) monitors, groups, tags, and notifications, and to retrieve heartbeats, stats, and incident history through MCP tools.
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    MCP server for Drumbeats monitoring. Enables creating monitors, triaging incidents, and running HTTP/SSL/DNS checks using natural language from any AI client.
    16
    28 npm
    2
    Apache 2.0

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

The three tools are clearly distinct: list checks, get a single check by key, and list status changes. There is no meaningful overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent lowercase verb_noun pattern: list_checks, get_check, list_flips. The singular/plural difference is natural and appropriate.

Tool Count5/5

Three tools is well-scoped for a read-only monitoring server. Each tool provides a distinct capability with no redundancy or filler.

Completeness4/5

The read-only monitoring surface is coherent: discover checks, inspect a check, and view its flip history. Check management and ping actions appear to happen outside MCP, so the lack of mutation tools is a minor gap rather than a fatal one.

Maintenance

ActivityMaintained
ResponsivenessNo issues