What it does
The server parses, validates and explains cron expressions. For a given expression it returns a human-readable description, the next N execution times in a chosen IANA timezone, and a breakdown of each field. It accepts standard 5-field expressions and extended 6-field expressions that include seconds.
It suits an agent that needs to check whether a cron schedule is correct, confirm when a job will next fire, or explain an unfamiliar expression. For scheduling tasks or JSON validation, the publisher points to other tools, api_test_webhook and data_validate_json respectively.
The tool, schedule_parse_cron, can be added to an MCP client configuration, or called over HTTP as a POST request to /api/parse using any x402-aware client. Each call costs $0.003 and is paid in USDC on Base L2, so no API key or signup is needed. Parameters are the expression, an optional timezone (default UTC), and an optional count of run times (default 5, maximum 20). The publisher lists the server as part of the klymax402 marketplace and releases it under the MIT licence.
Limitations and requirements
Each call is paid per request through the x402 protocol in USDC on Base L2, at $0.003 per call. The count parameter is capped at 20 run times, and the timezone defaults to UTC when omitted.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Cron Parser API
Parse, validate and explain cron expressions. Get next run times. x402 micropayment.
v1.1.0As shown on registry.modelcontextprotocol.io when we last read it