# Future Video Studio (remote · mcp.future.video)

Create and manage cinematic AI video renders through the Future Video Studio Agent API.

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.future.video`: 66/100 (this document), [markdown](https://verifymcp.io/servers/video-future-future-video-studio/mcp.md), [page](https://verifymcp.io/servers/video-future-future-video-studio/mcp)
- pypi · `future-video-studio-mcp`: 10/100, [markdown](https://verifymcp.io/servers/video-future-future-video-studio/future-video-studio-mcp.md), [page](https://verifymcp.io/servers/video-future-future-video-studio/future-video-studio-mcp)

## Channel facts

- Endpoint: `https://mcp.future.video/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.8`

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

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (fvs_submit_render).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1241 tokens (~124/item across 10 items; 8 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 35% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http video-future-future-video-studio https://mcp.future.video/mcp
```

### Codex

```toml
[mcp_servers.video-future-future-video-studio]
url = "https://mcp.future.video/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "video-future-future-video-studio": {
      "type": "remote",
      "url": "https://mcp.future.video/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add video-future-future-video-studio --url https://mcp.future.video/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  video-future-future-video-studio:
    url: "https://mcp.future.video/mcp"
```

### Other

```json
{
  "mcpServers": {
    "video-future-future-video-studio": {
      "type": "http",
      "url": "https://mcp.future.video/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-08-03 (score 66, +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-08-01 (score 65, +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-07-31 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 63, +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-07-27 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (8)

### `fvs_open_chatgpt_app` (~89 tokens)

Open Future Video Studio

Open the Future Video Studio ChatGPT app widget without creating a render. Use this when the user wants the FVS app panel, wants to paste a status URL, or wants to prepare a render interactively before spending credits.

Input parameters:

- `claim_token`
- `final_video_url`
- `project_id`
- `quote_id`
- `status_url`

### `fvs_submit_render` (~186 tokens)

Submit render

Submit a Future Video Studio render job through the FVS Agent API.

    Pass the render payload in the required `request` object. For reference
    assets, pass public HTTPS URLs in `upload_urls`; every
    `request.assets[].filename` must match one uploaded URL basename or explicit
    upload URL filename. Credentials come from the connector header,
    marketplace account mapping, or FVS_AGENT_API_KEY in the MCP server
    environment.

Input parameters:

- `poll_until_complete` (boolean)
- `request` (required): Required render request object. Include name. project_mode must be one of scene, music, or custom. Use assets[].purpose for asset intent. Usually include screenplay, instructions, shot_count, duratio…
- `upload_urls`: Optional public HTTPS reference asset URLs. Each object can include url and filename; filename should match request.assets[].filename.

### `fvs_create_paid_render_quote` (~200 tokens)

Create paid render quote

Create a no-account Link payment quote for an FVS render.

    The backend returns HTTP 402 payment details as data: `payment_url`,
    `status_url`, `claim_token`, `amount_cents`, `currency`, and a raw
    `www_authenticate` challenge. Pay `payment_url` with Link's MPP flow, then
    poll with fvs_get_paid_render_status. Local file uploads are not available
    in paid quote mode; use public HTTPS `upload_urls` when assets are needed.

Input parameters:

- `request` (required): Required render request object used for the paid quote. Include name. project_mode must be one of scene, music, or custom. Use assets[].purpose for asset intent. Usually include screenplay, instructi…
- `upload_urls`: Optional public HTTPS reference asset URLs. Each object can include url and filename; filename should match request.assets[].filename.

### `fvs_get_render_status` (~55 tokens)

Get render status

Check a Future Video Studio render job.

    Provide either `project_id` or the full `status_url` returned by
    fvs_submit_render.

Input parameters:

- `project_id`
- `status_url`

### `fvs_get_paid_render_status` (~66 tokens)

Get paid render status

Check a no-account paid render created with fvs_create_paid_render_quote.

    Provide the full `status_url` or pass both `quote_id` and `claim_token`.

Input parameters:

- `claim_token`
- `quote_id`
- `status_url`

### `fvs_cancel_render` (~54 tokens)

Cancel render

Cancel a Future Video Studio render job.

    Provide either `project_id` or the full `cancel_url` returned by
    fvs_submit_render.

Input parameters:

- `cancel_url`
- `project_id`

### `fvs_download_final_video` (~317 tokens)

Download final video

Download a completed Future Video Studio final render URL to a local file.

Use this only after fvs_get_render_status or fvs_get_paid_render_status returns
a final_video_url for a completed render. The tool performs an unauthenticated
HTTPS GET to that signed URL and writes the response bytes to output_path on the
MCP server's local filesystem. It does not call the FVS Agent API, spend wallet
credits, require FVS_AGENT_API_KEY, cancel jobs, or modify remote render state.

Side effects and constraints: output_path is a local filesystem path for the MCP
server process, parent directories are created, existing files are not replaced
unless overwrite is true, and large videos may take minutes to download. The
request timeout is 600 seconds. Use a fresh status check to refresh expired
signed URLs, and do not pass arbitrary or untrusted URLs.

Input parameters:

- `final_video_url` (string, required): HTTPS signed final_video_url returned by a completed fvs_get_render_status or fvs_get_paid_render_status response. Use a fresh status check if the signed URL has expired.
- `output_path` (string, required): Local filesystem path where the MCP server should write the video, for example C:/Users/me/Videos/fvs-result.mp4 or /tmp/fvs-result.mp4. Parent directories are created. Existing files are refused unl…
- `overwrite` (boolean): Set true only when replacing an existing output_path is intended. Defaults to false to avoid accidental local file overwrites.

### `fvs_example_render_request` (~21 tokens)

Example render request

Return a minimal scene render request agents can adapt.

## Diagnostics

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

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 65
- 2026-07-31: 64
- 2026-07-30: 64
- 2026-07-29: 63
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 61

## Links

- Remote endpoint: https://mcp.future.video/mcp
- Repository: https://github.com/ariadne-coil/fvs-mcp
- Website: https://future.video/
- Changelog RSS feed: https://verifymcp.io/servers/video-future-future-video-studio/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/video-future-future-video-studio/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/video-future-future-video-studio/mcp