cron-check
Related Servers
Alternatives to cron-check
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceParses cron expressions, returns next fire times, and provides an English description.MIT
- AlicenseNot gradedqualityBmaintenanceProvides tools to parse and describe cron expressions in plain English, and compute future run times.137 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to parse, validate, explain, and preview cron expressions, surfacing common silent bugs before deployment.456 npmMIT
- AlicenseAqualityDmaintenanceEnables exploration, explanation, and management of crontab entries, including translating cron expressions into plain English and calculating upcoming execution times.84MIT
- AlicenseNot gradedqualityDmaintenanceParse, validate, and explain cron expressions with pay-per-call via x402 (USDC on Base L2), returning next run times in any timezone.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to convert schedule text to cron expressions, describe cron in natural language, and compute upcoming run times.MIT
TDQS
Scored across 3 tools
Each tool serves a distinct purpose: conversion between schedulers, explanation/validation, and computing future runs. There is no overlap in functionality, and an agent can easily select the appropriate tool based on the task.
All tools follow a consistent verb_noun pattern (convert_cron, explain_cron, next_runs). The naming is clear and predictable, with 'cron' as the subject and a specific action verb prefix.
With exactly 3 tools, the server is tightly scoped to core cron operations: conversion, explanation, and scheduling. Each tool is essential and there is no bloat or unnecessary redundancy.
The tool set covers the full lifecycle of working with cron expressions: understanding (explain), adapting (convert), and planning (next_runs). No obvious missing operations exist for the server's stated purpose.