Get started free
All integrations

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.

13 toolsAPI keyAPI docs

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

  • POSTcreate_check

    Create a new check

  • DELETEdelete_check

    Delete a check

  • GETget_check

    Get a single check

  • GETlist_checks

    List all checks in the project

  • POSTpause_check

    Pause a check

  • POSTresume_check

    Resume a paused check

  • POSTupdate_check

    Update an existing check

Ping, 2 operations

  • GETget_ping_body

    Get the body of a single ping

  • GETlist_pings

    List recent pings for a check

Badge, 1 operation

  • GETlist_badges

    List project badges

Channel, 1 operation

  • GETlist_channels

    List notification integrations

Flip, 1 operation

  • GETlist_flips

    List status changes for a check

Status, 1 operation

  • GETget_status

    Healthchecks.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 Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Healthchecks.io

  1. Create your workspace

    Sign up free. Nothing to install.

  2. 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.

  3. 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.

Popular integrations

Browse the whole catalog