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.

io.github.JXUE0/opencut-controller

NPM · OPENCUT-CONTROLLER

Professional MCP server for video editing automation with OpenCut.

Available components

0 this week 79 Trust /100

Last scanned (22 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 Security92
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • 31 of 95 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 (MIT).Pass
  • Actively maintained (last published 124 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 5686 tokens (~34/item across 164 items; 161 tools + 3 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 Coverage82
  • 99% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
  • 46% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 14 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "project_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 162 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 (15)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

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.

  • 20 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
    • Stability: pass → 0.97 functional
  • 17 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 13 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 9 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
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/opencut-controller@1.30.0

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 →

Install scripts 1 script
Hook Tier Command
postinstall Not reviewed playwright install chromium

Background: Why install scripts are a supply-chain risk →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 161 exposed · ~5,638 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
timeline_track_add ~38

Add a new track to the timeline

NameTypeReqDescription
indexnumber–Optional index to insert at
typestringyesTrack type

No output schema declared.

No examples provided.

timeline_track_get ~23

Get a track by ID

NameTypeReqDescription
trackIdstringyes–

No output schema declared.

No examples provided.

timeline_track_list ~17

List all tracks in the current scene

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

timeline_track_remove ~23

Remove a track by ID

NameTypeReqDescription
trackIdstringyes–

No output schema declared.

No examples provided.

timeline_track_toggle_mute ~40

Toggle mute on a track

NameTypeReqDescription
mutedboolean–Set mute state explicitly (omit to toggle)
trackIdstringyes–

No output schema declared.

No examples provided.

timeline_track_toggle_visibility ~39

Toggle visibility on a track

NameTypeReqDescription
hiddenboolean–Set hidden state explicitly (omit to toggle)
trackIdstringyes–

No output schema declared.

No examples provided.

transcription_add_captions_to_timeline ~74

Add caption text elements to the timeline from segments

NameTypeReqDescription
colorstring–Text color (default: #ffffff)
fontSizenumber–Font size (default: 48)
segmentsarrayyes–
ynumber–Y position (default: 400)

No output schema declared.

No examples provided.

transcription_cancel ~14

Cancel an in-progress transcription

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

transcription_generate_captions ~82

Generate caption elements from a transcription result

NameTypeReqDescription
colorstring–Caption color hex (default: #ffffff)
fontSizenumber–Caption font size (default: 48)
segmentsarrayyesTranscription segments from transcribe result
wordsPerCaptionnumber–Words per caption element (default: 3)

No output schema declared.

No examples provided.

transcription_get_state ~23

Get the current transcription state (isTranscribing, progress, result)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

transcription_transcribe ~71

Transcribe audio/video from a media asset. Runs in browser Web Worker. Polls until complete.

NameTypeReqDescription
languagestring–Language code (default: en)
mediaIdstringyesMedia asset ID to transcribe
modelstring–Model to use (default: whisper-small)

No output schema declared.

No examples provided.

Install

How do I install the io.github.JXUE0/opencut-controller MCP server?

io.github.JXUE0/opencut-controller runs locally as an npm package, launched with npx -y opencut-controller. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · opencut-controller

# add to Claude Code
claude mcp add jxue0-opencut-controller -- npx -y opencut-controller
Common questions

What is the io.github.JXUE0/opencut-controller MCP server?

io.github.JXUE0/opencut-controller is an MCP server listed in the public MCP registry as io.github.JXUE0/opencut-controller. Professional MCP server for video editing automation with OpenCut. This page covers its npm package (opencut-controller).

Is the io.github.JXUE0/opencut-controller MCP server safe to use?

io.github.JXUE0/opencut-controller scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 io.github.JXUE0/opencut-controller MCP server expose?

io.github.JXUE0/opencut-controller exposes 161 tools: project_create, project_load, project_save, project_delete, project_list, and 156 more. Their descriptions and schemas cost roughly 5,638 tokens of context every time the server is loaded.

Is the io.github.JXUE0/opencut-controller MCP server still maintained?

io.github.JXUE0/opencut-controller 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 io.github.JXUE0/opencut-controller MCP server under?

io.github.JXUE0/opencut-controller declares the MIT 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 io.github.JXUE0/opencut-controller MCP server?

VerifyMCP ran 15 checks on io.github.JXUE0/opencut-controller, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.JXUE0/opencut-controller: Security disclosure. 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.