Tempo Cron Explorer
REMOTE · CRON-EXPLORER.ZOVO.ONE
Cron runs across timezones
Available components
Last scanned (21 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 324 tokens (~162/item across 2 items; 1 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Probed https://cron-explorer.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f1d3599c3f46a40e13be60f57e8ec796 |
| SANs: zovo.one, cron-explorer.zovo.one, *.cron-explorer.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cron-explorer.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cron-explorer.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://cron-explorer.zovo.one/mcp | HTTPS enforced | 301 | https://cron-explorer.zovo.one/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
explore_cron Explore cron schedule ~236
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 #.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of next occurrences, e.g. 5. Defaults to 5; maximum 20. |
| expression | string | yes | 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. |
| reference | string | yes | Explicit reference timestamp with seconds and Z or UTC offset, e.g. 2026-01-01T00:00:00Z. Runs are strictly after it. |
| timezone | string | yes | Explicit IANA timezone, e.g. America/New_York, Europe/Warsaw, or UTC. |
| Name | Type | Req | Description |
|---|---|---|---|
| complete | boolean | yes | – |
| day_rule | string | yes | – |
| downloads | object | yes | – |
| dst_policy | string | yes | – |
| expression | string | yes | – |
| fields | array | yes | – |
| found | number | yes | – |
| occurrences | array | yes | – |
| reference | string | yes | – |
| request | object | yes | – |
| requested | number | yes | – |
| search_end | string | yes | – |
| timezone | string | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the Tempo Cron Explorer MCP server?
Tempo Cron Explorer is a hosted endpoint at https://cron-explorer.zovo.one/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · cron-explorer.zovo.one
claude mcp add --transport http theluckystrike-cron-explorer 'https://cron-explorer.zovo.one/mcp'
What is the Tempo Cron Explorer MCP server?
Tempo Cron Explorer is an MCP server listed in the public MCP registry as io.github.theluckystrike/cron-explorer. Cron runs across timezones. This page covers its hosted endpoint (https://cron-explorer.zovo.one/mcp).
Is the Tempo Cron Explorer MCP server safe to use?
Tempo Cron Explorer scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tempo Cron Explorer MCP server expose?
Tempo Cron Explorer exposes 1 tool: explore_cron. Their descriptions and schemas cost roughly 236 tokens of context every time the server is loaded.
Does the Tempo Cron Explorer MCP server require authentication?
No. We connected to Tempo Cron Explorer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tempo Cron Explorer MCP server still maintained?
Tempo Cron Explorer is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.