Skip to main content
Glama

Server Details

Cron runs across timezones

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness4/5

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 tool
explore_cronExplore cron scheduleA
Read-only
Inspect

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

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Explains 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.
      3
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Validates 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Parse, validate, and explain cron expressions with pay-per-call via x402 (USDC on Base L2), returning next run times in any timezone.
      1
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources