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.

Kdenlive

PYPI · MCP-KDENLIVE

Inspect, edit and render Kdenlive video projects locally on Linux.

Available components

+15 this week 78 Trust /100

Last scanned (21 hours ago)

Scores higher than 73% of PyPI 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to mhbxyz/kdenlive-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 8 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 7593 tokens (~205/item across 37 items; 37 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
  • 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
  • All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 38 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • 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.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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.

  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 15 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 9 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 8 Nov 26 63

    First indexed and scored.

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 pypi/mcp-kdenlive@0.3.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo mhbxyz/kdenlive-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/mhbxyz/kdenlive-mcp/.github/workflows/release.yml@refs/tags/v0.3.0
Rekor log index 3758559336
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:9f7cb2712eb2aea456b3fdf296e43be9c6c48d86b14bd95787c358072abca817

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

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

Dependencies 28 packages
Packages resolved 28
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 37 exposed · ~7,532 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
trim_clip ~305

Change a clip's timeline bounds to [start, end) (either may be omitted); the source in/out points follow, like resizing in Kdenlive. Extending is limited by the source length. Positions are frames at the project rate; nothing ripples and nothing is overwritten (overlaps fail). A clip grouped with its audio/video counterpart is edited together with it. The result is written to `destination` with the save_project_copy rules.

NameTypeReqDescription
clipstringyesClip ref from get_timeline, '<track>@<start>' (e.g. 'V1@90'). It changes when the clip moves: read the timeline again after an edit.
destinationstringyesAbsolute path of the .kdenlive file to write (the source by default is never modified; see save_project_copy for the overwrite rules).
end–––
expected_sha256––Required to write over the source: its sha256 as last read. Tools that take `revision` use it when this is omitted.
overwriteboolean–Allow replacing an existing destination file.
pathstringyesAbsolute path of a .kdenlive project file on this machine.
revisionstringyessha256 of the project file (file.sha256 from get_timeline) that the clip ref comes from; the edit is refused if the file changed since.
sequence––Sequence uuid or name; default: active sequence.
start–––
NameTypeReqDescription
audio–––
effects–––
markers–––
media–––
relink–––
saved–yes–
subtitles–––
timeline–––
title–––
track–––

No examples provided.

update_effect ~299

Change parameters of the clip's effect at `index`; animated parameters (several keyframes) are refused. Video effects go on the video part of an audio/video pair. The result is written to `destination` with the save_project_copy rules.

NameTypeReqDescription
clipstringyesClip ref from get_timeline, '<track>@<start>' (e.g. 'V1@90'). It changes when the clip moves: read the timeline again after an edit.
destinationstringyesAbsolute path of the .kdenlive file to write (the source by default is never modified; see save_project_copy for the overwrite rules).
expected_sha256––Required to write over the source: its sha256 as last read. Tools that take `revision` use it when this is omitted.
indexintegeryesPosition of the effect in the clip's `effects` (get_timeline).
overwriteboolean–Allow replacing an existing destination file.
paramsobjectyesParameter values by name (see list_effects for names, units, ranges).
pathstringyesAbsolute path of a .kdenlive project file on this machine.
revisionstringyessha256 of the project file (file.sha256 from get_timeline) that the clip ref comes from; the edit is refused if the file changed since.
sequence––Sequence uuid or name; default: active sequence.
NameTypeReqDescription
audio–––
effects–––
markers–––
media–––
relink–––
saved–yes–
subtitles–––
timeline–––
title–––
track–––

No examples provided.

update_marker ~271

Change the marker at `position`: move it (`new_position`), or change its comment, category or duration; omitted fields are kept. Without `bin_id` the marker is a timeline **guide** (position in timeline frames); with `bin_id` it is a **clip marker** on that bin clip (position in the clip's source frames, shown on every instance). Kdenlive keeps one marker per position. The result is written to `destination` with the save_project_copy rules.

NameTypeReqDescription
bin_id––Bin clip id for a clip marker; omit for a timeline guide.
category–––
comment–––
destinationstringyesAbsolute path of the .kdenlive file to write (the source by default is never modified; see save_project_copy for the overwrite rules).
duration–––
expected_sha256––Required to write over the source: its sha256 as last read. Tools that take `revision` use it when this is omitted.
new_position–––
overwriteboolean–Allow replacing an existing destination file.
pathstringyesAbsolute path of a .kdenlive project file on this machine.
positionintegeryes–
sequence––Sequence uuid or name; default: active sequence.
NameTypeReqDescription
audio–––
effects–––
markers–––
media–––
relink–––
saved–yes–
subtitles–––
timeline–––
title–––
track–––

No examples provided.

Install

How do I install the Kdenlive MCP server?

Kdenlive runs locally as a PyPI package, launched with uvx mcp-kdenlive. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-kdenlive

# add to Claude Code
claude mcp add mhbxyz-kdenlive-mcp -- uvx mcp-kdenlive
Common questions

What is the Kdenlive MCP server?

Kdenlive is an MCP server listed in the public MCP registry as io.github.mhbxyz/kdenlive-mcp. Inspect, edit and render Kdenlive video projects locally on Linux. This page covers its PyPI package (mcp-kdenlive).

Is the Kdenlive MCP server safe to use?

Kdenlive scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 Kdenlive MCP server expose?

Kdenlive exposes 37 tools: diagnose_environment, inspect_project, get_timeline, list_project_media, probe_media, and 32 more. Their descriptions and schemas cost roughly 7,532 tokens of context every time the server is loaded.

Is the Kdenlive MCP server still maintained?

Kdenlive 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 Kdenlive MCP server under?

Kdenlive 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 Kdenlive MCP server?

VerifyMCP ran 15 checks on Kdenlive, 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 Kdenlive: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.