mcpbeat Sign in

Tempo Cron Explorer MCP Server

answering

Tempo Cron Explorer is answering right now. Last checked 11 min ago. It exposes 1 tools.

Cron runs across timezones

Uptime history 67 hours of history
67 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
210 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Tempo Cron Explorer every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add cron-explorer --transport http https://cron-explorer.zovo.one/mcp
Settings → Connectors → Add custom connector, then paste this address
https://cron-explorer.zovo.one/mcp
~/.codex/config.toml
[mcp_servers.cron-explorer]
url = "https://cron-explorer.zovo.one/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "cron-explorer": {
      "url": "https://cron-explorer.zovo.one/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "cron-explorer": {
      "type": "http",
      "url": "https://cron-explorer.zovo.one/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

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

Endpoints

URLTransportStateLatencyChecked
https://cron-explorer.zovo.one/mcp streamable-http answering 197 ms 11 min ago

Alternatives to Tempo Cron Explorer

same job, measured the same way
Cron Explainer
by idoazacalls

Cron expression parser: explains any cron + returns next N fire times. Timezone-aware.

1 tools answering
Time
by rog0x

Timezone, dates, cron, timestamps for AI agents

17 installs/wk local only
Cron Tools
by basitalisandhu

Parse, explain and validate 5-field cron expressions and list upcoming runs in a time zone.

local only
CronSpell
by workers-mike-tusa-cronspell

Validate and explain cron expressions; list next/previous run times in any time zone, DST-aware.

4 tools answering
MCP Time
by infoinlet-marketplace

Time & date for AI agents — timezones, conversion, date math, diffs, cron, business days.

6 installs/wk local only
Zovo Meeting Planner
by theluckystrike

Find meeting times across TZs

2 tools answering
Timeapi MCP
by mrfentmen

TimeAPI timezone conversion.

15 installs/wk local only
Timezone MCP
by mukundakatta

IANA timezone conversions with real DST rules.

13 installs/wk local only

Tempo Cron Explorer — questions

Answers built from our own checks of this server.

What can Tempo Cron Explorer do?
It exposes 1 tools, read directly from the server on our last check. Among them: explore_cron. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Tempo Cron Explorer working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 210 ms. The bar chart above shows every period we have measured.
How do I connect Tempo Cron Explorer?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Tempo Cron Explorer need an API key?
No. Tempo Cron Explorer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Tempo Cron Explorer?
It answers our handshake in 210 ms on average, which is faster than 70% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.