Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.ilovevideoeditor/mcp-server

NPM · @ILOVEVIDEOEDITOR/MCP-SERVER

Render videos from VideoJSON + 249+ templates via the iLoveVideoEditor API

0 this week 79 Trust /100

Last scanned (21 hours ago)

Scores higher than 63% of npm servers

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 32 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 557 tokens (~55/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1
    • Stability: 0.97 → pass security
  • 20 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 14 Nov 26 +1
    • Stability: 0.97 → pass security
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@ilovevideoeditor/mcp-server@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 8 findings
ID CVE Severity Vector Fix available
GHSA-rmxm-3fg6-px4f CVE-2026-118663 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-f897-62hf-6gxq high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 95 packages
Packages resolved 95
Stale 31
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~557 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ilovevideoeditor_get_download_url ~37

Get a fresh signed download URL for a completed render job.

NameTypeReqDescription
jobIdstringyesCompleted render job ID

No output schema declared.

No examples provided.

ilovevideoeditor_get_layer_capabilities ~101

Return the built-in effects and transitions that are compatible with a given layer type (text, image, video, shape, audio, etc.). Use this before choosing effects or transitions for a layer.

NameTypeReqDescription
includeMetadataboolean–When true, include labels, notes and recommended flags.
layerTypestringyesLayer type to query: text, image, video, shape, audio, captions, composition, group, empty

No output schema declared.

No examples provided.

ilovevideoeditor_get_render_status ~52

Check the status of a render job by its job ID.

NameTypeReqDescription
jobIdstringyesThe render job ID returned by ilovevideoeditor_render_json or ilovevideoeditor_render_template

No output schema declared.

No examples provided.

ilovevideoeditor_get_template ~44

Get detailed information about a specific template, including its variable schema.

NameTypeReqDescription
templateIdstringyesThe template ID (e.g., lovable_good_morning)

No output schema declared.

No examples provided.

ilovevideoeditor_list_templates ~25

List all available iLoveVideoEditor templates for generating personalized videos.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ilovevideoeditor_local_analyze ~56

Analyze the generated VideoJSON layout in the local preview and return structured metrics and issues (overflow, overlap, font fallback, etc.).

NameTypeReqDescription
timenumber–Time in seconds to analyze. Defaults to current frame.

No output schema declared.

No examples provided.

ilovevideoeditor_local_capture ~51

Capture a screenshot from the running local preview at a given time.

NameTypeReqDescription
formatstring–Image format.
timenumber–Time in seconds to capture. Defaults to current frame.

No output schema declared.

No examples provided.

ilovevideoeditor_local_preview ~62

Start or stop the local preview dev server. Use this before capturing frames.

NameTypeReqDescription
actionstringyesAction to perform on the local preview server.
filestring–Path to a TypeScript preview file to load. Required for start.

No output schema declared.

No examples provided.

ilovevideoeditor_render_json ~46

Submit a raw VideoJSON payload to the iLoveVideoEditor render queue and receive a job ID.

NameTypeReqDescription
videoJSONobjectyesA valid VideoJSON scene definition

No output schema declared.

No examples provided.

ilovevideoeditor_render_template ~83

Generate a video from a named template with variables, queue it for rendering, and return a job ID.

NameTypeReqDescription
templateIdstringyesTemplate ID (e.g., lovable_good_morning, lovable_apology, lovable_memory_montage)
variablesobjectyesTemplate-specific variables (userName, companionName, message, photos, etc.)

No output schema declared.

No examples provided.

Install

How do I install the com.ilovevideoeditor/mcp-server server?

com.ilovevideoeditor/mcp-server runs locally as an npm package, launched with npx -y @ilovevideoeditor/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @ilovevideoeditor/mcp-server

# add to Claude Code
claude mcp add com-ilovevideoeditor-mcp-server -- npx -y @ilovevideoeditor/mcp-server
Common questions

What is the com.ilovevideoeditor/mcp-server server?

com.ilovevideoeditor/mcp-server is listed in the public MCP registry as com.ilovevideoeditor/mcp-server. Render videos from VideoJSON + 249+ templates via the iLoveVideoEditor API. This page covers its npm package (@ilovevideoeditor/mcp-server).

Is the com.ilovevideoeditor/mcp-server server safe to use?

com.ilovevideoeditor/mcp-server scores 79 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.ilovevideoeditor/mcp-server server expose?

com.ilovevideoeditor/mcp-server exposes 10 tools: ilovevideoeditor_list_templates, ilovevideoeditor_get_template, ilovevideoeditor_get_layer_capabilities, ilovevideoeditor_render_json, ilovevideoeditor_render_template, and 5 more. Their descriptions and schemas cost roughly 557 tokens of context every time the server is loaded.

Is the com.ilovevideoeditor/mcp-server server still maintained?

com.ilovevideoeditor/mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the com.ilovevideoeditor/mcp-server server under?

com.ilovevideoeditor/mcp-server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the com.ilovevideoeditor/mcp-server server?

VerifyMCP ran 16 checks on com.ilovevideoeditor/mcp-server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.