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).
Recent checks of io.github.cirralink-stack/kevaremesh
CheckedResultHandshake
1 hour agoHandshake completed367 ms
1 day agoHandshake completed439 ms
2 days agoHandshake completed323 ms
3 days agoHandshake completed350 ms
4 days agoHandshake completed376 ms
5 days agoHandshake completed293 ms
6 days agoHandshake completed300 ms
9 days agoHandshake completed279 ms
11 days agoHandshake completed582 ms
14 days agoHandshake completed401 ms
16 days agoHandshake completed378 ms
18 days agoHandshake completed303 ms
20 days agoHandshake completed450 ms
22 days agoHandshake completed378 ms
24 days agoHandshake completed368 ms
26 days agoHandshake completed243 ms
27 days agoHandshake completed365 ms
29 days agoHandshake completed382 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.