Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

dev.workers.cronping-oren.cronping/heartbeat-monitor

REMOTE · CRONPING.CRONPING-OREN.WORKERS.DEV · SCANNED AUG 3

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

54 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 891 tokens (~222/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% of tool parameters carry a description.Partial
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · cronping.cronping-oren.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-cronping-oren-cronping-heartbeat-mon https://cronping.cronping-oren.workers.dev/mcp
# ~/.codex/config.toml
[mcp_servers.dev-workers-cronping-oren-cronping-heartbeat-mon]
url = "https://cronping.cronping-oren.workers.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-cronping-oren-cronping-heartbeat-mon": {
      "type": "remote",
      "url": "https://cronping.cronping-oren.workers.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-workers-cronping-oren-cronping-heartbeat-mon --url https://cronping.cronping-oren.workers.dev/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-workers-cronping-oren-cronping-heartbeat-mon:
    url: "https://cronping.cronping-oren.workers.dev/mcp"
// mcp.json
{
  "mcpServers": {
    "dev-workers-cronping-oren-cronping-heartbeat-mon": {
      "type": "http",
      "url": "https://cronping.cronping-oren.workers.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +2
    • Tool “get_heartbeat_status” rewrote its description, which is the text the model reads security
    • Schema quality: 656 → 891 functional
    • Schema quality: good → excellent functional
    • New tool “set_heartbeat_alert” functional
    • “create_heartbeat” reworded the description of “email” cosmetic
    • “create_heartbeat” reworded the description of “webhook_url” cosmetic
  • 31 Jul 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 53

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://cronping.cronping-oren.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cronping-oren.workers.dev CN=WE1,O=Google Trust Services,C=US 25 Jul 2026 23 Oct 2026 ECDSA 256 ECDSA-SHA256 532621a346fb9e013bdf3336ac6f61f
SANs: cronping-oren.workers.dev, *.cronping-oren.workers.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of cronping.cronping-oren.workers.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://cronping.cronping-oren.workers.dev/mcp Verified 200
http (plaintext) http://cronping.cronping-oren.workers.dev/mcp Served over HTTP 200
MCP tools — 4 exposed · ~891 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
create_heartbeat ~463

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

NameTypeReqDescription
emailstringEmail 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…
grace_secondsnumberExtra slack before marking DOWN, in seconds. Default 3600.
namestringyesLabel for what is monitored, e.g. "nightly-backup" or "research-agent-loop".
period_secondsnumberHow often you expect a ping, in seconds (min 60). Default 86400 (daily).
pull_containsstringOptional (pull checks only). The fetched response body must contain this text to count as UP; otherwise Cronping alerts.
pull_urlstringOptional. 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, s…
stuck_afternumberOptional. 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 progre…
webhook_urlstringhttps webhook (Slack/Discord/generic) for DOWN and recovery alerts. Set this OR email so someone is actually notified when the monitored job goes silent.

No output schema declared.

No examples provided.

get_heartbeat_status ~62

Get the live status of a Cronping check (up/down/new, last ping time, ping count, and whether an alert channel is set).

NameTypeReqDescription
claim_tokenstringyesThe claim_token returned by create_heartbeat.
idstringyes

No output schema declared.

No examples provided.

ping_heartbeat ~195

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.

NameTypeReqDescription
idstringyesThe check id returned by create_heartbeat.
progress_tokenstringOptional. 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.
signalstringsuccess | start | fail. Default success.

No output schema declared.

No examples provided.

set_heartbeat_alert ~171

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.

NameTypeReqDescription
claim_tokenstringyesThe claim_token returned by create_heartbeat.
emailstringEmail address to notify (e.g. the operator/owner). Pass empty string to clear.
idstringyesThe check id returned by create_heartbeat.
webhook_urlstringOptional https webhook (Slack/Discord/generic) to notify. Pass empty string to clear.

No output schema declared.

No examples provided.