# dev.workers.cronping-oren.cronping/heartbeat-monitor (remote · cronping.cronping-oren.workers.dev)

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

- Trust score: 54/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `cronping.cronping-oren.workers.dev`: 54/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-cronping-oren-cronping-heartbeat-monitor/cronping.md), [page](https://verifymcp.io/servers/dev-workers-cronping-oren-cronping-heartbeat-monitor/cronping)

## Channel facts

- Endpoint: `https://cronping.cronping-oren.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http dev-workers-cronping-oren-cronping-heartbeat-mon https://cronping.cronping-oren.workers.dev/mcp
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-cronping-oren-cronping-heartbeat-mon --url https://cronping.cronping-oren.workers.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-cronping-oren-cronping-heartbeat-mon:
    url: "https://cronping.cronping-oren.workers.dev/mcp"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 54, +2)

- [security] Tool “get_heartbeat_status” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 656 → 891
- [functional] Schema quality: good → excellent
- [functional] New tool “set_heartbeat_alert”
- [cosmetic] “create_heartbeat” reworded the description of “email”
- [cosmetic] “create_heartbeat” reworded the description of “webhook_url”

### 2026-07-31 (score 52, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 53)

First indexed and scored.

## MCP tools (4)

### `create_heartbeat` (~463 tokens)

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

Input parameters:

- `email` (string): Email 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_seconds` (number): Extra slack before marking DOWN, in seconds. Default 3600.
- `name` (string, required): Label for what is monitored, e.g. "nightly-backup" or "research-agent-loop".
- `period_seconds` (number): How often you expect a ping, in seconds (min 60). Default 86400 (daily).
- `pull_contains` (string): Optional (pull checks only). The fetched response body must contain this text to count as UP; otherwise Cronping alerts.
- `pull_url` (string): Optional. 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_after` (number): Optional. 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_url` (string): https webhook (Slack/Discord/generic) for DOWN and recovery alerts. Set this OR email so someone is actually notified when the monitored job goes silent.

### `ping_heartbeat` (~195 tokens)

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.

Input parameters:

- `id` (string, required): The check id returned by create_heartbeat.
- `progress_token` (string): Optional. 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.
- `signal` (string): success | start | fail. Default success.

### `get_heartbeat_status` (~62 tokens)

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

Input parameters:

- `claim_token` (string, required): The claim_token returned by create_heartbeat.
- `id` (string, required)

### `set_heartbeat_alert` (~171 tokens)

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.

Input parameters:

- `claim_token` (string, required): The claim_token returned by create_heartbeat.
- `email` (string): Email address to notify (e.g. the operator/owner). Pass empty string to clear.
- `id` (string, required): The check id returned by create_heartbeat.
- `webhook_url` (string): Optional https webhook (Slack/Discord/generic) to notify. Pass empty string to clear.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-cronping-oren-cronping-heartbeat-monitor/cronping#diagnostics

## Score history

- 2026-08-03: 54
- 2026-08-02: 54
- 2026-08-01: 52
- 2026-07-31: 52
- 2026-07-30: 53

## Links

- Remote endpoint: https://cronping.cronping-oren.workers.dev/mcp
- Website: https://cronping.cronping-oren.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-cronping-oren-cronping-heartbeat-monitor/cronping/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-cronping-oren-cronping-heartbeat-monitor/cronping/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-cronping-oren-cronping-heartbeat-monitor/cronping