Tempo Cron Explorer
Server Details
Cron runs across timezones
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 1 tool
With a single tool there is no cross-tool ambiguity to resolve, so misselection risk is essentially zero. The only caveat is that one tool bundles three modes (expression explanation, next-run projection, DST inspection) whose selection depends on argument shape rather than distinct tool names.
The lone name, explore_cron, follows a clean verb_noun snake_case convention that matches the broader MCP ecosystem norm. There is no competing convention to create inconsistency.
One tool is thin for a server, though the domain (cron expression analysis) is narrow enough that a single entry point is defensible and the description is dense with capability. Splitting explain vs. next-runs vs. DST could have improved clarity, but the count is not a serious mismatch.
The surface covers the core domain well: explaining a five-field expression, projecting up to 20 future runs in a named timezone, and surfacing DST transitions, with search bounded at 1,830 days. Gaps are acknowledged and reasonable (no execution, no macros/seconds/L/W/#), though there is no dedicated validation-only path for malformed expressions.
Available Tools
1 toolexplore_cronExplore cron scheduleARead-onlyInspect
Use this when you want to explain a five-field cron expression, find its next runs in an IANA timezone, or inspect daylight-saving transitions. Supports numeric *, lists, ascending ranges, and steps. Requires an explicit timestamp reference. Searches up to 1,830 days and returns up to 20 runs strictly after it. Does not execute jobs or support names, macros, seconds, years, ?, L, W, or #.
Inputs: timezone (required), reference (required), expression (required), count. Returns: found, fields, request, complete, +10 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Find meeting times across TZs
Validates cron expressions and finds DST bugs that make jobs silently skip or double-fire.
Deterministic time tools for AI agents: timezone conversion, business-day math, cron interpretation.
Explain cron expressions in English, list next run times, and catch scheduling gotchas.
Related MCP Servers
- AlicenseAqualityCmaintenanceExplains cron expressions in plain English, checks them for errors and gotchas, lists next run times in any time zone, and converts between Unix cron, GitHub Actions, Kubernetes, AWS EventBridge, Quartz and Spring dialects.31MIT
- AlicenseNot gradedqualityDmaintenanceValidates cron expressions and computes DST-correct next-fire times against real IANA timezone data, flagging schedules that silently skip a spring-forward run or double-fire on fall-back. Also surfaces the POSIX day-of-month/day-of-week OR semantics and other semantic footguns before a job ships.MIT
- AlicenseNot gradedqualityCmaintenanceParse, validate, and explain cron expressions with pay-per-call via x402 (USDC on Base L2), returning next run times in any timezone.1MIT
- AlicenseAqualityDmaintenanceAccess the time in any timezone and get the current local time142MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.