cli@1.1.5

VERIFIED· startup only

Publisher claims: "Video API for automated video production at scale: templates, AI voiceovers, subtitles, AI images" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher json2video · publishing for 217 daysInstalls 0Last detonated 5d ago
$claude mcp add cli -- npx -y @json2video/cli
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
JSON2VIDEO_API_KEYConfiguration, not credentials: JSON2VIDEO_BASE_URL, JSON2VIDEO_TIMEOUT
Where it talks to
json2video.com (its own)Also amazonaws.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names amazonaws.com as well as its own vendor. The guard injects JSON2VIDEO_API_KEY only into requests to json2video.com (and its subdomains) and refuses the rest.

$vet-skills run --secrets JSON2VIDEO_API_KEY=json2video.com -- npx -y @json2video/cli

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-10 and scored it 85/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 24 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
4.2sprocessdependency install exit 0
24sclaimedstartup only: exited (0) before answering · media Manage media files (upload, list, get, delete) skill Manage AI skills: install, update, list help [command] display help for command
24sprocessscript backend runs setup only
24sprocessno install scripts to re-run

Static findings

CRITICAL
Prompting user to enter sensitive credentialsdist/json2video.cjs:523 · Prompting user to enter sensitive credentials — social engineeringrl.question("Enter your API key: ", (answer) => {Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST03
MEDIUM
File type combined with upload actiondist/json2video.cjs:4219 · File type combined with upload action — agent may exfiltrate local data filesif (!opts.json) humanErr(`Uploading ${name} (${formatBytes(size)})...`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07

Cost to the agent

Instructions loaded
≈52 tok
1 file · 4 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for @json2video/cli@1.1.5 as of 5d ago. This is the package itself, not its dependencies.