Skip to main content
Glama
watchcron

watchcron-mcp

Official
by watchcron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to watchcron-mcp

No user-submitted related servers found.

    Related Servers

    • @tickwatch/mcp

      pyrrhuladev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables assistants to monitor cron jobs, investigate failures via runs and incidents, and create or manage monitors through the Tickwatch API.
      MIT

    • fettle-mcp

      fettlesh
      A
      license
      A
      quality
      A
      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
      0
      MIT

    • omniwatchguard-mcp

      Isoprest
      A
      license
      A
      quality
      B
      maintenance
      Enables users to manage OmniWatchGuard website monitors and alerts via natural language. Supports listing, creating, updating, pausing, resuming, and deleting monitors, plus reviewing recent notifications across channels.
      7
      294 npm
      MIT

    • healthchecks-io-mcp

      ronniechong
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Healthchecks.io, allowing users to list, create, update, pause, resume, and delete checks, as well as view ping history and integrations.
      34 npm
      1
      MIT

    • uptime-kuma-mcp-server

      mehbul
      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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a distinct resource+action target: monitor CRUD is split cleanly across list/get/create/update/delete, with pause_monitor covering the orthogonal state toggle. get_pings and get_incidents target clearly separate history types, and list_channels is the only channel tool, so there are no ambiguous boundaries.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (list_monitors, get_monitor, create_monitor, delete_monitor, get_pings, get_incidents). The single deviation, pause_monitor, still fits the pattern even though it also resumes.

    Tool Count5/5

    Nine tools is well-scoped for a cron monitoring service, with each tool earning its place across the lifecycle (create/list/get/update/delete) plus observability and notification surfaces. No redundant or filler tools.

    Completeness4/5

    Monitor lifecycle is fully covered (create, list, get, update, delete, pause/resume) with ping and incident history reads, so core workflows have no dead ends. The gap is channels: list_channels exists with no create/update/delete-channel counterpart, and there is no manual ping/test trigger.

    Resources