com.ilovevideoeditor/mcp-server
NPM · @ILOVEVIDEOEDITOR/MCP-SERVER · SCANNED SEP 22
Render videos from VideoJSON + 249+ templates via the iLoveVideoEditor API
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 69 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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
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
claude mcp add com-ilovevideoeditor-mcp-server -- npx -y @ilovevideoeditor/mcp-server
{
"mcpServers": {
"com-ilovevideoeditor-mcp-server": {
"command": "npx",
"args": [
"-y",
"@ilovevideoeditor/mcp-server"
]
}
}
} {
"servers": {
"com-ilovevideoeditor-mcp-server": {
"command": "npx",
"args": [
"-y",
"@ilovevideoeditor/mcp-server"
]
}
}
} codex mcp add com-ilovevideoeditor-mcp-server -- npx -y @ilovevideoeditor/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-ilovevideoeditor-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@ilovevideoeditor/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add com-ilovevideoeditor-mcp-server --command npx --arg -y --arg @ilovevideoeditor/mcp-server
mcp_servers:
com-ilovevideoeditor-mcp-server:
command: "npx"
args: ["-y", "@ilovevideoeditor/mcp-server"] {
"McpServers": {
"com-ilovevideoeditor-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@ilovevideoeditor/mcp-server"
]
}
}
} assistant mcp add com-ilovevideoeditor-mcp-server -t stdio -c npx -a -y @ilovevideoeditor/mcp-server
{
"mcpServers": {
"com-ilovevideoeditor-mcp-server": {
"command": "npx",
"args": [
"-y",
"@ilovevideoeditor/mcp-server"
]
}
}
} 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.
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
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 22 Sept 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 →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
ilovevideoeditor_get_download_url ~37
Get a fresh signed download URL for a completed render job.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Completed 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.
| Name | Type | Req | Description |
|---|---|---|---|
| includeMetadata | boolean | – | When true, include labels, notes and recommended flags. |
| layerType | string | yes | Layer 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.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| templateId | string | yes | The 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.).
| Name | Type | Req | Description |
|---|---|---|---|
| time | number | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Image format. |
| time | number | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform on the local preview server. |
| file | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| videoJSON | object | yes | A 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.
| Name | Type | Req | Description |
|---|---|---|---|
| templateId | string | yes | Template ID (e.g., lovable_good_morning, lovable_apology, lovable_memory_montage) |
| variables | object | yes | Template-specific variables (userName, companionName, message, photos, etc.) |
No output schema declared.
No examples provided.
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 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 22 September 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.