io.github.lazymac2x/cron-parser is an MCP server published by io.github.lazymac2x, hosted at api.lazy-mac.com. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 6 tools, including explain_cron, validate_cron, next_runs, generate_cron, diff_cron.
Cloudflare Workers MCP server: cron-parser
160 connections through 5 shared values. Tap any node.
Explain a cron expression in human-readable form and show parsed fields. Supports @presets like @daily, @weekly.
| Parameter | Type | Description |
|---|---|---|
| expression * | string | Cron expression (e.g. "*/5 * * * *" or "@daily") |
{
"name": "explain_cron",
"description": "Explain a cron expression in human-readable form and show parsed fields. Supports @presets like @daily, @weekly.",
"inputSchema": {
"type": "object",
"required": [
"expression"
],
"properties": {
"expression": {
"type": "string",
"description": "Cron expression (e.g. \"*/5 * * * *\" or \"@daily\")"
}
}
}
}Check if a cron expression is valid. Returns {valid: bool, error?: string}.
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
| Parameter | Type | Description |
|---|---|---|
| expression * | string | Cron expression to validate |
{
"name": "validate_cron",
"description": "Check if a cron expression is valid. Returns {valid: bool, error?: string}.",
"inputSchema": {
"type": "object",
"required": [
"expression"
],
"properties": {
"expression": {
"type": "string",
"description": "Cron expression to validate"
}
}
}
}Get the next N scheduled run times for a cron expression. Uses standard Unix OR semantics for day fields.
| Parameter | Type | Description |
|---|---|---|
| from | string | ISO 8601 start date (default: now) |
| count | number | Number of next runs to return (1-20, default 5) |
| expression * | string | Cron expression |
{
"name": "next_runs",
"description": "Get the next N scheduled run times for a cron expression. Uses standard Unix OR semantics for day fields.",
"inputSchema": {
"type": "object",
"required": [
"expression"
],
"properties": {
"from": {
"type": "string",
"description": "ISO 8601 start date (default: now)"
},
"count": {
"type": "number",
"description": "Number of next runs to return (1-20, default 5)"
},
"expression": {
"type": "string",
"description": "Cron expression"
}
}
}
}Generate a cron expression from human-friendly options.
| Parameter | Type | Description |
|---|---|---|
| at | object | |
| on | object | |
| every * | string | Frequency |
| month | number | Month (1-12) |
{
"name": "generate_cron",
"description": "Generate a cron expression from human-friendly options.",
"inputSchema": {
"type": "object",
"required": [
"every"
],
"properties": {
"at": {
"type": "object",
"properties": {
"hour": {
"type": "number"
},
"minute": {
"type": "number"
}
}
},
"on": {
"type": "object",
"properties": {
"day": {
"type": "number",
"description": "0=Sunday"
},
"date": {
"type": "number",
"description": "1-31"
}
}
},
"every": {
"enum": [
"minute",
"hour",
"day",
"week",
"month"
],
"type": "string",
"description": "Frequency"
},
"month": {
"type": "number",
"description": "Month (1-12)"
}
}
}
}Compare two cron expressions and return per-field differences.
| Parameter | Type | Description |
|---|---|---|
| first * | string | First cron expression |
| second * | string | Second cron expression |
{
"name": "diff_cron",
"description": "Compare two cron expressions and return per-field differences.",
"inputSchema": {
"type": "object",
"required": [
"first",
"second"
],
"properties": {
"first": {
"type": "string",
"description": "First cron expression"
},
"second": {
"type": "string",
"description": "Second cron expression"
}
}
}
}List commonly used cron expressions with descriptions.
No parameters.
{
"name": "common_crons",
"description": "List commonly used cron expressions with descriptions.",
"inputSchema": {
"type": "object",
"properties": {}
}
}Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.