Remote MCP · Endpoint

VideoUpscaler MCP server

No. VideoUpscaler answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://videoupscaler.co/api/mcp

The last check completed an MCP handshake.

Registry name
co.videoupscaler/video-upscaler
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
151 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI video upscaler: enhance videos to 1080p, 2K or 4K and track upscaling tasks.
Listing
From the official MCP registry (active).
Recent checks of VideoUpscaler
CheckedResultHandshake
34 minutes agoHandshake completed151 ms
9 days agoHandshake completed205 ms
10 days agoHandshake completed136 ms
11 days agoHandshake completed143 ms
12 days agoHandshake completed203 ms
14 days agoHandshake completed131 ms
14 days agoHandshake completed134 ms
15 days agoHandshake completed1.75 s
17 days agoHandshake completed132 ms
19 days agoHandshake completed157 ms
21 days agoHandshake completed160 ms
24 days agoCredentials required—
26 days agoCredentials required—
28 days agoCredentials required—

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

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