Heartbeat Monitor

dev.workers.cronping-oren.cronpingPublished by cronping.cronping-oren.workers.devOfficial publisherv1.4.0Updated Oct 24, 2026

Dead-man's-switch for cron jobs & AI agents. Import a crontab to arm one silent-miss alert per job.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that acts as a dead-man's-switch for cron jobs and AI agents, alerting when a scheduled job silently misses its run.

What you can do
Arm silent-miss alerts for scheduled jobs and AI agents, so a missed run is flagged rather than going unnoticed. Import an existing crontab to set up one alert per job in a single step. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you run cron jobs or AI agents on a schedule and want to know when one stops running silently, rather than discovering the gap later.
Requirements
A remote streamable HTTP endpoint; no local package, environment variables or headers are declared. The manifest declares no authentication, so check how the endpoint is secured before relying on it.
Before you install
It monitors scheduled jobs and is meant to raise alerts, so expect it to hold information about your job schedules. The manifest declares no authentication; confirm who can reach the endpoint and what data it stores before importing a crontab.

Installation

In SourceWeft

  1. Open Heartbeat Monitor in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.workers.cronping-oren.cronping%2Fheartbeat-monitor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "heartbeat-monitor": {
      "type": "http",
      "url": "https://cronping.cronping-oren.workers.dev/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.4.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.