accueil / serveurs / Dev & Code / com.crontoenglish/cron-translator
com.crontoenglish/cron-translator
serveur MCP (Model Context Protocol) · cron-translator 0.1.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.crontoenglish/cron-translator est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.crontoenglish/cron-translator » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 3 outils
- build_cron≈ 390 tokens
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.
Paramètres, retour & exemple (2)
Paramètresphrase· string · requis
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· string · optionnel
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.
Exemple d'appel{"name": "build_cron", "arguments": {"phrase": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - explain_cron≈ 501 tokens
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.
Paramètres, retour & exemple (3)
Paramètrescount· integer · optionnel
How many upcoming run times to return. 1-25, default 5.timezone· string · optionnel
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· string · requis
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.
Exemple d'appel{"name": "explain_cron", "arguments": {"expression": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - next_cron_runs≈ 422 tokens
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.
Paramètres, retour & exemple (3)
Paramètrescount· integer · optionnel
How many upcoming run times to return. 1-25, default 5.timezone· string · optionnel
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· string · requis
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.
Exemple d'appel{"name": "next_cron_runs", "arguments": {"expression": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».