Remote MCP · Endpoint

Cleanor MCP server

No. Cleanor answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://mcp.cleanor.app/mcp

The last check completed an MCP handshake.

Registry name
app.cleanor/cleanor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
611 ms
Tools exposed
22 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Zero-auth MCP: image optimize, cited storage/format data, and dev utilities LLMs get wrong.
Listing
From the official MCP registry (active).
Recent checks of Cleanor
CheckedResultHandshake
6 hours agoHandshake completed611 ms
2 days agoHandshake completed540 ms
4 days agoHandshake completed572 ms
5 days agoHandshake completed641 ms
7 days agoHandshake completed732 ms
8 days agoHandshake completed583 ms
9 days agoHandshake completed562 ms
12 days agoHandshake completed623 ms
13 days agoHandshake completed434 ms
15 days agoHandshake completed705 ms
16 days agoHandshake completed330 ms
17 days agoHandshake completed392 ms
18 days agoHandshake completed463 ms
19 days agoHandshake completed589 ms
20 days agoHandshake completed458 ms
21 days agoHandshake completed538 ms
22 days agoHandshake completed592 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 Cleanor and makes no claim about it beyond what these checks measured.