Cronping
About
Remote MCP server that gives your AI agent a dead-man's-switch: it calls create_heartbeat, pings on schedule, and emails you the instant an agent or cron loop stops checking in.
Details
- Author
- Unknown
- Categories
- Developer Tools, Infrastructure, Other, Automation
Jump to
Know the instant your agent or cron job dies.
Cronping is a dead-man's-switch for anything that runs on a loop — AI agents, bots, workers, cron jobs, backups, CI. Your process pings a URL each run. If a ping doesn't arrive on time, we email you. That's it.
No password, no credit card. Your ping URL is live instantly — add an email whenever you want alerts, and create an account later to keep it.
orpaste a whole crontab·import systemd timers·watch a 15-second live demo·see an example status page·monitor an AI agent·see how it works
🤖 Fittingly, Cronping is itself built and operated by an autonomous AI agent — watching over the loops that keep other automations alive.
Add one line to any cron, backup script, or CI job:
0 4 /run-backup.sh && curl -fsShttps://cronping.cronping-oren.workers.dev/ping/your-check-id
Create a check, copy the ping URL, drop it in your script. No agents to install, no config files.
Email the moment a job misses its window — and again when it recovers. No noise.
Agent loops, workers, and daemons stop with no error to catch. Ping each cycle (add /start + /fail for run timing) and hear about silence in under a minute. Free — 20 checks, no card.
Your AI agent can set up its own dead-man's-switch — Cronping is a remote MCP server with create_heartbeat / ping_heartbeat tools. Point any MCP client at /mcp.See how →
Silent failures are the worst failures. An agent loop that stalls, a worker that crashed at 3am, a nightly backup that quietly stopped, a certificate renewal that never ran — nothing errors in a place you're watching, so you find out when it's already a problem. Cronping flips that: instead of watching for errors, it watches forsilence*. If the expected heartbeat doesn't arrive, you hear about it right away.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
Cron scheduling, uptime monitoring, heartbeat monitoring, and email verification as native MCP tools for Claude Code, Cursor, and any MCP-compatible agent.
Breaking Change Alerts for Humans and AI Agents.
Paid remote MCP for CLI tool MCP, structured receipts, usage logs, and audit-ready evidence for agent and CI workflows.
MCP server for the Enoch control plane: dispatch gates, evidence sync, provenance, and quality gates for long-running autonomous AI work.
AI-powered Jenkins pipeline intelligence platform with natural language interface. Provides comprehensive pipeline analysis, failure prediction, optimization suggestions, and automated Jenkinsfile reconstruction using Model Context Protocol (MCP) integration.
Manage and observe Prefect workflows through natural language.
MCP server for catching cron silent failures — jobs that exit 0 with empty output, retry storms, action-budget leaks. 6 silent-fail patterns across system cron, systemd timers, OpenClaw cron logs.
Interact with Apache Airflow using natural language to manage and monitor your data workflows.
MCP server for Hatchet - let AI agents observe and operate your workflows: runs, logs, workers, metrics, plus trigger/cancel/replay
Manage notification workflows, users, preferences, and tenant branding via natural language. Trigger email, SMS, push, WhatsApp, Slack, and in-app notifications from Cursor, Claude Desktop, or Windsurf using 24 tools.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
