Skip to main content
Glama
omniwatchguard-mcp

omniwatchguard-mcp

Related Servers

Alternatives to omniwatchguard-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to set up and manage uptime checks for websites and APIs, status pages, cron heartbeats, Lighthouse and SEO audits, alerts, and related monitoring tasks through AI apps.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to manage cron job and scheduled task monitoring through the WatchCron API. Supports listing, creating, updating, pausing, and deleting monitors, retrieving ping URLs and ping/incident history, and listing notification channels.
      9
      11 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets an AI agent add websites, set up and tune uptime, user-flow, security, speed, SEO, domain and compliance monitors, run scans, and review results. It also explains what broke in a failed run and proposes fixes the agent can apply with the user.
      MIT
    • A
      license
      A
      quality
      B
      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.
      57
      1,340 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: CRUD for monitors, one status toggle, and one alert listing. The only potential overlap between update_monitor and set_monitor_status is explicitly resolved by the descriptions (fields vs. pause/resume).

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (list_monitors, get_monitor, create_monitor, update_monitor, delete_monitor, set_monitor_status). The one deviation, set_monitor_status, is still the same convention with a compound noun.

    Tool Count5/5

    Seven tools is a well-scoped set for a monitor-and-alert service, covering the lifecycle without bloat. Every tool has a clear place in the workflow.

    Completeness4/5

    The surface covers monitor CRUD, pause/resume, and alert listing, which are the core operations. Minor gaps exist, such as no alert acknowledgement/mark-read, no bulk operations, and no check-history retrieval beyond the last 20 results in get_monitor.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues