cron-translator

endpoint

https://crontoenglish.com/api/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is cron-translator live?

Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.

Is cron-translator free to use?

Yes — the hub reached it with no key and no payment.

What tools does cron-translator have?

3 tools: next_cron_runs, explain_cron, build_cron.

Is cron-translator safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• next_cron_runs reads unknown never probed

  List the next run times for a cron expression in a specific timezone, with no prose. Use this when the only question is "when does this next fire" — for example to check whether a job will run before a deadline, or to show a user their upcoming schedule. Do not compute these dates yourself: weekday arithmetic, month lengths, and daylight-saving shifts make manual calculation unreliable. Returns each run as a UTC ISO 8601 instant plus a local wall-clock rendering in the requested timezone. Refuses Quartz-only syntax (L, W, #, ?) rather than guessing.

  mcp-tool

  12345678910111213141516171819202122232425

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "expression"
    ],
    "properties": {
      "count": {
        "type": "integer",
        "default": 5,
        "maximum": 25,
        "minimum": 1,
        "description": "How many upcoming run times to return. 1-25, default 5."
      },
      "timezone": {
        "type": "string",
        "default": "UTC",
        "description": "IANA timezone name, for example \"UTC\", \"America/New_York\", or \"Europe/Berlin\". Cron expressions carry no timezone of their own, so this decides when the schedule actually fires. Defaults to UTC."
      },
      "expression": {
        "type": "string",
        "description": "A standard five-field cron expression: \"minute hour day-of-month month day-of-week\", for example \"0 9 * * 1-5\". Accepts *, numbers, ranges (9-17), lists (1,15), steps (*/5), three-letter month and day names (JAN, MON), and the @daily, @hourly, @weekly, @monthly, @yearly macros. A six-field expression is accepted and its leading seconds field is reported as non-standard."
      }
    }
  }

  arguments 25 lines copy
• explain_cron reads unknown 3h ago

  Translate a cron expression into plain English, list its upcoming run times in a specific timezone, and report the gotchas that make schedules misfire. Use this whenever a cron expression needs to be read, verified, or explained — and prefer it over reasoning about the expression directly. Cron has several counter-intuitive rules that are easy to get wrong: day-of-month and day-of-week are combined with OR (not AND) when both are set, steps like */7 do not divide their field evenly, dates like February 30 never fire at all, and daylight-saving transitions skip or repeat runs. This tool checks all of them. Returns the normalised expression, a one-sentence description, a per-field breakdown, a list of warnings with severity and a fix for each, the next run times as both UTC ISO 8601 instants and local wall-clock strings, and an approximate runs-per-day figure.

  mcp-tool

  12345678910111213141516171819202122232425

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "expression"
    ],
    "properties": {
      "count": {
        "type": "integer",
        "default": 5,
        "maximum": 25,
        "minimum": 1,
        "description": "How many upcoming run times to return. 1-25, default 5."
      },
      "timezone": {
        "type": "string",
        "default": "UTC",
        "description": "IANA timezone name, for example \"UTC\", \"America/New_York\", or \"Europe/Berlin\". Cron expressions carry no timezone of their own, so this decides when the schedule actually fires. Defaults to UTC."
      },
      "expression": {
        "type": "string",
        "description": "A standard five-field cron expression: \"minute hour day-of-month month day-of-week\", for example \"0 9 * * 1-5\". Accepts *, numbers, ranges (9-17), lists (1,15), steps (*/5), three-letter month and day names (JAN, MON), and the @daily, @hourly, @weekly, @monthly, @yearly macros. A six-field expression is accepted and its leading seconds field is reported as non-standard."
      }
    }
  }

  arguments 25 lines copy
• build_cron reads unknown 3h ago

  Convert an English schedule description into a standard five-field cron expression, then explain and validate the result. Use this when a user describes a schedule in words and needs the expression. This is a RULE-BASED converter, not a language model: it handles a fixed grammar and returns an error listing the supported phrasings when a phrase falls outside it. That refusal is deliberate — a plausible-looking wrong schedule is worse than no answer. If a phrase is rejected, rephrase it into one of the supported shapes and call again. Returns the expression, which rule matched, any words the rules did not use (check these — leftover words may mean the phrase was misread), the English description of the result, warnings, and the next run times.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "phrase"
    ],
    "properties": {
      "phrase": {
        "type": "string",
        "description": "An English schedule description, for example \"every weekday at 9am\" or \"on the 1st of every month at midnight\". Times accept 24-hour (\"14:30\"), 12-hour (\"2:30pm\"), \"midnight\", and \"noon\"."
      },
      "timezone": {
        "type": "string",
        "default": "UTC",
        "description": "IANA timezone name, for example \"UTC\", \"America/New_York\", or \"Europe/Berlin\". Cron expressions carry no timezone of their own, so this decides when the schedule actually fires. Defaults to UTC."
      }
    }
  }

  arguments 18 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.