Remote MCP · Endpoint

Cronus UI MCP server

No. Cronus UI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://aicronus.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.pedrogbraz/cronus-ui
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
157 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search, install, compose, add-page, and theme Cronus UI from the live registry.
Listing
From the official MCP registry (active).
Recent checks of Cronus UI
CheckedResultHandshake
1 hour agoHandshake completed157 ms
2 days agoHandshake completed1.24 s
4 days agoHandshake completed1.20 s
5 days agoHandshake completed129 ms
7 days agoHandshake completed95 ms
8 days agoHandshake completed122 ms
9 days agoHandshake completed68 ms
12 days agoHandshake completed701 ms
13 days agoHandshake completed80 ms
15 days agoHandshake completed80 ms
17 days agoHandshake completed63 ms
18 days agoHandshake completed62 ms
19 days agoHandshake completed91 ms
20 days agoHandshake completed109 ms
20 days agoHandshake completed997 ms
21 days agoHandshake completed82 ms
23 days agoHandshake completed133 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 Cronus UI and makes no claim about it beyond what these checks measured.