# io.github.takeaseatventure/cron-mcp (npm · cron-mcp-server)

MCP cron validator for AI agents; flags impossible schedules and other silent cron bugs.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- npm · `cron-mcp-server`: 66/100 (this document), [markdown](https://verifymcp.io/servers/takeaseatventure-cron-mcp/cron-mcp-server.md), [page](https://verifymcp.io/servers/takeaseatventure-cron-mcp/cron-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `cron-mcp-server`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-04.

- **Supply Chain Security**: 83/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects hono 4.12.33, reached via @modelcontextprotocol/sdk > hono. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 410 tokens (~102/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add takeaseatventure-cron-mcp -- npx -y cron-mcp-server
```

### Codex

```bash
codex mcp add takeaseatventure-cron-mcp -- npx -y cron-mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "takeaseatventure-cron-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "cron-mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add takeaseatventure-cron-mcp --command npx --arg -y --arg cron-mcp-server
```

### Hermes

```yaml
mcp_servers:
  takeaseatventure-cron-mcp:
    command: "npx"
    args: ["-y", "cron-mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "takeaseatventure-cron-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "cron-mcp-server"
      ]
    }
  }
}
```

## 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-04 (score 66, −1)

- [security regression] CVE-2026-69207 affects this package: medium
- [security regression] Known CVEs: partial → fail

### 2026-08-03 (score 67, +31)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: MIT

### 2026-08-02 (score 36, +13)

- [functional regression] Security disclosure: unverified → fail
- [functional regression] Dependency health: partial → unverified
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: unverified
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail

### 2026-08-01 (score 23)

First indexed and scored.

## MCP tools (4)

### `parse_cron` (~117 tokens)

Parse a cron expression and return a human-readable description of when it fires. Supports 5-field standard cron (min hour dom month dow) plus extensions: L (last day/weekday), W (nearest weekday), # (nth weekday), and named months/days (JAN..DEC, SUN..SAT). Use this to explain any cron schedule in plain English.

Input parameters:

- `expression` (string, required): The cron expression to parse, e.g. "*/5 * * * *" or "0 9 * * 1-5".

### `validate_cron` (~117 tokens)

Deeply validate a cron expression for correctness and common mistakes. Catches: impossible schedules (e.g. day 31 in Feb), OR-semantics gotchas (dom AND dow both restricted = either matches, not both), midnight scheduling spikes, uneven step values (*/7), leap-year edge cases, weekday-only warnings, and more. Returns warnings, observations, optimization suggestions, and an estimated yearly run count. Use this BEFORE deploying a cron job to catch silent failures.

Input parameters:

- `expression` (string, required): The cron expression to validate.

### `next_runs` (~103 tokens)

Compute the next N scheduled run times for a cron expression. Returns ISO-8601 timestamps with relative offsets (+5m, +1h, +2d). Use this to preview when a job will actually fire before committing it.

Input parameters:

- `count` (number): How many future runs to compute (default 5, max 50).
- `expression` (string, required): The cron expression.
- `from` (string): ISO-8601 start time (defaults to now).

### `cron_presets` (~73 tokens)

Return a library of common cron expression presets (every 5 min, hourly, daily at midnight, weekdays 9am, monthly, quarterly, yearly, etc.) with their plain-English labels. Use this when a user asks for a "common" or "standard" schedule and you want to offer proven starting points.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/takeaseatventure-cron-mcp/cron-mcp-server#diagnostics

## Score history

- 2026-08-04: 66
- 2026-08-03: 67
- 2026-08-02: 36
- 2026-08-01: 23

## Links

- npm package: https://www.npmjs.com/package/cron-mcp-server
- Socket report: https://socket.dev/npm/package/cron-mcp-server
- Repository: https://github.com/takeaseatventure/cron-mcp
- Changelog RSS feed: https://verifymcp.io/servers/takeaseatventure-cron-mcp/cron-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/takeaseatventure-cron-mcp/cron-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/takeaseatventure-cron-mcp/cron-mcp-server