Remote MCP · Endpoint

Kaio MCP server

No. Kaio answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.website.prod.akaion.com/mcp/kaio

The last check completed an MCP handshake.

Registry name
com.akaion/kaio
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
146 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Find and book local businesses in Italy on Kaio: real free times, booking, online payment link.
Listing
From the official MCP registry (active).
Recent checks of Kaio
CheckedResultHandshake
1 hour agoHandshake completed146 ms
1 day agoHandshake completed152 ms
3 days agoHandshake completed138 ms
3 days agoHandshake completed152 ms
4 days agoHandshake completed221 ms
5 days agoHandshake completed158 ms
7 days agoHandshake completed141 ms
10 days agoHandshake completed145 ms
12 days agoHandshake completed163 ms
15 days agoHandshake completed142 ms
17 days agoHandshake completed140 ms
19 days agoHandshake completed152 ms
21 days agoHandshake completed141 ms
23 days agoHandshake completed145 ms
25 days agoHandshake completed179 ms

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

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