MCP.Market

Zvid MCP server

online · 100% uptime
by zvid.io·io.zvid/mcp·v0.1.0
No reviews yet

Zvid: render videos & images from JSON; manage templates, projects, webhooks & credits.

A95/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A95/100

full report

Adoption
Growing

0 stars24 downloads/wk

Reviews

Write one

Nobody has reviewed Zvid yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Zvid tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • Code scan13 source files scanned25/25
  • Live reliabilityremote reachable in 366ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identitynamespace and repository owner differ; website matches verified namespace6/10
Overall 95/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Zvid compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
95/100
higher than 97% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
160 ms
faster than 71% of 30,031 servers
Downloads a week
24
more than 10% of 12,191 servers with a package

Install Zvid in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://mcp.zvid.io/mcp
Add to Cursor

What the publisher says

From the Zvid repository's README, as published. We do not edit it. Read it on GitHub

@zvid/mcp

Official Zvid agent and MCP server. Creator follows a quality-first workflow: plan the brief, adapt designed examples or library assets, validate exact project JSON, save a reviewable draft, then render only after approval. Automation and Developer add trusted direct operations.

Authentication

There are exactly two ways to authenticate. Every setup below uses one of them:

Method 1 — OAuth sign-in. Add https://mcp.zvid.io/mcp to your MCP client and sign in when prompted. The endpoint publishes OAuth discovery metadata, uses authorization code + PKCE with the single scope zvid:mcp, and issues short-lived access tokens with rotating refresh tokens (revocable per RFC 7009). This is what the client-specific instructions below use.

Method 2 — API key. Create a key at app.zvid.io/api-keys, then either:

for programmatic clients that cannot run an OAuth flow, or legacy access.

  • Hosted: send it in the X-Api-Key header on https://mcp.zvid.io/mcp —

shown in Local stdio / self-hosted setup. The stdio transport is API-key only, because MCP OAuth is defined for HTTP transports.

  • Local stdio / self-hosted: pass it via ZVIDAPIKEY / --api-key as

Hosted setup (recommended)

The hosted endpoint is https://mcp.zvid.io/mcp. It accepts both authentication methods: OAuth sign-in (method 1 — used by the client instructions below) and an API key in the X-Api-Key header (method 2).

Claude Code

claude mcp add --transport http zvid https://mcp.zvid.io/mcp
claude mcp login zvid

You can also open /mcp inside Claude Code and authenticate there.

OpenAI Codex

Register the server, then authenticate from MCP settings or the command line:

codex mcp add zvid --url https://mcp.zvid.io/mcp
codex mcp login zvid

The dashboard stores the default tool profile and maximum credits per render for MCP clients. A client may connect with concrete values in the endpoint, for example https://mcp.zvid.io/mcp?profile=creator&maxRenderCredits=60; this is connection configuration and cannot be changed by the model during a conversation. The default per-render credit limit is 120, and the dashboard limit, when set, is a hard ceiling: the effective limit is the lower of the dashboard value and the value requested in the endpoint.

The official n8n workflow copies both dashboard defaults into its workflow JSON when downloaded. Each workflow can then choose another concrete profile and credit ceiling locally without updating the dashboard or any other workflow.

Local stdio / self-hosted setup

The npm/stdio entry point uses an API key (authentication method 2). Configuration resolution is CLI flags, then environment, then ~/.zvid-mcp.json:

npx -y @zvid/mcp --api-key zvid_your_key_here --api-url http://localhost:4000

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Zvid: common questions

Is Zvid MCP server safe?
Yes, by our scan: it is graded A (95/100). Read the Zvid safety report
How do I install Zvid?
It runs remotely at mcp.zvid.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Zvid need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Zvid maintained?
The last commit was 42 days ago (2026-09-23). The latest release is v0.1.0.
Is Zvid up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Zvid compare with other MCP servers?
safety score 95/100 (higher than 97% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 160 ms (faster than 71% of 30,031 servers). Full comparison.