Skip to content

Future Video Studio MCP server

video.future/future-video-studiofuture.videostreamable-httpv0.1.8Scanned

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

8 tools: 3 can delete or cancel things, 3 change things and 2 only read.

Tools: 3 delete, 0 irreversible, 3 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Future Video Studio MCP server can do

The Future Video Studio MCP server is published by future.video, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (3 tools: fvs_submit_render, fvs_cancel_render and fvs_download_final_video) and create or change data (3 tools: fvs_open_chatgpt_app, fvs_create_paid_render_quote and fvs_example_render_request). 2 tools only read.

3 tools bring in text other people can write (fvs_submit_render, fvs_create_paid_render_quote and fvs_cancel_render).

The fixed checks matched 3 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 0.1.8.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Deletes or cancels 3Claude Code: deny
  • fvs_cancel_renderCancel a Future Video Studio render job.Reads text others writeNo findings

    Why it is in this group

    • The name "fvs_cancel_render" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Cancel a Future Video Studio render job. Provide either `project_id` or the full `cancel_url` returned by fvs_submit_render.

    Annotations the server declares

    • title: Cancel render
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • fvs_download_final_videoDownload a completed Future Video Studio final render URL to a local file.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Download final video
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • fvs_submit_renderSubmit a Future Video Studio render job through the FVS Agent API.Reads text others write1 finding

    Why it is in this group

    • The name "fvs_submit_render" says "submit": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "Credentials".

      Matched text

      description: "...me or explicit upload URL filename. Credentials come from the connector header, mar..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Submit render
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 3Claude Code: ask
  • fvs_create_paid_render_quoteCreate a no-account Link payment quote for an FVS render.Reads text others writeNo findings

    Why it is in this group

    • The name "fvs_create_paid_render_quote" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create paid render quote
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • fvs_example_render_requestReturn a minimal scene render request agents can adapt.1 finding

    Why it is in this group

    • The name "fvs_example_render_request" says "request": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "fvs_example_render_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "fvs_example_render_request" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Return a minimal scene render request agents can adapt.

    Annotations the server declares

    • title: Example render request
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • fvs_open_chatgpt_appOpen the Future Video Studio ChatGPT app widget without creating a render.1 finding

    Why it is in this group

    • The name "fvs_open_chatgpt_app" says "open": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "fvs_open_chatgpt_app" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "fvs_open_chatgpt_app" says "open": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Open Future Video Studio
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • fvs_get_paid_render_statusCheck a no-account paid render created with fvs_create_paid_render_quote.No findings

    Why it is in this group

    • The name "fvs_get_paid_render_status" says "get": a word for reading.
    Description, as the server wrote it
    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`.

    Annotations the server declares

    • title: Get paid render status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • fvs_get_render_statusCheck a Future Video Studio render job.No findings

    Why it is in this group

    • The name "fvs_get_render_status" says "get": a word for reading.
    Description, as the server wrote it
    Check a Future Video Studio render job. Provide either `project_id` or the full `status_url` returned by fvs_submit_render.

    Annotations the server declares

    • title: Get render status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:21 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (3 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.future.video/mcp: tools/list returned 8 tools to an anonymous client, including fvs_submit_render (destructive), fvs_cancel_render (destructive), fvs_download_final_video (destructive), fvs_open_chatgpt_app (write), fvs_create_paid_render_quote (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn1 info
  • The server marks "fvs_open_chatgpt_app" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "fvs_open_chatgpt_app" says "open": a word for a change.

    What this check looks for
  • The server marks "fvs_example_render_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "fvs_example_render_request" says "request": a word for a change.

    What this check looks for
  • The description mentions "Credentials".

    Matched text

    description: "...me or explicit upload URL filename. Credentials come from the connector header, mar..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.8. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__future-video-studio__fvs_get_render_status",
      "mcp__future-video-studio__fvs_get_paid_render_status"
    ],
    "ask": [
      "mcp__future-video-studio__fvs_open_chatgpt_app",
      "mcp__future-video-studio__fvs_create_paid_render_quote",
      "mcp__future-video-studio__fvs_example_render_request"
    ],
    "deny": [
      "mcp__future-video-studio__fvs_submit_render",
      "mcp__future-video-studio__fvs_cancel_render",
      "mcp__future-video-studio__fvs_download_final_video"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as future-video-studio. Review it before you use it.

Capability tags behind 3 rules
  • mcp__future-video-studio__fvs_submit_render untrusted-input
  • mcp__future-video-studio__fvs_create_paid_render_quote untrusted-input
  • mcp__future-video-studio__fvs_cancel_render untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/video.future/future-video-studio/verify?hash=4135473b587d024de7c2d80ff00f854bb9313b5905a4cfc0d4cf86b3c6914556" | jq -e '.changed == false'

Pinned hash 4135473b587d, from Nov 18, 2026, 10:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/video.future/future-video-studio/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for video.future/future-video-studio
[![Anlyon Radar](https://radar.anlyon.com/badge/video.future/future-video-studio.svg)](https://radar.anlyon.com/servers/video.future/future-video-studio)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:55 UTC.

Future Video Studio MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Future Video Studio MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Future Video Studio MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: fvs_submit_render, fvs_cancel_render and fvs_download_final_video.

Can the Future Video Studio MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Future Video Studio MCP server have?

8 tools: 3 destructive, 3 write, 2 read. fvs_submit_render, fvs_cancel_render, fvs_download_final_video, fvs_open_chatgpt_app, fvs_create_paid_render_quote, fvs_example_render_request, fvs_get_render_status and fvs_get_paid_render_status.

Does the Future Video Studio MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Future Video Studio MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Future Video Studio MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.