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.

io.github.hanshs474/movoa-mcp

REMOTE · MOVOA.AI · 2 COMPONENTS

Movoa (movoa.ai), the AI video generator with sound: text and photo to video from any MCP client.

+7 this week 77 Trust /100

Last scanned (3 hours ago)

Scores higher than 69% of remote servers

Reachable. Last reached 5 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 Security80
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 441 tokens (~147/item across 3 items; 3 tools + 0 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 Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 4 Nov 26 +1

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

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

  • 30 Oct 26 +5
    • HTTPS: unverified → pass ▲ security
  • 29 Oct 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.

  • 27 Oct 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.

  • 26 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 25 Oct 26 68

    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 5 Nov 2026 · Probed https://movoa.ai/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=movoa.ai CN=WE1,O=Google Trust Services,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA256 8aed1f80ed2b54e813a998f131182a3c
SANs: movoa.ai, *.movoa.ai
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 movoa.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
movoa.ai. 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
Header Value
strict-transport-security max-age=31536000
content-security-policy frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://movoa.ai/api/mcp Verified 200
http (plaintext) http://movoa.ai/api/mcp HTTPS enforced 301 https://movoa.ai/api/mcp
MCP tools · 3 exposed · ~365 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
check_status ~43

Read the status of a run started with generate_video, and the video URL when it is ready.

NameTypeReqDescription
run_idstringyesThe run id returned by generate_video.

No output schema declared.

No examples provided.

credits ~24

The credits left on the Movoa account behind your API key. Free to call.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

generate_video ~298

Generate a video clip with sound from a text prompt on movoa.ai, or animate a photo by passing image_url (photo to video). Defaults to MiniMax H3 at 480p. Runs cost credits on your Movoa account, at the prices on https://movoa.ai/pricing. Video takes minutes: this returns a run id to poll with check_status.

NameTypeReqDescription
aspect_ratiostring–'16:9' (default), '9:16' or '1:1' (Veo: 16:9 or 9:16).
durationinteger–Seconds. minimax-h3: 4/5/6/8/10/15; seedance-2-5: 5–30 in steps of 5; seedance-2 family: 4/6/8/10; veo-3-1-fast: 8.
image_urlstring–Optional photo (public https URL) used as the first frame — makes this photo to video.
modelstring–Default minimax-h3, the lowest-cost model.
promptstringyesThe shot: what happens, where, how the camera moves, and what it sounds like.
resolutionstring–minimax-h3: '480p' or '768p'; Seedance: '480p' or '720p'; Veo: '720p'.

No output schema declared.

No examples provided.

Install

How do I install the io.github.hanshs474/movoa-mcp server?

io.github.hanshs474/movoa-mcp is a hosted endpoint at https://movoa.ai/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 · movoa.ai

# add to Claude Code
claude mcp add --transport http hanshs474-movoa-mcp 'https://movoa.ai/api/mcp'
Common questions

What is the io.github.hanshs474/movoa-mcp server?

io.github.hanshs474/movoa-mcp is listed in the public MCP registry as io.github.hanshs474/movoa-mcp. Movoa (movoa.ai), the AI video generator with sound: text and photo to video from any MCP client. This page covers its hosted endpoint (https://movoa.ai/api/mcp).

Is the io.github.hanshs474/movoa-mcp server safe to use?

io.github.hanshs474/movoa-mcp scores 77 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 io.github.hanshs474/movoa-mcp server expose?

io.github.hanshs474/movoa-mcp exposes 3 tools: generate_video, check_status, credits. Their descriptions and schemas cost roughly 365 tokens of context every time the server is loaded.

Does the io.github.hanshs474/movoa-mcp server require authentication?

No. We connected to io.github.hanshs474/movoa-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.hanshs474/movoa-mcp server still maintained?

io.github.hanshs474/movoa-mcp 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.