# io.github.lazymac2x/cron-monitor (remote · api.lazy-mac.com)

Cloudflare Workers MCP server: cron-monitor

- Trust score: 59/100 (low)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.lazy-mac.com`: 59/100 (this document), [markdown](https://verifymcp.io/servers/lazymac2x-cron-monitor/cron-monitor-mcp.md), [page](https://verifymcp.io/servers/lazymac2x-cron-monitor/cron-monitor-mcp)

## Channel facts

- Endpoint: `https://api.lazy-mac.com/cron-monitor/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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 6 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**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 411 tokens (~68/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 lazymac2x-cron-monitor https://api.lazy-mac.com/cron-monitor/mcp
```

### Codex

```toml
[mcp_servers.lazymac2x-cron-monitor]
url = "https://api.lazy-mac.com/cron-monitor/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lazymac2x-cron-monitor": {
      "type": "remote",
      "url": "https://api.lazy-mac.com/cron-monitor/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lazymac2x-cron-monitor --url https://api.lazy-mac.com/cron-monitor/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lazymac2x-cron-monitor:
    url: "https://api.lazy-mac.com/cron-monitor/mcp"
```

### Other

```json
{
  "mcpServers": {
    "lazymac2x-cron-monitor": {
      "type": "http",
      "url": "https://api.lazy-mac.com/cron-monitor/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-03 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 57, −2)

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

### 2026-07-30 (score 59, 0)

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

### 2026-07-29 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 58, +1)

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

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (6)

### `ping_monitor` (~78 tokens)

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.

Input parameters:

- `monitor_id` (string, required): Monitor ID to ping
- `ping_type` (string): Type of ping event

### `get_monitor_status` (~47 tokens)

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

Input parameters:

- `monitor_id` (string, required): Monitor ID to check

### `get_dashboard` (~54 tokens)

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

Input parameters:

- `api_key` (string, required): API key (x-api-key header value)

### `create_monitor` (~133 tokens)

Register a new cron job monitor. Returns the monitor ID to use in ping URLs. Requires API key.

Input parameters:

- `api_key` (string, required): API key (x-api-key header value)
- `expected_interval_seconds` (integer, required): How often the job should run (seconds)
- `grace_period_seconds` (integer): Extra seconds allowed after interval before going DOWN
- `name` (string, required): Human-readable monitor name
- `notify_url` (string): Webhook URL for DOWN alerts (receives POST with JSON)
- `schedule_description` (string): Human-readable schedule (e.g. 'Every night at 3am UTC')

### `list_monitors` (~38 tokens)

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

Input parameters:

- `api_key` (string, required): API key (x-api-key header value)

### `get_ping_history` (~61 tokens)

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

Input parameters:

- `api_key` (string, required): API key (x-api-key header value)
- `monitor_id` (string, required): Monitor ID

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lazymac2x-cron-monitor/cron-monitor-mcp#diagnostics

## Score history

- 2026-08-03: 59
- 2026-08-02: 58
- 2026-08-01: 58
- 2026-07-31: 57
- 2026-07-30: 59
- 2026-07-29: 59
- 2026-07-28: 58
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://api.lazy-mac.com/cron-monitor/mcp
- Repository: https://github.com/lazymac2x/cron-monitor-api
- Changelog RSS feed: https://verifymcp.io/servers/lazymac2x-cron-monitor/cron-monitor-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/lazymac2x-cron-monitor/cron-monitor-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/lazymac2x-cron-monitor/cron-monitor-mcp