mcp-registry/io.github.egocen-vivideo/vivideo · v1.0.1
Also listed as glama/egocen-vivideo/-vivideo/mcp
As of 2026-10-21 06:17 UTC, the Egocen Vivideo Vivideo MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
AI video generation via the Vivideo API: auto or manual mode, avatars, voices, brand kits.
Claude Code
claude mcp add --transport http egocen-vivideo-vivideo-mcp-server https://api.vivideo.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"egocen-vivideo-vivideo-mcp-server": {
"type": "http",
"url": "https://api.vivideo.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
13 of 13 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
20 parameter(s) across 7 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~2,024 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 7 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.egocen-vivideo%2Fvivideo/fixes
{
"name": "check_account",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_configuration",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "create_auto_video",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"prompt"
],
"properties": {
"name": {
"type": "string",
"maxLength": 60
},
"prompt": {
"type": "string",
"maxLength": 5000,
"minLength": 1,
"description": "What the video should show or say."
},
"voice_id": {
"type": "string",
"description": "From list_voices."
},
"avatar_id": {
"type": "string",
"description": "From list_avatars. Omit for a default presenter."
},
"folder_id": {
"type": "string"
},
"orientation": {
"enum": [
"landscape",
"portrait"
],
"type": "string"
},
"brand_kit_id": {
"type": "string",
"description": "A brand_ref from list_brand_kits."
},
"idempotency_key": {
"type": "string",
"maxLength": 255,
"description": "Optional. Reuse the same key to make a retry safe."
},
"duration_seconds": {
"type": "integer",
"maximum": 300,
"minimum": 5,
"description": "5–300, default 30."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.egocen-vivideo/vivideo"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.egocen-vivideo/vivideo"}) over MCP.
create_auto_video ~344 tokenscreate_manual_video ~325 tokensestimate_credits ~190 tokenswait_for_video ~175 tokenslist_avatars ~173 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.egocen-vivideo%2Fvivideo?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.egocen-vivideo%2Fvivideo?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.egocen-vivideo%2Fvivideo.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.egocen-vivideo%2Fvivideo.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.egocen-vivideo%2Fvivideo?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c46d2394b391a8fb…, first seen 2026-10-17, included at leaf 5310 of 37,605. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable security servers · most reliable media servers · most reliable ml servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 06:17 UTC, the Egocen Vivideo Vivideo MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Egocen Vivideo Vivideo MCP server advertises 13 tools, including check_account, check_configuration, create_auto_video, create_manual_video, estimate_credits.
Point your MCP client at this streamable-http endpoint: https://api.vivideo.ai/mcp
Glimind scanned all 13 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.