Healthchecks.io integration
Healthchecks.io is a cron job monitoring service. Receive alerts when scheduled jobs (cron, scheduled tasks, backups, batch processes) don't run on time. The Management API lets you list, create, update, pause, resume and delete checks, inspect pings and status flips, list integrations and badges programmatically.
Say what should happen.
The workflow builds itself.
Common Healthchecks.io use cases
- Decommission a job
- Monitor a cron job
- Embed badges in a README
- End a maintenance window
- Audit when a job last ran
- Compute uptime over a window
- Show all jobs in a dashboard
- Reschedule a cron job monitor
- Discover available integrations
- Read the stdout of a failed run
What you can do with Healthchecks.io
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Check, 7 operations
create_checkCreate checkPOSTCreate a new checkdelete_checkDelete checkDELETEDelete a checkget_checkGet checkGETGet a single checklist_checksList checksGETList all checks in the projectpause_checkPause checkPOSTPause a checkresume_checkResume checkPOSTResume a paused checkupdate_checkUpdate checkPOSTUpdate an existing check
Ping, 2 operations
get_ping_bodyGet ping bodyGETGet the body of a single pinglist_pingsList pingsGETList recent pings for a check
Badge, 1 operation
list_badgesList badgesGETList project badges
Channel, 1 operation
list_channelsList channelsGETList notification integrations
Flip, 1 operation
list_flipsList flipsGETList status changes for a check
Status, 1 operation
get_statusGet statusGETHealthchecks.io service status
Healthchecks.io API rate limits
- 100 requests per minute
Exceeding ~100 req/min returns HTTP 429.
These are the limits Healthchecks.io documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Healthchecks.io documentation for current values.
Use Healthchecks.io from Claude Code, Cursor or Codex
Connect Healthchecks.io in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Healthchecks.io operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Healthchecks.io
- Create your workspace
Sign up free. Nothing to install.
- Connect Healthchecks.io once
Add your Healthchecks.io connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Healthchecks.io integration FAQ
What can you do with the Healthchecks.io integration?
LiveContext exposes 13 operations on Healthchecks.io, covering check, ping, badge and channel. Common uses include Decommission a job, Monitor a cron job and Embed badges in a README.
What are the Healthchecks.io API rate limits?
Healthchecks.io documents 100 requests per minute. Exceeding ~100 req/min returns HTTP 429. Limits are set by Healthchecks.io and can depend on your plan.
