Cron Monitor

io.github.lazymac2xPublished by GitHub account lazymac2xv1.0.0Updated Oct 25, 2026

Cloudflare Workers MCP server: cron-monitor

The publisher's own server: Croncool Cron Jobs

VerifiedStreamable HTTPWeb executableProductivity & Workflow Security & Monitoring

Server details

Identifier: io.github.lazymac2x/cron-monitor
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account lazymac2x for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.lazymac2x%2Fcron-monitor.svg)](https://sourceweft.com/mcp/io.github.lazymac2x%2Fcron-monitor?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A remote MCP server for cron job monitoring: an assistant can send heartbeats, check monitor status, and manage monitors and ping history.

What you can do: Send heartbeat pings to a monitor, including start/complete pairs for duration tracking or a fail ping to mark it down immediately (no API key needed). Read the current status of one monitor with last ping time and total ping count. Get a dashboard overview of all monitors with counts per status and a summary list. Create new monitors and receive the monitor ID for ping URLs. List all monitors with real-time computed status. Retrieve the last 100 ping events for a monitor, including type, timestamp, IP and duration.
When to use it: Useful when you want an assistant to report on scheduled job health, send heartbeats from automated workflows, or inspect recent ping history while debugging a failing cron job.
Requirements: A remote endpoint at api.lazy-mac.com over streamable HTTP; no local runtime or package is needed. An API key is required for the dashboard, monitor creation, monitor listing and ping history tools; the ping tool needs no key.

Before you install

The server writes data: pings change monitor state and creating a monitor adds a new record. An API key is needed for several tools, so treat it as a secret. Ping events expose client IP addresses in the history.

Installation

In SourceWeft

Open Cron Monitor in the dashboard and add it to a workspace.
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/io.github.lazymac2x%2Fcron-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": {
    "cron-monitor": {
      "type": "http",
      "url": "https://api.lazy-mac.com/cron-monitor/mcp"
    }
  }
}

README

cron-monitor-api

Cloudflare Workers MCP server: cron-monitor. REST + MCP (JSON-RPC 2.0). Live: api.lazy-mac.com/cron-monitor

Source: README.md at commit 29387d6

Tools

ping_monitor

Send a heartbeat ping to a cron monitor to confirm the job ran successfully. Use ping_type='ping' for simple heartbeats, 'start'+'complete' for duration tracking, or 'fail' to immediately mark it down.

Parametersping_typemonitor_idrequired

get_monitor_status

Get the current status (up/down/grace/new) of a specific cron monitor along with last ping time and total ping count.

Parametersmonitor_idrequired

get_dashboard

Get an overview of all cron monitors — total count, counts per status (up/down/grace/new), and a summary list. Requires API key.

Parametersapi_keyrequired

create_monitor

Parametersnamerequiredapi_keyrequirednotify_urlgrace_period_secondsschedule_descriptionexpected_interval_secondsrequired

list_monitors

List all monitors with real-time computed status. Requires API key.

Parametersapi_keyrequired

get_ping_history

Retrieve the last 100 ping events for a monitor (type, timestamp, IP, duration for complete events). Requires API key.

Parametersapi_keyrequiredmonitor_idrequired

Version history

v1.0.0LatestSep 16, 2026

Score

90% 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.