Skip to content

Cron Translator MCP server

com.crontoenglish/cron-translatorcrontoenglish.comstreamable-httpv0.1.0Scanned

Explain cron expressions in English, list next run times, and catch scheduling gotchas.

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Cron Translator MCP server can do

The Cron Translator MCP server is published by crontoenglish.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: next_cron_runs and build_cron), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • build_cronConvert an English schedule description into a standard five-field cron expression, then explain and validate the result.1 finding

    Why it is in this group

    • The description's first verb is "convert": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "build_cron" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "convert": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • next_cron_runsList the next run times for a cron expression in a specific timezone, with no prose.1 finding

    Why it is in this group

    • The name "next_cron_runs" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "next_cron_runs" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "next_cron_runs" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • explain_cronTranslate a cron expression into plain English, list its upcoming run times in a specific timezone, and report the gotchas that make schedules misfire.No findings

    Why it is in this group

    • The name "explain_cron" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:36 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://crontoenglish.com/api/mcp: tools/list returned 3 tools to an anonymous client, including next_cron_runs (write), build_cron (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "next_cron_runs" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "next_cron_runs" says "run": a word for a change.

    What this check looks for
  • The server marks "build_cron" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "convert": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http cron-translator https://crontoenglish.com/api/mcp
claude mcp add --transport http cron-translator https://crontoenglish.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__cron-translator__explain_cron"
    ],
    "ask": [
      "mcp__cron-translator__next_cron_runs",
      "mcp__cron-translator__build_cron"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as cron-translator. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.crontoenglish/cron-translator/verify?hash=7f8a1b30663456de4fddde40f135ce490b8698ba2595897bd69b51b2b4b008a6" | jq -e '.changed == false'

Pinned hash 7f8a1b306634, from Nov 10, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.crontoenglish/cron-translator/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.crontoenglish/cron-translator
[![Anlyon Radar](https://radar.anlyon.com/badge/com.crontoenglish/cron-translator.svg)](https://radar.anlyon.com/servers/com.crontoenglish/cron-translator)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:53 UTC.

Cron Translator MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Cron Translator MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Cron Translator MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Cron Translator MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Cron Translator MCP server have?

3 tools: 2 write, 1 read. next_cron_runs, build_cron and explain_cron.

Does the Cron Translator MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Cron Translator MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Cron Translator MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.