Remote MCP · Endpoint

CronSpell MCP server

No. CronSpell answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://cronspell.mike-tusa.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.mike-tusa.cronspell/cronspell
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
69 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Validate and explain cron expressions; list next/previous run times in any time zone, DST-aware.
Listing
From the official MCP registry (active).
Recent checks of CronSpell
CheckedResultHandshake
56 minutes agoHandshake completed69 ms
3 days agoHandshake completed189 ms
12 days agoHandshake completed182 ms
13 days agoHandshake completed104 ms
15 days agoHandshake completed115 ms
15 days agoHandshake completed75 ms
17 days agoHandshake completed80 ms
18 days agoHandshake completed64 ms
18 days agoHandshake completed101 ms
20 days agoHandshake completed129 ms
22 days agoHandshake completed51 ms
25 days agoHandshake completed73 ms
27 days agoHandshake completed83 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with CronSpell and makes no claim about it beyond what these checks measured.