vivideo MCP server
io.github.egocen-vivideo/vivideoegocen-vivideostreamable-httpv1.0.2Scanned
AI video generation via the Vivideo API: auto or manual mode, avatars, voices, brand kits.
13 tools: 4 change things and 9 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 vivideo MCP server can do
The vivideo MCP server is published by the GitHub account egocen-vivideo. It has 13 tools. It can create or change data (4 tools: check_configuration, estimate_credits, create_auto_video and create_manual_video), but cannot delete data. 9 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 1.0.2.
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.
13 tools
Changes things 4Claude Code: ask
check_configurationCheck whether a Vivideo API key is present on this request.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.
Description, as the server wrote it Check whether a Vivideo API key is present on this request. Call this FIRST. Returns { configured: boolean }. If false, ask the user to add an Authorization: Bearer vv_live_... header to the MCP server config (a key from https://app.vivideo.ai/account/api-keys). Never asks for or exposes the key.
create_auto_videoCreate a video in AUTO mode: Vivideo writes the script and produces a complete AI-avatar video from your prompt.No findings
Why it is in this group
- The name "create_auto_video" says "create": a word for a change.
Description, as the server wrote it Create a video in AUTO mode: Vivideo writes the script and produces a complete AI-avatar video from your prompt. Returns immediately with a video id and status "processing" (paid) or "preview" (free accounts — see the preview field and upgrade link). Then call wait_for_video or get_video. An Idempotency-Key is sent automatically so a retry never creates a duplicate. Rendering requires a premium plan and credits.
create_manual_videoCreate a video in MANUAL mode: send your prompt straight to a specific model (get ids/options from list_models).No findings
Why it is in this group
- The name "create_manual_video" says "create": a word for a change.
Description, as the server wrote it Create a video in MANUAL mode: send your prompt straight to a specific model (get ids/options from list_models). The operation is inferred from inputs — add image_url for image-to-video. resolution/duration/aspect_ratio must match the model (an invalid value returns a 400 listing what is allowed). Returns a video id and status; then wait_for_video or get_video. Idempotency handled automatically.
estimate_creditsEstimate the credits a generation will cost, from the published per-model rates — BEFORE creating it.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.
Description, as the server wrote it Estimate the credits a generation will cost, from the published per-model rates — BEFORE creating it. This is an estimate, not a charge; the exact amount is returned as credits_charged when you create the video. Use it with check_account to confirm the user can afford the request.
Only reads 9Show 9 read-only tools
check_accountGet the account plan, premium status, and remaining credit balance.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get the account plan, premium status, and remaining credit balance. Use this to decide whether the user can generate a video (rendering needs a premium plan and enough credits). Returns plan, premium, credits, free_video_available, and links (upgrade / buy_credits). Cheap and safe to call often.
get_videoGet a video's current status and result.No findings
Why it is in this group
- The name "get_video" says "get": a word for reading.
Description, as the server wrote it Get a video's current status and result. status is one of queued | processing | completed | failed | preview. When completed, video_url is the MP4. When failed, credits are refunded and error explains why. Cheap; prefer wait_for_video for polling instead of calling this in a tight loop.
list_avatarsList available avatars for auto-mode videos (the stock catalogue plus the account's own avatars).No findings
Why it is in this group
- The name "list_avatars" says "list": a word for reading.
Description, as the server wrote it List available avatars for auto-mode videos (the stock catalogue plus the account's own avatars). Stock avatars are grouped by person, each with a `looks` array — pass a looks[].avatar_id (or an owned avatar's id) as `avatar_id` in create_auto_video. Use `search`/`limit` to keep responses small.
list_brand_kitsList the account's brand kits (logo, colors, fonts, motion style).No findings
Why it is in this group
- The name "list_brand_kits" says "list": a word for reading.
Description, as the server wrote it List the account's brand kits (logo, colors, fonts, motion style). Returns brand_ref ids to pass as `brand_kit_id` in create_auto_video to produce an on-brand video.
list_modelsList the video models available for MANUAL mode plus the auto-generate pipeline (id "vivideo-auto").No findings
Why it is in this group
- The name "list_models" says "list": a word for reading.
Description, as the server wrote it List the video models available for MANUAL mode plus the auto-generate pipeline (id "vivideo-auto"). Each model lists its operations, allowed durations, resolutions, aspect ratios, style presets and per-second credit rate — use these to build a valid create request. Filter with `mode` to keep the response small.
list_videosList the account's videos, newest first.No findings
Why it is in this group
- The name "list_videos" says "list": a word for reading.
Description, as the server wrote it List the account's videos, newest first. Filter by status and limit the count to keep responses small.
list_voicesList available voices for auto-mode videos.No findings
Why it is in this group
- The name "list_voices" says "list": a word for reading.
Description, as the server wrote it List available voices for auto-mode videos. Returns voice ids to pass as `voice_id` in create_auto_video. Filter by language/gender/search and cap with `limit`. Voice cloning is not available via the API.
render_previewFor FREE accounts only: after the user upgrades, render a video that was returned as status "preview".No findings
Why it is in this group
- The name "render_preview" says "preview": a word for reading.
Description, as the server wrote it For FREE accounts only: after the user upgrades, render a video that was returned as status "preview". Charges run on the same project (the first video after upgrading is free). If the video is already rendering/complete, returns its current state. If the account is still free, returns an upgrade_required error with an upgrade link.
wait_for_videoWait for a video to reach a terminal state (completed / failed / preview), then return it.No findings
Why it is in this group
- The name "wait_for_video" says "wait": a word for reading.
Description, as the server wrote it Wait for a video to reach a terminal state (completed / failed / preview), then return it. Polls safely at the API-suggested interval for up to ~20 seconds per call (HTTP requests are time-capped). If it does not finish in time it returns { timed_out: true } with the latest status — simply call it again with the same id to keep waiting. It never blocks indefinitely or over-polls.
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 untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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.
Looked at Nov 20, 2026, 19:04 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
- 4
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.vivideo.ai/mcp: tools/list returned 13 tools to an anonymous client, including check_configuration (write), estimate_credits (write), create_auto_video (write), create_manual_video (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
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 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http vivideo https://api.vivideo.ai/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http vivideo https://api.vivideo.ai/mcp --header 'Authorization: <your-authorization>'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.
{
"permissions": {
"allow": [
"mcp__vivideo__check_account",
"mcp__vivideo__list_models",
"mcp__vivideo__list_avatars",
"mcp__vivideo__list_voices",
"mcp__vivideo__list_brand_kits",
"mcp__vivideo__get_video",
"mcp__vivideo__wait_for_video",
"mcp__vivideo__list_videos",
"mcp__vivideo__render_preview"
],
"ask": [
"mcp__vivideo__check_configuration",
"mcp__vivideo__estimate_credits",
"mcp__vivideo__create_auto_video",
"mcp__vivideo__create_manual_video"
],
"deny": []
}
}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 vivideo. Review it before you use it.
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/io.github.egocen-vivideo/vivideo/verify?hash=8a4a46948163623adcd31cdcd3a7190c29af9584007bec51957aac31a3b77af6" | jq -e '.changed == false'Pinned hash 8a4a46948163, from Nov 19, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.egocen-vivideo/vivideo/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.egocen-vivideo/vivideo)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:33 UTC.
vivideo MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the vivideo MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 4 of which can change, send or delete something, and 0 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 vivideo MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the vivideo 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 vivideo MCP server have?
- 13 tools: 4 write, 9 read. check_configuration, estimate_credits, create_auto_video, create_manual_video, check_account, list_models, list_avatars, list_voices and 5 more.
Does the vivideo MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the vivideo MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the vivideo MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.