Future Video Studio
REMOTE · MCP.FUTURE.VIDEO · 2 COMPONENTS · SCANNED AUG 3
Create and manage cinematic AI video renders through the Future Video Studio Agent API.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (fvs_submit_render). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 35% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.future.video
claude mcp add --transport http video-future-future-video-studio https://mcp.future.video/mcp
[mcp_servers.video-future-future-video-studio] url = "https://mcp.future.video/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"video-future-future-video-studio": {
"type": "remote",
"url": "https://mcp.future.video/mcp",
"enabled": true
}
}
} openclaw mcp add video-future-future-video-studio --url https://mcp.future.video/mcp --transport streamable-http
mcp_servers:
video-future-future-video-studio:
url: "https://mcp.future.video/mcp" {
"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.
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.
- 3 Aug 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.
- 1 Aug 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.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 61
First indexed and scored.
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 3 Aug 2026 · Probed https://mcp.future.video/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.future.video | CN=WR3,O=Google Trust Services,C=US | 21 Jun 2026 | 19 Sept 2026 | RSA 2048 | SHA256-RSA | f1e4fc52b0bb8fb20a37377fff801ab5 |
| SANs: mcp.future.video | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
DNSSEC insecure
Validation of mcp.future.video. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| video. | present | 42529 | 8 | Verified |
| future.video. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.future.video/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.future.video/mcp | HTTPS enforced | 302 | https://mcp.future.video/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.
fvs_cancel_render Cancel render ~54
Cancel a Future Video Studio render job. Provide either `project_id` or the full `cancel_url` returned by fvs_submit_render.
| Name | Type | Req | Description |
|---|---|---|---|
| cancel_url | — | — | — |
| project_id | — | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
fvs_create_paid_render_quote Create paid render quote ~200
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request | — | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
fvs_download_final_video Download final video ~317
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.
| Name | Type | Req | Description |
|---|---|---|---|
| final_video_url | string | yes | 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 | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
fvs_example_render_request Example render request ~21
Return a minimal scene render request agents can adapt.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
fvs_get_paid_render_status Get paid render status ~66
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_token | — | — | — |
| quote_id | — | — | — |
| status_url | — | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
fvs_get_render_status Get render status ~55
Check a Future Video Studio render job. Provide either `project_id` or the full `status_url` returned by fvs_submit_render.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | — | — | — |
| status_url | — | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
fvs_open_chatgpt_app Open Future Video Studio ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_token | — | — | — |
| final_video_url | — | — | — |
| project_id | — | — | — |
| quote_id | — | — | — |
| status_url | — | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
fvs_submit_render Submit render ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| poll_until_complete | boolean | — | — |
| request | — | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.