Remote MCP · Endpoint

Reka MCP server

No. Reka answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://mcp.reka.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.reka/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
318 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Understand your videos with Reka AI — search, ask questions, and extract insights.
Listing
From the official MCP registry (active).
Recent checks of Reka
CheckedResultHandshake
8 hours agoHandshake completed318 ms
2 days agoHandshake completed327 ms
4 days agoHandshake completed326 ms
5 days agoHandshake completed331 ms
7 days agoHandshake completed359 ms
8 days agoHandshake completed320 ms
9 days agoHandshake completed363 ms
12 days agoHandshake completed330 ms
13 days agoHandshake completed325 ms
15 days agoHandshake completed330 ms
16 days agoHandshake completed333 ms
17 days agoHandshake completed322 ms
18 days agoHandshake completed334 ms
19 days agoHandshake completed325 ms
20 days agoHandshake completed324 ms
21 days agoHandshake completed320 ms
23 days agoHandshake completed331 ms

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

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