VideoUpscaler
REMOTE · VIDEOUPSCALER.CO
AI video upscaler: enhance videos to 1080p, 2K or 4K and track upscaling tasks.
Available components
Last scanned (5 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 686 tokens (~137/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- “upscale_video” reworded the description of “ops” cosmetic
- 3 Nov 26 +1
- “upscale_video” added an optional parameter “webhook_url” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 2 Nov 26 0
- Schema quality: pass → fail ▼ functional
- Tool coverage: 50% → 56% ▲ functional
- “upscale_video” added an optional parameter “ops” cosmetic
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://videoupscaler.co/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=videoupscaler.co | CN=YR1,O=Let's Encrypt,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 51e1815eabfe3fda9b4cbc9b2b9b5f5d445 |
| SANs: videoupscaler.co | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of videoupscaler.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| videoupscaler.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://videoupscaler.co/.well-known/oauth-protected-resource/api/mcp"
Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://videoupscaler.co/.well-known/oauth-protected-resource/api/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://pagead2.googlesyndication.com https://www.googletagmanager.com https://www.clarity.ms https://scripts.clarity.ms https://cdn.promotekit.com https://affonso.io https://openpanel.dev https://client.crisp.chat https://embed.tawk.to https://va.vercel-scripts.com https://js.stripe.com https://www.paypal.com https://accounts.google.com https://*.posthog.com; style-src 'self' 'unsafe-inline' https://accounts.google.com; img-src 'self' data: blob: https:; media-src 'self' blob: data: https://storage.videoupscaler.co https://storage.imageupscaler.run https://cdn-vu.a1d.ai https://*.r2.cloudflarestorage.com; connect-src 'self' https: wss:; font-src 'self' https://fonts.gstatic.com; frame-src 'self' https://js.stripe.com https://www.paypal.com https://td.doubleclick.net https://www.google.com; worker-src 'self' blob:; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://videoupscaler.co/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://videoupscaler.co/api/mcp |
| Authorisation server | https://videoupscaler.co/api/auth |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://videoupscaler.co/api/mcp | Verified | 200 | |
| http (plaintext) | http://videoupscaler.co/api/mcp | HTTPS enforced | 308 | https://videoupscaler.co/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_upload Create an upload URL ~83
Get a signed URL to upload a local video file (up to 100MB) when it has no public URL. PUT the file bytes to upload_url with the returned headers (no Authorization header), then pass video_url to upscale_video. The URL expires in 1 hour.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | yes | – |
| size | integer | yes | File size in bytes |
No output schema declared.
No examples provided.
get_account Get account ~22
Your credit balance and the price per second of video for each resolution.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_task Get a task ~76
Get an upscale task. Status is queued, processing, completed (output_url is the result) or failed (credits were refunded). Set wait_seconds (up to 45) to wait for it to finish before returning; call again if it is still running.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
| wait_seconds | integer | – | – |
No output schema declared.
No examples provided.
list_tasks List tasks ~30
List your upscale tasks, newest first, including ones started on the website.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
upscale_video Upscale a video ~317
Start upscaling a video to 1080p, 2k or 4k. Charges credits for the whole video (its length is read from the file) and returns the task. Downloading a large video can take a few minutes. If this call times out or fails, first call list_tasks to see whether the task was created, and retry only with the SAME idempotency_key: a new key charges again.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | A unique string for this request, e.g. a UUID (printable ASCII, no spaces). Reuse it when retrying the same request. |
| ops | object | – | Optional enhancement options (deinterlace, stabilize, denoise 0-3, deflicker, fpsMultiplier 2/4/8 with slowMotion, faceRestore, hdr hdr10/hlg, engine anime). faceRestore and fpsMultiplier each double… |
| resolution | string | yes | Target resolution |
| video_url | string | yes | Public http(s) URL of the video (MP4, MOV or WebM, up to 500MB; up to 1200 seconds at 1080p, 600 seconds at 2k and 4k), or the video_url returned by create_upload |
| webhook_url | string | – | Optional public https:// URL to receive a POST webhook when the task completes or fails |
No output schema declared.
No examples provided.
How do I install the VideoUpscaler MCP server?
VideoUpscaler is a hosted endpoint at https://videoupscaler.co/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · videoupscaler.co
claude mcp add --transport http co-videoupscaler-video-upscaler 'https://videoupscaler.co/api/mcp'
What is the VideoUpscaler MCP server?
VideoUpscaler is an MCP server listed in the public MCP registry as co.videoupscaler/video-upscaler. AI video upscaler: enhance videos to 1080p, 2K or 4K and track upscaling tasks. This page covers its hosted endpoint (https://videoupscaler.co/api/mcp).
Is the VideoUpscaler MCP server safe to use?
VideoUpscaler scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the VideoUpscaler MCP server expose?
VideoUpscaler exposes 5 tools: upscale_video, get_task, list_tasks, get_account, create_upload. Their descriptions and schemas cost roughly 528 tokens of context every time the server is loaded.
Does the VideoUpscaler MCP server require authentication?
Yes. VideoUpscaler asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the VideoUpscaler MCP server still maintained?
VideoUpscaler is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.