Developer · Remote MCP server
Heartbeat Monitor
Dead-man's-switch for cron jobs & AI agents. Import a crontab to arm one silent-miss alert per job.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.workers.cronping-oren.cronping/heartbeat-monitor- Version
- 1.4.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-29
- Updated
- 2026-08-29
- Publisher
- dev.workers.cronping-oren.cronping
- Namespace
- Namespace verified by the MCP Registry via the domain cronping.cronping-oren.workers.dev or a parent domain of it · how
- Website
- cronping.cronping-oren.workers.dev
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://cronping.cronping-oren.workers.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
How to connect Heartbeat Monitor
Heartbeat Monitor is a remote MCP server: there is nothing to install. Its endpoint is https://cronping.cronping-oren.workers.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Health Hub MCPSelf-hosted MCP server for Android Health Connect - 34 metrics, daily rollups, dedup, 5 LLM tools. | Remote · HTTP |
| HealthchecksInspect, create and adjust Healthchecks cron and uptime checks, and read why one failed. | Local · stdio |
| HealthchecksioManage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io. | Remote · HTTPLive check: ✓ handshake |
| Heartbeat - dead-man switch for cron jobs & AI agentsDead-man switch monitors for cron & AI agents with dependency-cascade alerts. No account needed. | Remote · HTTPLive check: ✓ handshake |
| Heartwood Memory - governed memory for AI agentsHeartwood Memory - governed AI agent memory; signed provenance. BUSL-1.1; not OSI open source. | Local · stdio |
| HeddleContent-addressed contracts and a verification cache that cut agent context by skipping proven code. | Local · stdio |
| HefestoAIPre-commit code quality guardian. Detects semantic drift in AI-generated code. | Remote · HTTPLive check: ✓ handshake |
| HEIDESDeterministic code analysis harness giving AI agents senses, memory and judgment for code. | Local · stdio |