Skip to main content
Glama

Server Details

Dead-man's-switch for cron jobs & AI agents. Import a crontab to arm one silent-miss alert per job.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
64.6% over 71 days
Last Tested
Transport
Streamable HTTP
URL

TDQS

A4.4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct role: create, delete, status check, bulk import from crontab, pause/resume, ping, and alert configuraiton. No two tools appear to perform the same action, and the descriptions reinforce their separation.

Naming Consistency4/5

Tool names consistently follow a verb_noun snake_case pattern (create_, delete_, pause_, ping_, set_). 'import_crontab' deviates slightly by naming the input format rather than the domain object, but it remains readable and fits the verb-based convention.

Tool Count5/5

Seven tools is well within the ideal range for a focused heartbeat-monitoring server. Each tool represents a necessary operation without bloat or redundant overlap.

Completeness4/5

The core lifecycle is covered: create, ping, pause/resume, alert setup, status, delete, and bulk import. Missing update functionality for period/grace and no list-all-heartbeats operation are notable but non-blocking gaps for the core dead-man's-switch workflow.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Addeddelete_heartbeat
    • Addedpause_heartbeat
  2. 1 tool update
    • Addedimport_crontab
  3. 1 tool update
    • Addedset_heartbeat_alert
  4. 1 tool update
    • Changedcreate_heartbeat2 fields changed
      • changedInput schema / properties / email / description
        Previous value: -"Optional email address for DOWN and recovery alerts."New value: +"Email address for DOWN and recovery alerts. STRONGLY RECOMMENDED — without an email or webhook_url, Cronping tracks status but cannot notify anyone when the job stops, which defeats the purpose. Use your operator's email."
      • changedInput schema / properties / webhook_url / description
        Previous value: -"Optional https webhook (Slack/Discord/generic) for alerts."New value: +"https webhook (Slack/Discord/generic) for DOWN and recovery alerts. Set this OR email so someone is actually notified when the monitored job goes silent."
  5. 1 tool update
    • Changedcreate_heartbeat2 fields changed
      • addedInput schema / properties / pull_contains
        Added value: +{
        +  "description": "Optional (pull checks only). The fetched response body must contain this text to count as UP; otherwise Cronping alerts.",
        +  "type": "string"
        +}
      • addedInput schema / properties / pull_url
        Added value: +{
        +  "description": "Optional. If set, creates a PULL check instead: Cronping itself fetches this URL every period_seconds and alerts if it fails — use for a target that can't call a ping URL (a public health endpoint, status page, or API). No ping needed.",
        +  "type": "string"
        +}
  6. 2 tool updates
    • Changedcreate_heartbeat1 field changed
      • addedInput schema / properties / stuck_after
        Added value: +{
        +  "description": "Optional. Flip to STUCK if the progress_token passed to ping_heartbeat stays identical for this many consecutive runs (default 3, 0 disables). Catches zombie runs that keep pinging but make no progress.",
        +  "type": "number"
        +}
    • Changedping_heartbeat1 field changed
      • addedInput schema / properties / progress_token
        Added value: +{
        +  "description": "Optional. A short digest/hash of this run's output (e.g. last-processed id, row count, content hash). If it stays identical across stuck_after consecutive runs, the check flips to STUCK and alerts.",
        +  "type": "string"
        +}
  7. 3 tool updates
    • First observedcreate_heartbeat
    • First observedget_heartbeat_status
    • First observedping_heartbeat

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    The watchdog for unattended AI agents: flags MISSED, FAILED, NO_EVIDENCE, RETRY_STORM, BUDGET, DRIFT and STALLED runs of Claude Code routines, OpenClaw, n8n and cron jobs, and alerts via Telegram, Slack or webhook. MIT and self-hostable.
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    Dead-man's-switch monitoring for cron jobs and AI agents: your job or agent pings a URL each run, and Kywio alerts you when the pings stop. MCP-native (create/ping/get heartbeat) plus REST — an outside observer for agents that can't detect their own death.
    -
  • A
    license
    Not graded
    quality
    D
    maintenance
    Schedule any prompt on any cron expression; when it fires, we POST the job to your callback URL. No LLM in the stack.
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources