Remote MCP · Endpoint

KAI Router MCP server

No. KAI Router answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gycvbmliobjydcdghhtj.supabase.co/functions/v1/kai-x402-router/mcp

The last check completed an MCP handshake.

Registry name
io.github.kingdt1991-netizen/kai-router
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
349 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find pay-per-call x402 tools (USDC on Base) for any task, ranked by relevance and real demand.
Listing
From the official MCP registry (active).
Recent checks of KAI Router
CheckedResultHandshake
2 hours agoHandshake completed349 ms
1 day agoHandshake completed282 ms
2 days agoHandshake completed388 ms
2 days agoHandshake completed278 ms
4 days agoHandshake completed219 ms
7 days agoHandshake completed287 ms
9 days agoHandshake completed256 ms
12 days agoHandshake completed398 ms
14 days agoHandshake completed220 ms
16 days agoHandshake completed253 ms
18 days agoHandshake completed214 ms
20 days agoHandshake completed234 ms
22 days agoHandshake completed223 ms
23 days agoHandshake completed196 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 KAI Router and makes no claim about it beyond what these checks measured.