heartbeat-monitor
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
Scored across 7 tools
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.
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.
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.
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.
2 tool updates
- Added
delete_heartbeat - Added
pause_heartbeat
1 tool update
- Added
import_crontab
1 tool update
- Added
set_heartbeat_alert
1 tool update
- Changed
create_heartbeat2 fields changed- changed
Input schema / properties / email / descriptionPrevious 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." - changed
Input schema / properties / webhook_url / descriptionPrevious 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."
1 tool update
- Changed
create_heartbeat2 fields changed- added
Input schema / properties / pull_containsAdded value: +{ + "description": "Optional (pull checks only). The fetched response body must contain this text to count as UP; otherwise Cronping alerts.", + "type": "string" +} - added
Input schema / properties / pull_urlAdded 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" +}
2 tool updates
- Changed
create_heartbeat1 field changed- added
Input schema / properties / stuck_afterAdded 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" +}
- Changed
ping_heartbeat1 field changed- added
Input schema / properties / progress_tokenAdded 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" +}
3 tool updates
- First observed
create_heartbeat - First observed
get_heartbeat_status - First observed
ping_heartbeat
Related MCP Connectors
Dead-man switch monitors for cron & AI agents with dependency-cascade alerts. No account needed.
Dead-man switch for cron and webhooks: ingest URL, miss detection, alerts and a status feed.
Dead-man switch for AI agents & cron jobs: heartbeat with state capsule, alerts + resume links
Know when cron jobs and AI agents stop running: create monitors and check in from your agent.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceThe 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
- FlicenseNot gradedqualityBmaintenanceDead-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.-
- AlicenseAqualityAmaintenanceMonitoring that agents set up for themselves — cron jobs, CI/CD pipelines and AI agent runs.503MIT
- AlicenseNot gradedqualityDmaintenanceSchedule any prompt on any cron expression; when it fires, we POST the job to your callback URL. No LLM in the stack.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.