Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

cron-mcp

NPM · @NOPILOT/CRON-MCP

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

Available components

71 Trust /100

Last scanned (19 hours ago)

Scores higher than 42% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 374 tokens (~124/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 17 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 16 Nov 26 71

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@nopilot/cron-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 97 packages
Packages resolved 97
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~374 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cron_describe ~76

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

NameTypeReqDescription
expressionstringyesCron expression (5 or 6 fields)
localestring–Output language: 'en' English or 'zh' Simplified Chinese

No output schema declared.

No examples provided.

cron_next_runs ~163

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.

NameTypeReqDescription
countinteger–Number of upcoming fire times to return (1..100, default 1)
expressionstringyesCron expression (5 or 6 fields)
fromstring–ISO-8601 instant to search from, exclusive (e.g. '2026-03-01T00:00:00Z'). Defaults to now.
timezonestring–IANA timezone the expression is anchored to (default 'UTC')

No output schema declared.

No examples provided.

cron_validate ~135

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.

NameTypeReqDescription
expressionstringyesCron expression, e.g. "*/5 * * * *" (5-field) or "0 30 9 * * *" (6-field with seconds)

No output schema declared.

No examples provided.

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.

npm · @nopilot/cron-mcp

# add to Claude Code
claude mcp add latbert-cron-mcp -- npx -y @nopilot/cron-mcp
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.