Remote MCP · Endpoint
ai.kaiv/bridge MCP server
No. ai.kaiv/bridge answered an MCP handshake 8 hours ago.
Up · key neededLast checked 8 hours ago
Server URL
https://api.kaiv.ai/api/bridge/manage/mcp
The handshake completes, but listing its tools needs credentials.
- Registry name
- ai.kaiv/bridge
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 202 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Turn any OpenAPI spec or API docs link into a hosted MCP server. Free Kaiva Bridge account.
- Repository
- https://github.com/ai-kaiva/bridge
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 8 hours ago | Handshake completed | 202 ms |
| 2 days ago | Handshake completed | 190 ms |
| 4 days ago | Handshake completed | 138 ms |
| 5 days ago | Handshake completed | 158 ms |
| 7 days ago | Handshake completed | 196 ms |
| 8 days ago | Handshake completed | 335 ms |
| 9 days ago | Handshake completed | 132 ms |
| 12 days ago | Handshake completed | 238 ms |
| 13 days ago | Handshake completed | 150 ms |
| 15 days ago | Handshake completed | 170 ms |
| 16 days ago | Handshake completed | 158 ms |
| 17 days ago | Handshake completed | 128 ms |
| 18 days ago | Handshake completed | 167 ms |
| 19 days ago | Handshake completed | 148 ms |
| 20 days ago | Handshake completed | 161 ms |
| 21 days ago | Handshake completed | 130 ms |
| 23 days ago | Handshake completed | 173 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 ai.kaiv/bridge and makes no claim about it beyond what these checks measured.