Remote MCP · Endpoint

cloro MCP server

No. cloro answered an MCP handshake 23 hours ago.

UpLast checked 23 hours ago

Server URL

https://mcp.cloro.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.cloro/cloro
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
41 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Scrape AI answer engines and Google Search/News with country and state-level geo-targeting.
Listing
From the official MCP registry (active).
Recent checks of cloro
CheckedResultHandshake
23 hours agoHandshake completed41 ms
3 days agoHandshake completed49 ms
4 days agoHandshake completed49 ms
6 days agoHandshake completed69 ms
7 days agoHandshake completed45 ms
8 days agoHandshake completed49 ms
10 days agoHandshake completed57 ms
12 days agoHandshake completed55 ms
14 days agoHandshake completed72 ms
16 days agoHandshake completed47 ms
17 days agoHandshake completed46 ms
18 days agoHandshake completed37 ms
19 days agoHandshake completed44 ms
20 days agoHandshake completed64 ms
20 days agoHandshake completed43 ms
22 days agoHandshake completed39 ms
23 days agoHandshake completed49 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 cloro and makes no claim about it beyond what these checks measured.