How do I install Cron Parser API?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Cron Parser API need an API key?

No required environment variable is listed on this record.

What transport does Cron Parser API use?

Cron Parser API is reached over HTTP.

Cron Parser API

by io.github.Br0ski777

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

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Server URL

https://cron-parser.api.klymax402.com/mcp

Provider

Add in Claude

Claude opens with the name and URL filled in. You still confirm it there.

Claude Code

claude mcp add --transport http io.github.br0ski777-cron-parser https://cron-parser.api.klymax402.com/mcp

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "io.github.br0ski777-cron-parser": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://cron-parser.api.klymax402.com/mcp"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

Related skills

View all

Questions

How do I install Cron Parser API?: Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Cron Parser API need an API key?: No required environment variable is listed on this record.
What transport does Cron Parser API use?: Cron Parser API is reached over HTTP.
When was Cron Parser API last checked?: Last checked 2026-10-21. Parse, validate and explain cron expressions. Get next run times. x402 micropayment.

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

Tool	Method	Path	Price	Description
`schedule_parse_cron`	POST	`/api/parse`	$0.003	Parse 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

Name	Type	Required	Description
`expression`	string	yes	Cron expression (e.g. '0 9 * * 1-5' or '/5 * * *')
`timezone`	string	no	IANA timezone (default: UTC, e.g. America/New_York)
`count`	number	no	Number 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.

Catalog: https://klymax402.com/llms.txt
Full API reference: https://klymax402.com/llms-full.txt
Live stats: https://klymax402.com/stats

License

MIT

Cron Parser API

by io.github.Br0ski777

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

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Server URL

https://cron-parser.api.klymax402.com/mcp

Provider

Add in Claude

Claude opens with the name and URL filled in. You still confirm it there.

Claude Code

claude mcp add --transport http io.github.br0ski777-cron-parser https://cron-parser.api.klymax402.com/mcp

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "io.github.br0ski777-cron-parser": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://cron-parser.api.klymax402.com/mcp"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

Related skills

View all

Questions

How do I install Cron Parser API?: Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Cron Parser API need an API key?: No required environment variable is listed on this record.
What transport does Cron Parser API use?: Cron Parser API is reached over HTTP.
When was Cron Parser API last checked?: Last checked 2026-10-21. Parse, validate and explain cron expressions. Get next run times. x402 micropayment.

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

Tool	Method	Path	Price	Description
`schedule_parse_cron`	POST	`/api/parse`	$0.003	Parse a cron expression and get next run times

`schedule_parse_cron`

Parameters

Name	Type	Required	Description
`expression`	string	yes	Cron expression (e.g. '0 9 * * 1-5' or '/5 * * *')
`timezone`	string	no	IANA timezone (default: UTC, e.g. America/New_York)
`count`	number	no	Number 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.

Catalog: https://klymax402.com/llms.txt
Full API reference: https://klymax402.com/llms-full.txt
Live stats: https://klymax402.com/stats

License

MIT