Shotcut MCP
MCPB · SHOTCUT-MCP-1.6.0.MCPB
Create, edit, validate, preview, and render Shotcut projects through AI clients.
Available components
Last scanned (5 hours ago)
Scores higher than 88% of MCPB servers
Category Design and Media
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency48
- 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 (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4657 tokens (~166/item across 28 items; 28 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 28 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 29 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 −1
- Stability: pass → 0.93 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 0
- Stability: pass → 0.97 functional
- 18 Oct 26 0
- Stability: 0.97 → pass security
- 17 Oct 26 0
- Schema quality: 3963 → 4657 ▼ functional
- 16 Oct 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.
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 5 Nov 2026 · Analysed mcpb/https://github.com/matrodrigs/shotcut-mcp/releases/download/v1.6.0/shotcut-mcp-1.6.0.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
start_render Start render ~289
Use only after the user explicitly requests export or approves a preflight summary of project, output, preset, range or duration, and overwrite behavior; never infer export from edit completion, and do not ask twice after an explicit request. Starts one revision-bound durable render and exact editable project snapshot; pass expected_revision when known and monitor job_id with render_status.
| Name | Type | Req | Description |
|---|---|---|---|
| consumer_properties | object | – | Up to 50 scalar MLT avformat properties. Safe names are allowlisted unless the administrator enables unsafe properties; prefer a named preset. |
| expected_revision | string | – | Optional SHA-256 revision returned by inspect_project. When supplied, rendering fails before creating job or output state if the saved project changed. |
| in_frame | integer | – | Inclusive first project frame; requires out_frame. |
| marker_id | string | – | Range marker id from inspect_project; mutually exclusive with explicit frames. |
| out_frame | integer | – | Inclusive last project frame; requires in_frame. |
| output_path | string | yes | Authorized destination path. Omit only for single-frame or contact-sheet previews to use bounded managed output. |
| overwrite | boolean | – | Replace an existing destination only when the user explicitly authorized it. |
| preset | string | – | Named safe export preset returned by shotcut_capabilities. |
| project_path | string | yes | Existing authorized Shotcut .mlt or .xml project path, except when create_project creates it. |
| Name | Type | Req | Description |
|---|---|---|---|
| current_revision | string|null | – | – |
| details | object | – | Bounded structured context specific to the error code. |
| editable_project_path | string | – | – |
| error | string | – | Human-readable failure summary. |
| error_code | string | – | Stable machine-readable Shotcut MCP error code. |
| error_type | string | – | Stable Python exception family retained for compatibility. |
| expected_revision | string|null | – | – |
| in_frame | integer|null | – | – |
| job_id | string | – | – |
| marker_id | string|null | – | – |
| marker_text | string|null | – | – |
| out_frame | integer|null | – | – |
| output_path | string | – | – |
| preset | string | – | – |
| project_path | string | – | – |
| project_revision | string|null | – | – |
| range_duration_frames | integer|null | – | – |
| recommended_action | string | – | Machine-readable next action for the caller. |
| recommended_tool | string|null | – | MCP tool to call next when one action is preferred. |
| recoverable | boolean | – | Whether the caller can take a safe corrective action. |
| render_project_path | string | – | – |
| rendered_project_revision | string | – | – |
| source_duration_frames | integer|null | – | – |
| source_project_path | string | – | – |
| status | string | – | – |
| total_frames | integer|null | – | – |
No examples provided.
validate_project Validate project with MLT ~102
Use when saved-project readiness is unknown or media/service dependencies changed before preview or render; edit_project already validates its candidate, so do not repeat this after every successful edit. Checks XML, local resources, required installed MLT services, and first-frame Melt processing; this is not visual-quality analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Existing authorized local project, media, folder, or backup path. |
| timeout_seconds | integer | – | Bounded timeout for local MLT processing. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | object | – | Independent project dependency checks. |
| current_revision | string|null | – | – |
| details | object | – | Bounded structured context specific to the error code. |
| diagnostic | string|null | – | Bounded Melt diagnostic output, when present. |
| error | string | – | Human-readable failure summary. |
| error_code | string | – | Stable machine-readable Shotcut MCP error code. |
| error_type | string | – | Stable Python exception family retained for compatibility. |
| expected_revision | string|null | – | – |
| project | object | – | Project snapshot; inspect_project publishes its complete schema. |
| ready | boolean | – | Whether validation passed, local resources exist, and required MLT services were verified. |
| recommended_action | string | – | Machine-readable next action for the caller. |
| recommended_tool | string|null | – | MCP tool to call next when one action is preferred. |
| recoverable | boolean | – | Whether the caller can take a safe corrective action. |
| return_code | integer | – | Local Melt process exit code. |
| valid | boolean | – | Whether local Melt processed the first project frame successfully. |
No examples provided.
How do I install the Shotcut MCP server?
Shotcut MCP ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 0f2194bbe39950e703b3b2c6253bfd71ef19dce1f3303e680f1c7853799cefba; the commands to do that are on this page. If it does not match, do not open it.
mcpb · shotcut-mcp-1.6.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
0f2194bbe39950e703b3b2c6253bfd71ef19dce1f3303e680f1c7853799cefba
macOS / Linux
echo "0f2194bbe39950e703b3b2c6253bfd71ef19dce1f3303e680f1c7853799cefba shotcut-mcp-1.6.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\shotcut-mcp-1.6.0.mcpb).Hash -eq "0f2194bbe39950e703b3b2c6253bfd71ef19dce1f3303e680f1c7853799cefba"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the Shotcut MCP server?
Shotcut MCP is listed in the public MCP registry as io.github.matrodrigs/shotcut-mcp. Create, edit, validate, preview, and render Shotcut projects through AI clients. This page covers its MCPB bundle (https://github.com/matrodrigs/shotcut-mcp/releases/download/v1.6.0/shotcut-mcp-1.6.0.mcpb).
Is the Shotcut MCP server safe to use?
Shotcut MCP scores 54 out of 100 on VerifyMCP. 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 Shotcut MCP server expose?
Shotcut MCP exposes 28 tools: shotcut_status, shotcut_doctor, shotcut_capabilities, discover_media, probe_media, and 23 more. Their descriptions and schemas cost roughly 3,785 tokens of context every time the server is loaded.
What licence is the Shotcut MCP server under?
Shotcut MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.