Remote MCP · Endpoint

Rokha MCP server

No. Rokha answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://rokha.ai/mcp/jsonrpc

The last check completed an MCP handshake.

Registry name
ai.rokha/rokha
Transport
Streamable HTTP
Protocol negotiated
2025-11-25
Handshake latency
242 ms
Tools exposed
290 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Search a registry of agent skills and MCP servers, then run them for real. No install, traced.
Listing
From the official MCP registry (active).
Recent checks of Rokha
CheckedResultHandshake
2 hours agoHandshake completed242 ms
2 days agoHandshake completed263 ms
4 days agoHandshake completed223 ms
6 days agoHandshake completed229 ms
8 days agoHandshake completed256 ms
9 days agoHandshake completed221 ms
11 days agoHandshake completed617 ms
12 days agoHandshake completed224 ms
14 days agoHandshake completed185 ms
16 days agoHandshake completed216 ms
17 days agoHandshake completed220 ms
19 days agoHandshake completed185 ms
20 days agoHandshake completed224 ms
21 days agoHandshake completed214 ms
22 days agoHandshake completed338 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

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 Rokha and makes no claim about it beyond what these checks measured.