io.github.takeaseatventure/cron-mcp
NPM · CRON-MCP-SERVER · SCANNED AUG 3
MCP cron validator for AI agents; flags impossible schedules and other silent cron bugs.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 410 tokens (~102/item across 4 items; 4 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
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · cron-mcp-server
claude mcp add takeaseatventure-cron-mcp -- npx -y cron-mcp-server
codex mcp add takeaseatventure-cron-mcp -- npx -y cron-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"takeaseatventure-cron-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"cron-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add takeaseatventure-cron-mcp --command npx --arg -y --arg cron-mcp-server
mcp_servers:
takeaseatventure-cron-mcp:
command: "npx"
args: ["-y", "cron-mcp-server"] {
"mcpServers": {
"takeaseatventure-cron-mcp": {
"command": "npx",
"args": [
"-y",
"cron-mcp-server"
]
}
}
} 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.
- 3 Aug 26 +31
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 2 Aug 26 +13
- Security disclosure: unverified → fail ▼ functional
- Dependency health: partial → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: pass functional
- First check of Schema quality: unverified functional
- First check of Tool coverage: 100 functional
- 1 Aug 26 23
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
cron_presets ~73
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
next_runs ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | — | How many future runs to compute (default 5, max 50). |
| expression | string | yes | The cron expression. |
| from | string | — | ISO-8601 start time (defaults to now). |
No output schema declared.
No examples provided.
parse_cron ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expression | string | yes | The cron expression to parse, e.g. "*/5 * * * *" or "0 9 * * 1-5". |
No output schema declared.
No examples provided.
validate_cron ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expression | string | yes | The cron expression to validate. |
No output schema declared.
No examples provided.