# VideoUpscaler (remote · videoupscaler.co)

AI video upscaler: enhance videos to 1080p, 2K or 4K and track upscaling tasks.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `videoupscaler.co`: 82/100 (this document), [markdown](https://verifymcp.io/servers/co-videoupscaler-video-upscaler/api-mcp.md), [page](https://verifymcp.io/servers/co-videoupscaler-video-upscaler/api-mcp)

## Channel facts

- Endpoint: `https://videoupscaler.co/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http co-videoupscaler-video-upscaler 'https://videoupscaler.co/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-videoupscaler-video-upscaler": {
      "url": "https://videoupscaler.co/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-videoupscaler-video-upscaler": {
      "type": "http",
      "url": "https://videoupscaler.co/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-videoupscaler-video-upscaler]
url = "https://videoupscaler.co/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-videoupscaler-video-upscaler": {
      "type": "remote",
      "url": "https://videoupscaler.co/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-videoupscaler-video-upscaler --url 'https://videoupscaler.co/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-videoupscaler-video-upscaler:
    url: "https://videoupscaler.co/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-videoupscaler-video-upscaler": {
      "Transport": "http",
      "Url": "https://videoupscaler.co/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-videoupscaler-video-upscaler -t streamable-http -u 'https://videoupscaler.co/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-videoupscaler-video-upscaler": {
      "type": "http",
      "url": "https://videoupscaler.co/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [cosmetic] “upscale_video” reworded the description of “ops”

### 2026-11-03 (score 82, +1)

- [cosmetic] “upscale_video” added an optional parameter “webhook_url”

### 2026-11-02 (score 81, 0)

- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 50% → 56%
- [cosmetic] “upscale_video” added an optional parameter “ops”

### 2026-11-01 (score 81, +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.

### 2026-10-30 (score 80, +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.

### 2026-10-28 (score 79, +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.

### 2026-10-26 (score 78, +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.

### 2026-10-25 (score 77, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (5)

### `upscale_video` (~317 tokens)

Upscale a video

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.

Input parameters:

- `idempotency_key` (string, required): 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, required): Target resolution
- `video_url` (string, required): 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

### `get_task` (~76 tokens)

Get a task

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.

Input parameters:

- `task_id` (string, required)
- `wait_seconds` (integer)

### `list_tasks` (~30 tokens)

List tasks

List your upscale tasks, newest first, including ones started on the website.

Input parameters:

- `limit` (integer)

### `get_account` (~22 tokens)

Get account

Your credit balance and the price per second of video for each resolution.

### `create_upload` (~83 tokens)

Create an upload URL

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.

Input parameters:

- `content_type` (string, required)
- `size` (integer, required): File size in bytes

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-videoupscaler-video-upscaler/api-mcp#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79
- 2026-10-28: 79
- 2026-10-27: 78
- 2026-10-26: 78
- 2026-10-25: 77
- 2026-10-24: 77
- 2026-10-23: 38
- 2026-10-22: 38
- 2026-10-21: 38
- 2026-10-20: 38
- 2026-10-19: 38
- 2026-10-18: 38
- 2026-10-17: 38
- 2026-10-16: 38
- 2026-10-15: 38
- 2026-10-14: 38

## Common questions

### 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.

## Links

- Remote endpoint: https://videoupscaler.co/api/mcp
- Website: https://videoupscaler.co/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/co-videoupscaler-video-upscaler/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-videoupscaler-video-upscaler/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-videoupscaler-video-upscaler/api-mcp