cron-parser

Cloudflare Workers MCP server: cron-parser

Should I use this

Quality & Safety

A
Description quality
92%
Schema completeness
87%
Naming quality
90%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (1)

  • LOWTool 'diff_cron' description lacks action verbin diff_cron

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~479Tokens (tool definitions)
~616 BTypical response size
Minimal attention impact (0.37% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "cron-parser": {
      "url": "https://api.lazy-mac.com/cron-parser/mcp"
    }
  }
}

Remote endpoints

https://api.lazy-mac.com/cron-parser/mcpstreamable-http

What it can do

Tool inventory

Tools (6)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢explain_cron(expression)

Explain a cron expression in human-readable form and show parsed fields. Supports @presets like @daily, @weekly.

Input Schema

{
  "type": "object",
  "properties": {
    "expression": {
      "type": "string",
      "description": "Cron expression (e.g. \"*/5 * * * *\" or \"@daily\")"
    }
  },
  "required": [
    "expression"
  ]
}
🟢validate_cron(expression)

Check if a cron expression is valid. Returns {valid: bool, error?: string}.

Input Schema

{
  "type": "object",
  "properties": {
    "expression": {
      "type": "string",
      "description": "Cron expression to validate"
    }
  },
  "required": [
    "expression"
  ]
}
🟢next_runs(expression, count, from)

Get the next N scheduled run times for a cron expression. Uses standard Unix OR semantics for day fields.

Input Schema

{
  "type": "object",
  "properties": {
    "expression": {
      "type": "string",
      "description": "Cron expression"
    },
    "count": {
      "type": "number",
      "description": "Number of next runs to return (1-20, default 5)"
    },
    "from": {
      "type": "string",
      "description": "ISO 8601 start date (default: now)"
    }
  },
  "required": [
    "expression"
  ]
}
⚪generate_cron(every, at, on, month)

Generate a cron expression from human-friendly options.

Input Schema

{
  "type": "object",
  "properties": {
    "every": {
      "type": "string",
      "enum": [
        "minute",
        "hour",
        "day",
        "week",
        "month"
      ],
      "description": "Frequency"
    },
    "at": {
      "type": "object",
      "properties": {
        "minute": {
          "type": "number"
        },
        "hour": {
          "type": "number"
        }
      }
    },
    "on": {
      "type": "object",
      "properties": {
        "day": {
          "type": "number",
          "description": "0=Sunday"
        },
        "date": {
          "type": "number",
          "description": "1-31"
        }
      }
    },
    "month": {
      "type": "number",
      "description": "Month (1-12)"
    }
  },
  "required": [
    "every"
  ]
}
⚪diff_cron(first, second)

Compare two cron expressions and return per-field differences.

Input Schema

{
  "type": "object",
  "properties": {
    "first": {
      "type": "string",
      "description": "First cron expression"
    },
    "second": {
      "type": "string",
      "description": "Second cron expression"
    }
  },
  "required": [
    "first",
    "second"
  ]
}
🟢common_crons

List commonly used cron expressions with descriptions.

Input Schema

{
  "type": "object",
  "properties": {}
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded6 tools
verifiedversion not recorded6 tools