Remote MCP · Endpoint

Kleap MCP server

No. Kleap answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://kleap.co/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.kleaphq/kleap
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
547 ms
Tools exposed
34 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Build, edit, publish, and manage websites and web apps with Kleap hosting, domains, and analytics.
Listing
From the official MCP registry (active).
Recent checks of Kleap
CheckedResultHandshake
1 hour agoHandshake completed547 ms
2 days agoHandshake completed174 ms
4 days agoHandshake completed548 ms
5 days agoHandshake completed541 ms
7 days agoHandshake completed280 ms
8 days agoHandshake completed308 ms
9 days agoHandshake completed540 ms
12 days agoHandshake completed660 ms
13 days agoHandshake completed569 ms
15 days agoHandshake completed532 ms
17 days agoHandshake completed750 ms
18 days agoHandshake completed540 ms
19 days agoHandshake completed534 ms
20 days agoHandshake completed555 ms
20 days agoHandshake completed150 ms
21 days agoHandshake completed461 ms
23 days agoHandshake completed166 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 Kleap and makes no claim about it beyond what these checks measured.