Remote MCP · Endpoint
Kaiva Bridge MCP server
No. Kaiva Bridge answered an MCP handshake 2 hours ago.
Up · key neededLast checked 2 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
- 397 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Turn any OpenAPI/Swagger spec or REST API docs link into a managed MCP server. Free account.
- Repository
- https://github.com/ai-kaiva/bridge
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 397 ms |
| 1 day ago | Handshake completed | 172 ms |
| 3 days ago | Handshake completed | 221 ms |
| 3 days ago | Handshake completed | 187 ms |
| 4 days ago | Handshake completed | 180 ms |
| 5 days ago | Handshake completed | 173 ms |
| 7 days ago | Handshake completed | 8.45 s |
| 10 days ago | Handshake completed | 413 ms |
| 12 days ago | Handshake completed | 140 ms |
| 15 days ago | Handshake completed | 172 ms |
| 17 days ago | Handshake completed | 187 ms |
| 19 days ago | Handshake completed | 314 ms |
| 21 days ago | Handshake completed | 202 ms |
| 23 days ago | Handshake completed | 190 ms |
| 25 days ago | Handshake completed | 138 ms |
| 26 days ago | Handshake completed | 158 ms |
| 28 days ago | Handshake completed | 196 ms |
| 29 days ago | Handshake completed | 335 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 Kaiva Bridge and makes no claim about it beyond what these checks measured.