Developer · Remote MCP server
Cron Explainer
Cron expression parser: explains any cron + returns next N fire times. Timezone-aware.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.IdoAzaCalls/cron-explainer- Version
- 0.1.2
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-04-23
- Updated
- 2026-04-23
- Publisher
- IdoAzaCalls (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/IdoAzaCalls) · how
- Website
- cron-explainer.cron-explainer-prod.workers.dev/
- Repository
- github.com/IdoAzaCalls/cron-explainer
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://cron-explainer.cron-explainer-prod.workers.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- cron-explainer 0.1.2 · protocol 2025-06-18
- Tools discovered
- 1:
explain_cron - Checked on
- 2026-10-05
How to connect Cron Explainer
Cron Explainer is a remote MCP server: there is nothing to install. Its endpoint is https://cron-explainer.cron-explainer-prod.workers.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Create StarterScaffold Starter Series projects and check release, deployment, security, and agent instructions. | Local · stdio |
| Credence - Epistemic GuardEpistemic guard for AI coding: tracks uncertain values and blocks writes until verified. | Local · stdio |
| Creedspace MCP ServerConstitutional-AI safety guardrails for any LLM - personas, constitutions, adjudication. | Local · stdio |
| CroftDeploy and host the apps your AI assistant builds - a real server, database, and shareable URL. | Remote · HTTPLive check: sign-in required |
| Cron MCPParse, describe, and compute next runs for cron expressions locally. No network and no key. | Local · stdio |
| Cron MCPCron-as-a-service MCP. Schedule prompts; when the cron fires we POST to your callback URL. | Remote · HTTPLive check: ✗ no handshake |
| Cron MCPMCP cron validator for AI agents; flags impossible schedules and other silent cron bugs. | Local · stdio |
| Cron Parser APIParse, validate and explain cron expressions. Get next run times. x402 micropayment. | Remote · SSELive check: ✗ no handshake |