Koskamo

Tempo Cron Explorer MCP

A developer utility for inspecting five-field cron schedules in an explicit IANA timezone, providing matched field values, next UTC and local occurrences, and visible DST policy. It supports numeric wildcards, lists, ranges, and steps, and allows downloading JSON schedule reports.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Tempo Cron Explorer MCP logo, by ZovoCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-01Published by Zovo
MCP endpoint (Streamable HTTP)
https://cron-explorer.zovo.one/mcp
Vendor documentation

What you can do with it

  • Inspect cron schedules in explicit IANA timezones
  • View next UTC and local occurrences
  • Check DST policy impacts
  • Download JSON schedule reports

Source and maintenance

Community listingRegistry 1.0.0

Protocol and capabilities

Server
cron-explorer 1.0.0
MCP protocol
2025-06-18
Tools
1 advertised
Resources
1 advertised
Resource templates
1 advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "resources": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Use explore_cron to inspect five-field numeric cron schedules. Require an explicit IANA timezone and timestamp reference; do not infer either. Next occurrences are strictly after the reference. Describe the stated DST policy and five-year search horizon. Does not install or run jobs. Sunday is 0 or 7; follows Vixie cron star-prefix day semantics.

Tools

1 advertised

explore_cron — Explore cron schedule
Advertised by the server during the last successful anonymous check.
Advertised read-only

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 #.

explore_cron input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "expression",
    "timezone",
    "reference"
  ],
  "properties": {
    "count": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Number of next occurrences, e.g. 5. Defaults to 5; maximum 20."
    },
    "timezone": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1,
      "description": "Explicit IANA timezone, e.g. America/New_York, Europe/Warsaw, or UTC."
    },
    "reference": {
      "type": "string",
      "maxLength": 40,
      "description": "Explicit reference timestamp with seconds and Z or UTC offset, e.g. 2026-01-01T00:00:00Z. Runs are strictly after it."
    },
    "expression": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "Five-field numeric cron expression, e.g. 0 9 * * 1-5. Fields: minute hour day-of-month month day-of-week; Sunday is 0 or 7."
    }
  }
}
explore_cron output schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "expression",
    "timezone",
    "reference",
    "fields",
    "day_rule",
    "dst_policy",
    "occurrences",
    "requested",
    "found",
    "complete",
    "search_end",
    "warnings",
    "downloads",
    "request"
  ],
  "properties": {
    "found": {
      "type": "number"
    },
    "fields": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "field",
          "expression",
          "matches"
        ],
        "properties": {
          "field": {
            "type": "string"
          },
          "matches": {
            "type": "array",
            "items": {
              "type": "number"
            }
          },
          "expression": {
            "type": "string"
          }
        },
        "additionalProperties": false
      }
    },
    "request": {
      "type": "object",
      "required": [
        "expression",
        "timezone",
        "reference"
      ],
      "properties": {
        "count": {
          "type": "number"
        },
        "timezone": {
          "type": "string"
        },
        "reference": {
          "type": "string"
        },
        "expression": {
          "type": "string"
        }
      },
      "additionalProperties": false
    },
    "complete": {
      "type": "boolean"
    },
    "day_rule": {
      "type": "string"
    },
    "timezone": {
      "type": "string"
    },
    "warnings": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "downloads": {
      "type": "object",
      "required": [
        "report"
      ],
      "properties": {
        "report": {
          "type": "string"
        }
      },
      "additionalProperties": false
    },
    "reference": {
      "type": "string"
    },
    "requested": {
      "type": "number"
    },
    "dst_policy": {
      "type": "string"
    },
    "expression": {
      "type": "string"
    },
    "search_end": {
      "type": "string"
    },
    "occurrences": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "utc",
          "local",
          "offset"
        ],
        "properties": {
          "utc": {
            "type": "string"
          },
          "local": {
            "type": "string"
          },
          "offset": {
            "type": "string"
          }
        },
        "additionalProperties": false
      }
    }
  },
  "additionalProperties": false
}
explore_cron annotations
{
  "title": "Explore cron schedule",
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

1 advertised

cron-explorer-widget — Tempo Cron Explorer view

Advertised by the server during the last successful anonymous check.

Interactive view for Tempo Cron Explorer.

cron-explorer-widget URI
ui://widget/cron-explorer-v1-1.0.0-579792642cd5d7d354227ee5dbc40a05259fa94ffd797a7690f7b70825f97dd2.html

MIME type: text/html;profile=mcp-app

cron-explorer-widget-legacy — Tempo Cron Explorer view (previous versions)

Advertised by the server during the last successful anonymous check.

cron-explorer-widget-legacy URI template
ui://widget/cron-explorer-{version}.html

MIME type: text/html;profile=mcp-app

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
520 ms
95th percentile latency
520 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 520 ms · metadata changed · 1 tool(s), 1 resource(s), 1 resource template(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http tempo-cron-explorer-mcp https://cron-explorer.zovo.one/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add tempo-cron-explorer-mcp --url https://cron-explorer.zovo.one/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable tempo-cron-explorer-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "tempo-cron-explorer-mcp": {
      "url": "https://cron-explorer.zovo.one/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "tempo-cron-explorer-mcp": {
      "type": "streamableHttp",
      "url": "https://cron-explorer.zovo.one/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start tempo-cron-explorer-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "tempo-cron-explorer-mcp": {
      "type": "http",
      "url": "https://cron-explorer.zovo.one/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http tempo-cron-explorer-mcp https://cron-explorer.zovo.one/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "tempo-cron-explorer-mcp": {
      "url": "https://cron-explorer.zovo.one/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "tempo-cron-explorer-mcp": {
      "serverUrl": "https://cron-explorer.zovo.one/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Tempo Cron Explorer MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.