Remote MCP · Endpoint

Refs MCP server

No. Refs answered an MCP handshake 48 minutes ago.

UpLast checked 48 minutes ago

Server URL

https://refs.video/mcp

The last check completed an MCP handshake.

Registry name
video.refs/refs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
104 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
4,100 launch videos measured shot by shot. Free account to search; Pro for blueprints and plans.
Listing
From the official MCP registry (active).
Recent checks of Refs
CheckedResultHandshake
48 minutes agoHandshake completed104 ms
10 days agoHandshake completed150 ms
10 days agoHandshake completed104 ms
11 days agoHandshake completed79 ms
12 days agoHandshake completed100 ms
14 days agoHandshake completed59 ms
14 days agoHandshake completed76 ms
15 days agoHandshake completed68 ms
17 days agoHandshake completed178 ms
19 days agoCredentials required—
21 days agoCredentials required—
24 days agoHandshake completed58 ms
26 days agoHandshake completed75 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 Refs and makes no claim about it beyond what these checks measured.