Remote MCP · Endpoint
io.github.cirralink-stack/kevaremesh MCP server
No. io.github.cirralink-stack/kevaremesh answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://ytqrligiuzhjkuotpiwb.supabase.co/functions/v1/kevaremesh-mcp
The last check completed an MCP handshake.
- Registry name
- io.github.cirralink-stack/kevaremesh
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-11-25
- Handshake latency
- 367 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Market-validated MCP capabilities with x402 paid execution.
- Listing
- From the official MCP registry (deprecated).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 367 ms |
| 1 day ago | Handshake completed | 439 ms |
| 2 days ago | Handshake completed | 323 ms |
| 3 days ago | Handshake completed | 350 ms |
| 4 days ago | Handshake completed | 376 ms |
| 5 days ago | Handshake completed | 293 ms |
| 6 days ago | Handshake completed | 300 ms |
| 9 days ago | Handshake completed | 279 ms |
| 11 days ago | Handshake completed | 582 ms |
| 14 days ago | Handshake completed | 401 ms |
| 16 days ago | Handshake completed | 378 ms |
| 18 days ago | Handshake completed | 303 ms |
| 20 days ago | Handshake completed | 450 ms |
| 22 days ago | Handshake completed | 378 ms |
| 24 days ago | Handshake completed | 368 ms |
| 26 days ago | Handshake completed | 243 ms |
| 27 days ago | Handshake completed | 365 ms |
| 29 days ago | Handshake completed | 382 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 io.github.cirralink-stack/kevaremesh and makes no claim about it beyond what these checks measured.