Cron Parser API

by Br0ski777io.github.Br0ski777/cron-parserv1.1.0

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

  • Remote endpoint

Uptime

Checked  · every day

0%from 4 days of checks

Up without downtime on 0 of 4 days with data; down 5626 minutes in all, the longest 1440 minutes on 1 November.

  • No downtime
  • Degraded
  • Down over 5 minutes
  • No data
  • Not checked yet

How far each check got

  • Reached the address 0.0%
  • Completed the handshake 0.0%
  • Listed its tools 0.0%
Every day
DayResultChecksMedian
3 Nov (today)Down 1427 minutes1–
2 NovDown 1440 minutes1of 1–
1 NovDown 1440 minutes1of 1–
31 OctDown 1319 minutes13–

A failure counts as down time only when a second check five minutes later fails too. How we check

Connect to the publisher's own endpoint

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "cron-parser": {
      "url": "https://cron-parser.api.klymax402.com/mcp"
    }
  }
}
For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server Cron Parser API (`io.github.Br0ski777/cron-parser`)

Its page: https://plug.directory/servers/io.github.Br0ski777/cron-parser

It runs on the publisher's servers; the client connects to its URL.

Use the section for the person's client.

## Claude Desktop

Paste into Settings › Connectors › Add custom connector:

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

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport sse cron-parser https://cron-parser.api.klymax402.com/mcp
```

## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA

Merge into the place for the person's client:

- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project

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

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "cron-parser": {
      "type": "sse",
      "url": "https://cron-parser.api.klymax402.com/mcp"
    }
  }
}
```

## Zed

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Cline, AnythingLLM, Augment Code

Merge into the place for the person's client:

- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)

```json
{
  "mcpServers": {
    "cron-parser": {
      "type": "sse",
      "url": "https://cron-parser.api.klymax402.com/mcp"
    }
  }
}
```

## Continue

Merge into ~/.continue/config.yaml:

```yaml
mcpServers:
  - name: "cron-parser"
    type: sse
    url: "https://cron-parser.api.klymax402.com/mcp"
```

## Goose

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Codex

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Agenvoy

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

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

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.

From the publisher's entry in the Official MCP Registry (the registry entry). Report a problem