Remote MCP · Endpoint
ai.kaiv/can-i-use MCP server
No. ai.kaiv/can-i-use answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b
The last check completed an MCP handshake.
- Registry name
- ai.kaiv/can-i-use
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 280 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Browser support for web features, live from caniuse. From which version, and is it safe to ship?
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 280 ms |
| 1 day ago | Handshake completed | 170 ms |
| 3 days ago | Handshake completed | 166 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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 ai.kaiv/can-i-use and makes no claim about it beyond what these checks measured.