Remote MCP · Endpoint

402cron MCP server

No. 402cron answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://402cron.com/mcp

The last check completed an MCP handshake.

Registry name
com.402cron/402cron
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
90 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Paid cron for AI agents: we call your https URL on schedule, signed. No account, paid with x402.
Listing
From the official MCP registry (active).
Recent checks of 402cron
CheckedResultHandshake
1 hour agoHandshake completed90 ms
2 days agoHandshake completed70 ms
4 days agoHandshake completed71 ms
5 days agoHandshake completed142 ms
7 days agoHandshake completed59 ms
8 days agoHandshake completed261 ms
9 days agoHandshake completed272 ms
12 days agoHandshake completed65 ms
13 days agoHandshake completed69 ms
15 days agoHandshake completed365 ms
16 days agoHandshake completed64 ms
17 days agoHandshake completed25 ms
18 days agoHandshake completed58 ms
19 days agoHandshake completed63 ms
20 days agoHandshake completed51 ms
21 days agoHandshake completed52 ms
22 days agoHandshake completed61 ms

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

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 402cron and makes no claim about it beyond what these checks measured.