Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Image to Video AI

REMOTE · IMAGETOVIDEOAI.TOOLS

Turn an uploaded photo into an AI video. Preview the credit cost and get the finished video link.

+3 this week 65 Trust /100

Last scanned (12 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 297 tokens (~74/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 20% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 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.

  • 16 Nov 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.

  • 14 Nov 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.

  • 12 Nov 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.

  • 11 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 60

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://imagetovideoai.tools/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=imagetovideoai.tools CN=WE1,O=Google Trust Services,C=US 29 Sept 2026 28 Dec 2026 ECDSA 256 ECDSA-SHA256 df98da7c0489f56f0ea3c069557b3913
SANs: imagetovideoai.tools, *.imagetovideoai.tools
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of imagetovideoai.tools. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
tools. DS published 1547 8 Verified
imagetovideoai.tools. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://imagetovideoai.tools/api/mcp Verified 200
http (plaintext) http://imagetovideoai.tools/api/mcp HTTPS enforced 301 https://imagetovideoai.tools/api/mcp
MCP tools · 4 exposed · ~220 tokens

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 →

Tool Tokens
generate_video ~90

Animate one uploaded photo. This spends credits. Get a quote first and confirm cost and visibility with the user. Retry with the same request_id and inputs.

NameTypeReqDescription
asset_idstringyes–
expected_creditsnumberyes–
is_publicbooleanyesUse true for public output. Private output requires paid access.
promptstringyes–
request_idstringyes–

No output schema declared.

No examples provided.

get_generation ~32

Check a task belonging to the connected account and get its video link when ready.

NameTypeReqDescription
task_idstringyes–

No output schema declared.

No examples provided.

list_image_assets ~36

List photos already uploaded to the connected account. Use an ID from this list to generate a video.

NameTypeReqDescription
pageinteger––

No output schema declared.

No examples provided.

quote_generation ~62

Check the credit cost and settings for turning an uploaded photo into a video. Does not start generation.

NameTypeReqDescription
asset_idstringyes–
is_publicbooleanyesUse true for public output. Private output requires paid access.
promptstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Image to Video AI MCP server?

Image to Video AI is a hosted endpoint at https://imagetovideoai.tools/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 · imagetovideoai.tools

# add to Claude Code
claude mcp add --transport http tools-imagetovideoai-image-to-video 'https://imagetovideoai.tools/api/mcp'
Common questions

What is the Image to Video AI MCP server?

Image to Video AI is an MCP server listed in the public MCP registry as tools.imagetovideoai/image-to-video. Turn an uploaded photo into an AI video. Preview the credit cost and get the finished video link. This page covers its hosted endpoint (https://imagetovideoai.tools/api/mcp).

Is the Image to Video AI MCP server safe to use?

Image to Video AI scores 65 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 Image to Video AI MCP server expose?

Image to Video AI exposes 4 tools: list_image_assets, quote_generation, generate_video, get_generation. Their descriptions and schemas cost roughly 220 tokens of context every time the server is loaded.

Does the Image to Video AI MCP server require authentication?

No. We connected to Image to Video AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Image to Video AI MCP server still maintained?

Image to Video AI is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Image to Video AI MCP server?

VerifyMCP ran 13 checks on Image to Video AI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.