# cron-mcp (npm · @nopilot/cron-mcp)

Cron toolkit: validate 5/6-field expressions (L/#nth), next fire times in any IANA timezone

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@nopilot/cron-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/latbert-cron-mcp/nopilot-cron-mcp.md), [page](https://verifymcp.io/servers/latbert-cron-mcp/nopilot-cron-mcp)

## Channel facts

- Registry: `npm`
- Package: `@nopilot/cron-mcp`
- Version: `1.0.1`
- 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-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 97 dependencies flagged as unhealthy.
- **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 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 374 tokens (~124/item across 3 items; 3 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **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

### How do I install the cron-mcp server?

cron-mcp runs locally as an npm package, launched with npx -y @nopilot/cron-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add latbert-cron-mcp -- npx -y @nopilot/cron-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "latbert-cron-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@nopilot/cron-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "latbert-cron-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@nopilot/cron-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add latbert-cron-mcp -- npx -y @nopilot/cron-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add latbert-cron-mcp --command npx --arg -y --arg @nopilot/cron-mcp
```

### Hermes

```yaml
mcp_servers:
  latbert-cron-mcp:
    command: "npx"
    args: ["-y", "@nopilot/cron-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "latbert-cron-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@nopilot/cron-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add latbert-cron-mcp -t stdio -c npx -a -y @nopilot/cron-mcp
```

### Other

```json
{
  "mcpServers": {
    "latbert-cron-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@nopilot/cron-mcp"
      ]
    }
  }
}
```

## 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-11-17 (score 71, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-16 (score 71)

First indexed and scored.

## MCP tools (3)

### `cron_validate` (~135 tokens)

Cron expression validator

Validate a cron expression (5-field minute..day-of-week or 6-field second..day-of-week). Returns valid/error plus normalized per-field parts and whether day-of-month and day-of-week are both restricted (Vixie-cron OR semantics). Supported syntax: *, lists, ranges, steps, L (last day / last weekday), W (nearest weekday), LW, ? and #nth weekday. Pure local computation.

Input parameters:

- `expression` (string, required): Cron expression, e.g. "*/5 * * * *" (5-field) or "0 30 9 * * *" (6-field with seconds)

### `cron_next_runs` (~163 tokens)

Next fire times

Compute the next N fire times of a cron expression in any IANA timezone, returned as ISO-8601 UTC instants. Deterministic; no network access. DST semantics: times skipped by spring-forward gap roll to the next valid time; ambiguous fall-back times use the later offset.

Input parameters:

- `count` (integer): Number of upcoming fire times to return (1..100, default 1)
- `expression` (string, required): Cron expression (5 or 6 fields)
- `from` (string): ISO-8601 instant to search from, exclusive (e.g. '2026-03-01T00:00:00Z'). Defaults to now.
- `timezone` (string): IANA timezone the expression is anchored to (default 'UTC')

### `cron_describe` (~76 tokens)

Cron to human language

Explain a cron expression in plain English or Chinese (中文). Deterministic template-based rendering — no LLM involved. Understands L/W/# modifiers.

Input parameters:

- `expression` (string, required): Cron expression (5 or 6 fields)
- `locale` (string): Output language: 'en' English or 'zh' Simplified Chinese

## Diagnostics

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

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 71
- 2026-11-16: 71

## Common questions

### What is the cron-mcp server?

cron-mcp is listed in the public MCP registry as io.github.latbert/cron-mcp. Cron toolkit: validate 5/6-field expressions (L/#nth), next fire times in any IANA timezone. This page covers its npm package (@nopilot/cron-mcp).

### Is the cron-mcp server safe to use?

cron-mcp scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the cron-mcp server expose?

cron-mcp exposes 3 tools: cron_validate, cron_next_runs, cron_describe. Their descriptions and schemas cost roughly 374 tokens of context every time the server is loaded.

### Is the cron-mcp server still maintained?

cron-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the cron-mcp server under?

cron-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the cron-mcp server?

VerifyMCP ran 15 checks on cron-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about cron-mcp: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@nopilot/cron-mcp
- Socket report: https://socket.dev/npm/package/@nopilot/cron-mcp
- Repository: https://github.com/latbert/temporal-tools
- Changelog RSS feed: https://verifymcp.io/servers/latbert-cron-mcp/nopilot-cron-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/latbert-cron-mcp/nopilot-cron-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/latbert-cron-mcp/nopilot-cron-mcp.json
- HTML version of this page: https://verifymcp.io/servers/latbert-cron-mcp/nopilot-cron-mcp
