Cron Tools
OCI · GHCR.IO/BASITALISANDHU/MCP-CRON-TOOLS
Parse, explain and validate 5-field cron expressions and list upcoming runs in a time zone.
Available components
Last scanned (21 hours ago)
Scores higher than 78% of OCI servers
Category Developer Tools
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to basitalisandhu/dev-mcp-servers). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 885 tokens (~177/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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: 2 categories
Categories scored 0 because we could not verify them: 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.
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.
- 14 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 82 functional
- 13 Oct 26 0
- Package version: 0.2.0 → 0.2.1 functional
- 12 Oct 26 0
- Package version: 0.1.1 → 0.2.0 functional
- 6 Oct 26 20
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 16 Oct 2026 · Analysed oci/ghcr.io/basitalisandhu/mcp-cron-tools@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | basitalisandhu/dev-mcp-servers |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/basitalisandhu/dev-mcp-servers/.github/workflows/publish-github-packages.yml@refs/tags/v0.2.1 |
| Rekor log index | 3244679573 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:9d193b31021f71db8bd087fd0ea3430be0aacf3253a7c1332ac6a1c2cc6feafb |
Background: How many MCP packages publish verified provenance →
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 →
explain_cron Explain a cron expression in English ~113
Translate a 5-field cron expression into one English sentence, for example '*/15 9-17 * * 1-5' becomes 'At every 15th minute past every hour from 9 through 17 on Monday through Friday.' When both day fields are restricted the sentence says 'or', matching Vixie cron semantics. Also returns the validation warnings.
| Name | Type | Req | Description |
|---|---|---|---|
| expression | string | yes | Five space-separated fields (minute hour day-of-month month day-of-week) or a macro such as @daily. |
No output schema declared.
No examples provided.
next_runs List the next runs of a cron expression ~218
Compute the next count (1 to 100, default 5) run times of a 5-field cron expression in an IANA time zone (default UTC), strictly after 'from' (ISO 8601 date-time, default now). Each run is returned in the zone's local time with its UTC offset and in UTC. Daylight-saving transitions follow the zone's rules: a wall-clock time skipped by a forward transition is not run that day, and a repeated hour runs twice. Reports when no run exists within ten years. Results are oldest first.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| expression | string | yes | Five space-separated fields (minute hour day-of-month month day-of-week) or a macro such as @daily. |
| from | string | – | ISO 8601 date-time to start after, for example 2026-01-31T09:00:00Z. Default: now. |
| timezone | string | – | IANA zone such as Europe/Berlin or America/New_York. Default UTC. |
No output schema declared.
No examples provided.
parse_cron Parse a cron expression ~92
Parse a 5-field cron expression (or @ macro) and return, for each field, the raw text, whether it is a wildcard, and every value it accepts, plus the normalised expression. Returns an error with the offending field when the expression is invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| expression | string | yes | Five space-separated fields (minute hour day-of-month month day-of-week) or a macro such as @daily. |
No output schema declared.
No examples provided.
previous_runs List the previous runs of a cron expression ~218
Compute the previous count (1 to 100, default 5) run times of a 5-field cron expression in an IANA time zone (default UTC), strictly before 'from' (ISO 8601 date-time, default now). Each run is returned in the zone's local time with its UTC offset and in UTC. Daylight-saving transitions follow the zone's rules: a wall-clock time skipped by a forward transition is not run that day, and a repeated hour runs twice. Reports when no run exists within ten years. Results are newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| expression | string | yes | Five space-separated fields (minute hour day-of-month month day-of-week) or a macro such as @daily. |
| from | string | – | ISO 8601 date-time to start before, for example 2026-01-31T09:00:00Z. Default: now. |
| timezone | string | – | IANA zone such as Europe/Berlin or America/New_York. Default UTC. |
No output schema declared.
No examples provided.
validate_cron Validate a cron expression ~103
Check a 5-field cron expression and return valid (boolean), errors (syntax or range problems) and warnings for expressions that parse but behave unexpectedly: day-of-month and day-of-week both restricted (OR semantics), days that do not exist in the selected months, 7 used for Sunday, ? spelling, macro expansion.
| Name | Type | Req | Description |
|---|---|---|---|
| expression | string | yes | Five space-separated fields (minute hour day-of-month month day-of-week) or a macro such as @daily. |
No output schema declared.
No examples provided.
How do I install the Cron Tools MCP server?
Cron Tools runs locally as a container image, launched with docker run --rm -i ghcr.io/basitalisandhu/mcp-cron-tools:0.2.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/basitalisandhu/mcp-cron-tools
claude mcp add basitalisandhu-mcp-cron-tools -- docker run --rm -i ghcr.io/basitalisandhu/mcp-cron-tools:0.2.1
What is the Cron Tools MCP server?
Cron Tools is an MCP server listed in the public MCP registry as io.github.basitalisandhu/mcp-cron-tools. Parse, explain and validate 5-field cron expressions and list upcoming runs in a time zone. This page covers its container image (ghcr.io/basitalisandhu/mcp-cron-tools).
Is the Cron Tools MCP server safe to use?
Cron Tools scores 50 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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 Tools MCP server expose?
Cron Tools exposes 5 tools: parse_cron, explain_cron, validate_cron, next_runs, previous_runs. Their descriptions and schemas cost roughly 744 tokens of context every time the server is loaded.
Is the Cron Tools MCP server still maintained?
Cron Tools is still listed as active in the MCP registry. We last reached this channel on 16 October 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 Tools MCP server under?
Cron Tools declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.