Is io.github.egocen-vivideo/vivideo safe to use?

io.github.egocen-vivideo/vivideo has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.

How do I install io.github.egocen-vivideo/vivideo?

io.github.egocen-vivideo/vivideo supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with io.github.egocen-vivideo/vivideo?

io.github.egocen-vivideo/vivideo is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.

Is io.github.egocen-vivideo/vivideo actively maintained?

io.github.egocen-vivideo/vivideo is actively maintained — last commit was 26 days ago.

io.github.egocen-vivideo/vivideo

@vivideo/mcp

AI video generation via the Vivideo API: auto or manual mode, avatars, voices, brand kits.

47/wk GitHub npm

No known CVEs

MIT license

Actively maintained

Last commit 26d ago

Works with most clients

Transport: stdio, sse, http

0 tools

Grade F

MCPpedia last refreshed this data 11h ago

Edit this pageView history

io.github.egocen-vivideo/vivideo is an MCP server that AI video generation via the Vivideo API: auto or manual mode, avatars, voices, brand kits. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 57/100 on MCPpedia's security, maintenance and efficiency rubric.

Marketing

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-egocen-vivideo-vivideo": {
      "args": [
        "-y",
        "@vivideo/mcp"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-egocen-vivideo-vivideo)](https://mcppedia.org/s/io-github-egocen-vivideo-vivideo)

Read me

What io.github.egocen-vivideo/vivideo does

The developer + agent integration layer for the Vivideo API — a shared client, an MCP server, a CLI, and Skills. Agents are a primary user, not an afterthought.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y '@vivideo/mcp' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

57/100across 5 weighted dimensions

How we score →

0255075100

−43

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked @vivideo/mcp against OSV.dev.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.egocen-vivideo/vivideo safe to use?: io.github.egocen-vivideo/vivideo has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.
How do I install io.github.egocen-vivideo/vivideo?: io.github.egocen-vivideo/vivideo supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.egocen-vivideo/vivideo?: io.github.egocen-vivideo/vivideo is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.egocen-vivideo/vivideo actively maintained?: io.github.egocen-vivideo/vivideo is actively maintained — last commit was 26 days ago.

Similar servers

Others in marketing

View all →

Mcp Server Typescript94

DataForSEO API modelcontextprotocol server

240 9

com.generect/generect-mcp89

B2B lead generation and company search through Generect Live API for sales prospecting.

1 5

ai.canvora/canvora88

Turn any idea, URL, doc, or PDF into on-brand visuals: 100+ formats, native in 150+ languages

Google Search Console Mcp88

Google Search Console MCP Server for Claude, Cursor, Windsurf and other MCP Clients

38 1

MCP Security Weekly

Get CVE alerts and security updates for io.github.egocen-vivideo/vivideo and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Marketing

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-egocen-vivideo-vivideo": {
      "args": [
        "-y",
        "@vivideo/mcp"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-egocen-vivideo-vivideo)](https://mcppedia.org/s/io-github-egocen-vivideo-vivideo)

Read me

What io.github.egocen-vivideo/vivideo does

The developer + agent integration layer for the Vivideo API — a shared client, an MCP server, a CLI, and Skills. Agents are a primary user, not an afterthought.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y '@vivideo/mcp' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

Vivideo Toolchain

The developer + agent integration layer for the Vivideo API — a shared client, an MCP server, a CLI, and Skills. Agents are a primary user, not an afterthought.

Everything sits on top of the public API (the source of truth). No backend business logic is duplicated here — the toolchain only adds client-side ergonomics and guardrails.

vivideo-toolchain/            npm workspaces monorepo (TypeScript)
├── packages/core   @vivideo/core   one typed API client + guardrails (shared)
├── packages/mcp    @vivideo/mcp    MCP server (stdio) — 13 agent tools
├── packages/cli    @vivideo/cli    `vivideo` CLI — humans, scripts, CI, agents
├── skills/                          reusable agent Skills (SKILL.md)
└── docs/                            installation, configuration, workflows

Architecture

One client, one set of types, derived from packages/core/openapi.yaml. The MCP server and CLI both call @vivideo/core — there is exactly one representation of each request/response, so the tools, CLI, docs and OpenAPI stay consistent.

@vivideo/core adds only client-side concerns, never business logic:

Guardrail	What it does
Rate limiting	Token-bucket cap on request rate (default 8/s) — the client can't become a request flood.
Concurrency cap	Semaphore limits in-flight requests (default 4).
Bounded retries	Retries only `retryable` failures, with full-jitter backoff, capped attempts.
Honors `Retry-After`	On 429 it waits the API-specified delay before retrying.
Idempotency	Every video-create sends an `Idempotency-Key`; retries reuse it → no duplicate charges.
Timeouts	Per-request `AbortController` timeout (default 30s).
Safe waiting	`waitForVideo` polls at the API's suggested interval, with a hard timeout — never a `while(true)`.
Secret redaction	API keys / signing secrets are stripped from every log, error, and output.

These complement — and never bypass — the API's own auth, rate limits, idempotency, credit checks, premium gates, ownership and error model.

Quick start

# from the repo (until packages are published to npm)
npm install
npm run build

# authenticate (stored 0600 in ~/.vivideo/config.json), or use VIVIDEO_API_KEY
export VIVIDEO_API_KEY="vv_live_..."   # from https://app.vivideo.ai/account/api-keys

# CLI
node packages/cli/dist/index.js account
node packages/cli/dist/index.js create auto --prompt "A 20s product teaser" --wait

# MCP server (stdio) — point an MCP client at this command
node packages/mcp/dist/index.js

Once published: npm i -g @vivideo/cli (gives vivideo), and npx @vivideo/mcp for the server.

Docs

Authentication & security

Keys are read from (in order): explicit option → VIVIDEO_API_KEY env → ~/.vivideo/config.json (written owner-only 0600).
The key is never printed — all output passes through secret redaction; configure stores it without echoing it.
Keys are account-scoped secrets. Keep them server-side; one per integration so a leak is revocable in isolation.

Not included (honest scope)

Cancellation — the public API has no cancel endpoint, so no cancel tool/command is offered. Failed/stuck renders are auto-refunded by the API.
Agent/chat mode — not exposed by the public API, so not in the toolchain.
Nothing here publishes to npm, provisions DNS, or deploys — those are external steps (see the final section of docs/mcp.md).

Development

npm run buil

... [View full README on GitHub](https://github.com/egocen-vivideo/vivideo-toolchain#readme)

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

57/100across 5 weighted dimensions

How we score →

0255075100

−43

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked @vivideo/mcp against OSV.dev.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.egocen-vivideo/vivideo safe to use?: io.github.egocen-vivideo/vivideo has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.
How do I install io.github.egocen-vivideo/vivideo?: io.github.egocen-vivideo/vivideo supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.egocen-vivideo/vivideo?: io.github.egocen-vivideo/vivideo is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.egocen-vivideo/vivideo actively maintained?: io.github.egocen-vivideo/vivideo is actively maintained — last commit was 26 days ago.