Remote MCP · Endpoint

OpenVidu Docs MCP server

No. OpenVidu Docs answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://docs-mcp.openvidu.io/mcp

The last check completed an MCP handshake.

Registry name
io.openvidu/docs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
304 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
The official OpenVidu documentation, per version, for coding agents.
Listing
From the official MCP registry (active).
Recent checks of OpenVidu Docs
CheckedResultHandshake
2 hours agoHandshake completed304 ms
1 day agoHandshake completed306 ms
4 days agoHandshake completed861 ms
6 days agoHandshake completed298 ms
9 days agoHandshake completed289 ms
11 days agoHandshake completed283 ms
13 days agoHandshake completed336 ms
15 days agoHandshake completed343 ms
17 days agoHandshake completed330 ms
19 days agoHandshake completed298 ms
20 days agoHandshake completed913 ms
22 days agoHandshake completed892 ms
23 days agoHandshake completed280 ms

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

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