Remote MCP · Endpoint

api.video MCP by usefulapi MCP server

No. api.video MCP by usefulapi answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://apivideo.usefulapi.io/mcp

The last check completed an MCP handshake.

Registry name
io.usefulapi/apivideo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
343 ms
Tools exposed
15 tools
Uptime, last 30 days
72.2% from 18 checks
Described by its publisher as
Manage videos and live streams, inspect captions, players and webhooks, and read play analytics.
Listing
From the official MCP registry (active).
Recent checks of api.video MCP by usefulapi
CheckedResultHandshake
1 hour agoHandshake completed343 ms
2 days agoHandshake completed292 ms
4 days agoHandshake completed185 ms
6 days agoHandshake completed234 ms
7 days agoHandshake completed200 ms
9 days agoHandshake completed253 ms
10 days agoFailed - the check failed for an unclassified reason—
11 days agoHandshake completed367 ms
14 days agoFailed - the check failed for an unclassified reason—
15 days agoFailed - the check failed for an unclassified reason—
17 days agoHandshake completed323 ms
19 days agoHandshake completed153 ms
20 days agoHandshake completed171 ms
21 days agoFailed - the check failed for an unclassified reason—
22 days agoHandshake completed254 ms
22 days agoHandshake completed181 ms
23 days agoHandshake completed219 ms
25 days agoFailed - the check failed for an unclassified reason—

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

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 api.video MCP by usefulapi and makes no claim about it beyond what these checks measured.