Skip to main content
Glama
jaredhobbs

cronalert-mcp

by jaredhobbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to cronalert-mcp

No user-submitted related servers found.

    Related Servers

    • uptrack-mcp by Uptrack-App

      uptrack-mcpofficial

      Uptrack-App
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents like Claude, ChatGPT, and Cursor.
      5 npm
      MIT

    • exit1-mcp

      Mopra
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Exit1 uptime monitoring. Enables AI assistants to create and manage uptime checks, configure alerts, and query status via natural language.
      41 npm
      MIT
    • Drumbeats MCP by drumbeats-io

      Drumbeats MCPofficial

      drumbeats-io
      A
      license
      A
      quality
      A
      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
      13 npm
      2
      Apache 2.0
    • uptimepage by uptimepage

      uptimepageofficial

      uptimepage
      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.
      35
      AGPL 3.0

    • keepitalive-mcp

      salab3rt
      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.
      14 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The tools are well-organized around specific resources (monitors, incidents, status pages) and actions (create, delete, get, list, update), making it easy for an agent to select the correct tool without confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., create_monitor, list_incidents, update_monitor). The naming is uniform throughout, using snake_case and clear, descriptive verbs that align with the action each tool performs.

    Tool Count5/5

    With 9 tools, the server is well-scoped for uptime monitoring and alerting. Each tool serves a distinct and necessary function, covering core operations like CRUD for monitors, incident management, and status page listing, without being overly sparse or bloated.

    Completeness5/5

    The tool surface provides complete CRUD/lifecycle coverage for the uptime monitoring domain. It includes creation, retrieval, updating, and deletion of monitors, along with incident tracking and status page management, leaving no obvious gaps for agent workflows.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources