Remote MCP · Endpoint

Vyexa — video link to short clips MCP server

No. Vyexa — video link to short clips answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://vyexa.net/mcp

The last check completed an MCP handshake.

Registry name
net.vyexa/clips
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
310 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Turn a video link into vertical short clips with subtitles: create jobs, poll, get downloads.
Listing
From the official MCP registry (active).
Recent checks of Vyexa — video link to short clips
CheckedResultHandshake
1 hour agoHandshake completed310 ms
1 day agoHandshake completed309 ms
4 days agoHandshake completed310 ms
6 days agoHandshake completed319 ms
9 days agoHandshake completed300 ms
11 days agoHandshake completed306 ms
13 days agoHandshake completed335 ms
15 days agoHandshake completed352 ms
17 days agoHandshake completed564 ms
19 days agoHandshake completed309 ms
20 days agoHandshake completed311 ms
22 days agoHandshake completed339 ms
23 days agoHandshake completed303 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 Vyexa — video link to short clips and makes no claim about it beyond what these checks measured.