Remote MCP · Endpoint

klanex MCP server

No. klanex answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://api.klanexai.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.chrassy/klanex
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
368 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Reliable async execution for agent tool calls: schema gating, retries, idempotency, audit trail.
Listing
From the official MCP registry (active).
Recent checks of klanex
CheckedResultHandshake
7 hours agoHandshake completed368 ms
2 days agoHandshake completed393 ms
4 days agoHandshake completed380 ms
5 days agoHandshake completed120 ms
7 days agoHandshake completed113 ms
8 days agoHandshake completed351 ms
9 days agoHandshake completed115 ms
12 days agoHandshake completed411 ms
13 days agoHandshake completed349 ms
15 days agoHandshake completed378 ms
16 days agoHandshake completed353 ms
17 days agoHandshake completed355 ms
19 days agoHandshake completed110 ms
19 days agoHandshake completed375 ms
20 days agoHandshake completed114 ms
21 days agoHandshake completed346 ms
22 days agoHandshake completed366 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 klanex and makes no claim about it beyond what these checks measured.