Name: ResolveMCP-ext
Author: captrauti

ResolveMCP-ext

Resolve MCP gaps: clip effects, Paste Attributes, frame export, photo albums, camera layouts.

Grade A Local · stdio No auth needed 10 tools v1.0.1 MIT

No reviews yet by captrautiPyPI 356 Runs on your machine, nothing hosted

100/100

trust score

downloads a day

local

runs on your machine

downloads in 30d

What it does

Resolve MCP gaps: clip effects, Paste Attributes, frame export, photo albums, camera layouts.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user resolvemcp-ext '--' uvx resolve-ext

# 2 — ask your agent for something these tools do
#   effects, clip_attrs, resolve_ext_status and 7 more

ResolveMCP-ext costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

captrauti1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts ResolveMCP-ext as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user resolvemcp-ext '--' uvx resolve-ext

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

Nothing is required, but it can take RESOLVE_SCRIPT_API (Path to the DaVinci Resolve scripting API folder. Optional: the server locates it automatically on Windows, macOS and Linux, and only uses this when set to an existing path.), RESOLVE_SCRIPT_LIB (Path to fusionscript.dll / fusionscript.so. Optional for the same reason.) if you want to set them.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Read from its source code. A server that builds its tool list when it starts can list more tools than this.

Clip effects and effect properties on TimelineItems (Resolve 21.1.2+).

Parameter	Type	Required	Notes
action	string	yes	—
params	object	no	—

Copy clip attributes between timeline items (Resolve 21.1.2+).

Parameter	Type	Required	Notes
action	string	yes	—
params	object	no	—

Health check for the resolve-ext server and its Resolve connection.

Takes no parameters.

Inspect clip placement, handle offsets, gaps and timeline enable state.

Parameter	Type	Required	Notes
action	string	yes	—
params	object	no	—

Export a frame as a still — from a timeline, a clip, or the media pool.

Parameter	Type	Required	Notes
action	string	yes	—
params	object	no	—

Folder hierarchy lookups the upstream server does not expose.

Parameter	Type	Required	Notes
action	string	yes	—
params	object	no	—

Photo albums and their items (Resolve 21.1.2+).

Parameter	Type	Required	Notes
action	string	yes	—
params	object	no	—

Node graph inspection and labelling, on a clip or a photo (21.1.2+).

Parameter	Type	Required	Notes
action	string	yes	—
params	object	no	—

Project-level gaps: render presets, audio render formats, transcription.

Parameter	Type	Required	Notes
action	string	yes	—
params	object	no	—

Lay out a multi-camera comparison timeline (Insta360 grid / split views).

Parameter	Type	Required	Notes
action	string	yes	—
params	object	no	—

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install ResolveMCP-ext or to call it, at any volume.

ATrust score 100 / 100

Release 1.0.1 · scanned 3 Nov 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score100

Findings0 threat · 0 capability

Capabilityminimal

Coveragesource

Verificationsource

Surface digest7050a5693de95efbde47a8114aa6fa4db934ec0d34bf50bb01f49a0c8cbbbf31

Score vectorthreat 100 → client 100

Term	Level	What it prices	Points
capability-exposure	minimal	capability blast radius (minimal) — client exposure if the model is manipulated	−0
verification-discount	source	publisher verification (provenance) — cryptographic build provenance ties the artifact to its source	−0
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfaceread

Implementation sourceread

Package metadataread

Live transportnot available

Tools were statically extracted from the published source (10 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.

Tool	Capability tags	Why the tag was assigned
effects	no tags
clip_attrs	no tags
resolve_ext_status	no tags
clip_position	no tags
export_frame	no tags
folder_ops	no tags
photo_albums	no tags
node_graph	no tags
project_extras	no tags
camera_comparison	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest7050a5693de95efb

Scanned2026-11-03

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.