Remote MCP · Endpoint

Clearcrawl MCP server

No. Clearcrawl answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://agentreader.onrender.com/clearcrawl/mcp

The last check completed an MCP handshake.

Registry name
io.github.clearcrawl/clearcrawl
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
257 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Any URL to clean markdown/JSON; PDF, XLSX, CSV, DOCX to text and tables. Free tier for agents.
Listing
From the official MCP registry (active).
Recent checks of Clearcrawl
CheckedResultHandshake
4 days agoHandshake completed257 ms
4 days agoHandshake completed173 ms
5 days agoHandshake completed142 ms
7 days agoHandshake completed173 ms
8 days agoHandshake completed159 ms
9 days agoHandshake completed121 ms
10 days agoHandshake completed272 ms
11 days agoHandshake completed344 ms
12 days agoHandshake completed146 ms
15 days agoHandshake completed127 ms
18 days agoHandshake completed322 ms
20 days agoHandshake completed257 ms
22 days agoHandshake completed143 ms
24 days agoHandshake completed243 ms

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

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