Remote MCP · Endpoint

Vyexa — video link to short clips MCP server

No. Vyexa — video link to short clips answered an MCP handshake 32 minutes ago.

UpLast checked 32 minutes 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
296 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 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
32 minutes agoHandshake completed296 ms
3 days agoHandshake completed302 ms
13 days agoHandshake completed306 ms
13 days agoHandshake completed318 ms
15 days agoHandshake completed316 ms
16 days agoHandshake completed420 ms
17 days agoHandshake completed316 ms
18 days agoHandshake completed318 ms
18 days agoHandshake completed306 ms
20 days agoHandshake completed310 ms
22 days agoHandshake completed309 ms
25 days agoHandshake completed310 ms
27 days agoHandshake completed319 ms
29 days agoHandshake completed300 ms

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

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.