mcpbeat

Heartbeat Monitor MCP Server

by workers-cronping-oren-cronping
answering

Heartbeat Monitor is answering right now. Last checked moments ago. It exposes 4 tools.

Heartbeat monitor & dead-man's-switch for AI agents, cron jobs & workers. Late ping emails you.

Uptime history 63 hours of history
63 hours agonow
100.0%
Uptime 24h
92 of 92 checks
4
Tools
read from the server
71 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add heartbeat-monitor --transport http https://cronping.cronping-oren.workers.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "heartbeat-monitor": {
      "url": "https://cronping.cronping-oren.workers.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.heartbeat-monitor]
url = "https://cronping.cronping-oren.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "heartbeat-monitor": {
      "url": "https://cronping.cronping-oren.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "heartbeat-monitor": {
      "url": "https://cronping.cronping-oren.workers.dev/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

heartbeat
create_heartbeat
Create a Cronping heartbeat monitor (dead-man's-switch). Returns a ping_url to call on each successful run of your agent loop, worker, or cron job, plus a claim_token to manage it. If pings stop arriving within period+grace, Cronping raises an alert. No account required. After creating, send one verification ping (call ping_heartbeat with the returned id) to confirm setup — the check flips from 'new' to UP so you know it's wired correctly. Alternatively, pass pull_url to make a PULL check: Cronping fetches that URL on schedule and alerts if it fails — for targets that can't call a ping URL (a health endpoint, status page, or API).
get_heartbeat_status
Get the live status of a Cronping check (up/down/new, last ping time, ping count, and whether an alert channel is set).
set_heartbeat_alert
Add or change the alert channel on an EXISTING Cronping check (use this instead of creating a duplicate). Sets the email and/or webhook (Slack/Discord/generic https) that Cronping notifies when the monitor goes silent or recovers. Without an alert channel a check tracks status but can't warn you — call this once per check to make the dead-man's-switch actually protect you.
ping
ping_heartbeat
Send a heartbeat signal to a Cronping check. signal="success" (default) marks it UP and resets the timer; "start" records that a run began (for duration); "fail" marks it DOWN immediately and alerts. Optionally pass progress_token (a digest of your run's actual output) on success pings: if the same token repeats for several consecutive runs, the check flips to STUCK — catching a "zombie" job that keeps pinging on schedule while its real work has stalled.

Endpoints

URLTransportStateLatencyChecked
https://cronping.cronping-oren.workers.dev/mcp streamable-http answering 96 ms 0 min ago

Alternatives to Heartbeat Monitor

same job, measured the same way
Datasieve
by gitwormq

On-chain watches, web-page monitors, dead-man switches, cron, and agent coordination, paid via x402.

32 installs/wk local only
Docker MCP Server
by friendlygeorge

MCP server for Docker — containers, health checks, Compose, logs, monitoring for AI agents

77 installs/wk local only
Web
by rog0x

Web scraping, search, monitoring, and HTML-to-markdown for AI agents

34 installs/wk local only
Pingcheck MCP
by churman1113

PingCheck status monitoring for AI agents. Read public pages or your own monitors via pk_ API key.

217 installs/wk local only
Anakin
by anakin

Web data for AI agents: scrape, crawl, search, deep research, site monitoring, browser automation

70 installs/wk local only
MCP Server Health Monitor
by dbsectrainer

Health monitoring for all your MCP servers

33 installs/wk local only
Site Spy
by vkuprin

MCP server for Site Spy — lets AI agents monitor websites for changes

32 installs/wk local only
Cronitor
by usefulapi

Manage Cronitor monitors and send telemetry pings — list, inspect, create, update, delete.

6 tools answering

Heartbeat Monitor — questions

Answers built from our own checks of this server.

What can Heartbeat Monitor do?
It exposes 4 tools, read directly from the server on our last check. Among them: create_heartbeat, get_heartbeat_status, ping_heartbeat, set_heartbeat_alert. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Heartbeat Monitor working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 71 ms. The bar chart above shows every period we have measured.
How do I connect Heartbeat Monitor?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Heartbeat Monitor need an API key?
No. Heartbeat Monitor completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Heartbeat Monitor?
It answers our handshake in 71 ms on average, which is faster than 94% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.