Remote MCP · Endpoint
ai.kavel/kavel-mcp MCP server
No. ai.kavel/kavel-mcp answered an MCP handshake 3 hours ago.
UpLast checked 3 hours ago
Server URL
https://www.kavel.ai/api/mcp
The last check completed an MCP handshake.
- Registry name
- ai.kavel/kavel-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 642 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 14 checks
- Described by its publisher as
- Discover Kavel's AI photo/video generators, get tuned prompts, and open the right tool on kavel.ai.
- Website
- https://www.kavel.ai/
- Repository
- https://github.com/hanshs474/kavel-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 hours ago | Handshake completed | 642 ms |
| 9 days ago | Handshake completed | 203 ms |
| 10 days ago | Handshake completed | 222 ms |
| 11 days ago | Handshake completed | 150 ms |
| 12 days ago | Handshake completed | 147 ms |
| 14 days ago | Handshake completed | 324 ms |
| 14 days ago | Handshake completed | 161 ms |
| 15 days ago | Handshake completed | 187 ms |
| 17 days ago | Handshake completed | 198 ms |
| 19 days ago | Handshake completed | 156 ms |
| 21 days ago | Handshake completed | 188 ms |
| 24 days ago | Handshake completed | 197 ms |
| 26 days ago | Handshake completed | 232 ms |
| 28 days ago | Handshake completed | 131 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.
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.kavel/kavel-mcp and makes no claim about it beyond what these checks measured.