English Français العربية

Cron Parser API

Official registry Other

Parse, validate and explain cron expressions. Get next run times. x402 micropayment.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (sse)
Claude Code 
claude mcp add --transport sse cron-parser-api 'https://cron-parser.api.klymax402.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "cron-parser-api": {
            "type": "sse",
            "url": "https://cron-parser.api.klymax402.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Cron Parser API
  2. Quickstart -- MCP
  3. Quickstart -- HTTP (x402)
  4. Tools
  5. Example agent prompts
  6. Payment
  7. Part of klymax402
  8. License

Cron Parser API

Parse, validate, and explain cron expressions. Get next N run times in any timezone. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

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

Quickstart -- HTTP (x402)

curl -X POST "https://cron-parser.api.klymax402.com/api/parse" \
  -H "Content-Type: application/json" \
  -d '{"expression":"..."}'
# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
schedule_parse_cronPOST/api/parse$0.003Parse a cron expression and get next run times
schedule_parse_cron

Use this when you need to parse, validate, or explain a cron expression. Returns human-readable description, next N execution times, and field breakdown. Supports standard 5-field cron and extended 6-field (with seconds). Do NOT use for scheduling tasks — use api_test_webhook instead. Do NOT use for JSON validation — use data_validate_json instead.

Parameters

NameTypeRequiredDescription
expressionstringyesCron expression (e.g. '0 9 * * 1-5' or '*/5 * * * *')
timezonestringnoIANA timezone (default: UTC, e.g. America/New_York)
countnumbernoNumber of next run times to return (default: 5, max: 20)

Example agent prompts

  • "Parse, validate, or explain a cron expression"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Frequently asked questions

What is Cron Parser API?

Parse, validate and explain cron expressions. Get next run times. x402 micropayment.

How do I install Cron Parser API?

It runs as a remote server. In Claude Code: claude mcp add --transport sse cron-parser-api 'https://cron-parser.api.klymax402.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Cron Parser API need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Cron Parser API open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Cron Parser API?

It is published by Br0ski777. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.