Scout for Premiere Pro
MCPB · SCOUT-PREMIERE-MCP-0.3.0.MCPB
Drive Adobe Premiere Pro from an AI agent: transcript search, markers, cuts, exports, 277 tools.
Available components
Last scanned (18 hours ago)
Scores higher than 78% 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 & Transparency32
- 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
- License check failed: the license (SEE LICENSE IN https://www.trevorohare.com/policies) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 65 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 14753 tokens (~53/item across 277 items; 277 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 19 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_markers" implies "remove" 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 277 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.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
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.
- Malware scan in Supply Chain Security (scores 0 for this)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.
- Known CVEs in Supply Chain Security (scores 0 for this)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).
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)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).
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 →
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 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.
- 3 Nov 26 0
- Maintenance: unverified → pass ▲ functional
- Stability: pass → 0.93 functional
- 1 Nov 26 −1
- Maintenance: pass → unverified ▼ functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 +1
- Maintenance: unverified → pass ▲ functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
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/tro2789/scout-premiere-mcp/releases/download/v0.3.0/scout-premiere-mcp-0.3.0.mcpb@0.3.0
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 →
set_sequence_settings ~84
Updates sequence settings. Applies width, height, frameRate and pixelAspectRatio, reads the values back afterwards, and reports any field Premiere accepted but did not actually change. Frame size CAN be changed after creation, contrary to an earlier note in this codebase.
| Name | Type | Req | Description |
|---|---|---|---|
| sequenceId | string | yes | The ID of the sequence |
| settings | object | yes | Settings to update |
No output schema declared.
No examples provided.
set_source_in_out ~20
Premiere Pro expanded operation: set source in out.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_start_time ~18
Premiere Pro expanded operation: set start time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_target_track ~18
Premiere Pro expanded operation: set target track.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_time_interpolation ~19
Premiere Pro expanded operation: set time interpolation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_transcode_on_ingest ~23
Premiere Pro expanded operation: set transcode on ingest.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_uniform_scale ~18
Premiere Pro expanded operation: set uniform scale.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_work_area ~59
Sets the work area in/out points for a sequence.
| Name | Type | Req | Description |
|---|---|---|---|
| inPoint | number | yes | The in point in seconds |
| outPoint | number | yes | The out point in seconds |
| sequenceId | string | yes | The ID of the sequence |
No output schema declared.
No examples provided.
set_workspace ~16
Premiere Pro expanded operation: set workspace.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_xmp_metadata ~20
Premiere Pro expanded operation: set xmp metadata.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_zero_point ~18
Premiere Pro expanded operation: set zero point.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
setup_ducking ~248
High-level wrapper around add_audio_keyframes that builds a ducking curve from a base level + ducking windows. Computes 4 keyframes per window (pre-fade, duck-in, duck-out, post-fade) plus boundary keyframes at clip start/end. Replaces the manual "8 keyframes per video" pattern from Sprint 3. Times are clip-source-time absolute (same convention as add_audio_keyframes).
| Name | Type | Req | Description |
|---|---|---|---|
| baseDb | number | yes | Sustained level in dB (e.g. -25 for music bed under voice) |
| clipEndTime | number | – | Clip end time anchor for last keyframe; if omitted, last duck window endTime + 1s is used |
| clipId | string | yes | The ID of the music/SFX clip to apply ducking to |
| clipStartTime | number | – | Clip start time anchor for first keyframe (default 0) |
| duckingWindows | array | yes | Windows where the clip should duck below baseDb. Empty array = sustained baseDb only. |
| fadeSeconds | number | – | Ramp time for each transition (default 0.2s = 6 frames @30fps) |
No output schema declared.
No examples provided.
slide_edit ~16
Premiere Pro expanded operation: slide edit.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
slip_edit ~16
Premiere Pro expanded operation: slip edit.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
speed_change ~73
Changes the playback speed of a clip.
| Name | Type | Req | Description |
|---|---|---|---|
| clipId | string | yes | The ID of the clip |
| maintainAudio | boolean | – | Whether to maintain audio pitch when changing speed |
| speed | number | yes | Speed multiplier (0.1 = 10% speed, 2.0 = 200% speed) |
No output schema declared.
No examples provided.
split_clip ~55
Splits a clip at a specific time point, creating two separate clips.
| Name | Type | Req | Description |
|---|---|---|---|
| clipId | string | yes | The ID of the clip to split |
| splitTime | number | yes | The time in seconds where to split the clip |
No output schema declared.
No examples provided.
stabilize_clip ~57
Applies video stabilization to reduce camera shake.
| Name | Type | Req | Description |
|---|---|---|---|
| clipId | string | yes | The ID of the clip to stabilize |
| method | string | – | Stabilization method |
| smoothness | number | – | Stabilization smoothness (0-100) |
No output schema declared.
No examples provided.
start_batch_encode ~18
Premiere Pro expanded operation: start batch encode.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
stop_playback ~17
Premiere Pro expanded operation: stop playback.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
toggle_track_visibility ~123
Shows or hides a video track by toggling its output (the eye icon) in the specified sequence. The sequence does not have to be the active one. This is track OUTPUT, not track targeting -- use set_target_track for the V1/A1 patch buttons.
| Name | Type | Req | Description |
|---|---|---|---|
| sequenceId | string | yes | The sequence ID (GUID) as returned in the "id" field by list_sequences or get_active_sequence |
| trackIndex | number | yes | The index of the video track |
| visible | boolean | yes | Whether to show (true) or hide (false) |
No output schema declared.
No examples provided.
trim_clip ~113
Adjusts the in and out points of a clip on the timeline, effectively shortening it.
| Name | Type | Req | Description |
|---|---|---|---|
| clipId | string | yes | The ID of the clip on the timeline to trim |
| duration | number | – | Alternative: set the desired timeline duration in seconds; cannot be combined with outPoint |
| inPoint | number | – | The new in point in seconds from the start of the clip |
| outPoint | number | – | The new out point in seconds from the start of the clip; cannot be combined with duration |
No output schema declared.
No examples provided.
undo ~15
Performs an undo operation in Premiere Pro.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
unlink_selection ~16
Premiere Pro expanded operation: unlink selection.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
unnest_sequence ~18
Premiere Pro expanded operation: unnest sequence.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_marker ~136
Updates an existing marker's properties in the specified sequence. The sequence does not have to be the active one.
| Name | Type | Req | Description |
|---|---|---|---|
| color | – | – | New colour. Marker colour — a name (green, red, purple, orange, yellow, white, blue, cyan) or an index 0-7. Defaults to green. |
| comment | string | – | New comment |
| markerId | string | yes | The ID of the marker to update |
| name | string | – | New name for the marker |
| sequenceId | string | yes | The sequence ID (GUID) as returned in the "id" field by list_sequences or get_active_sequence |
No output schema declared.
No examples provided.
validate_project_for_export ~167
Runs a non-destructive export readiness audit for the active or requested sequence. Checks timeline content, offline media, missing export preset/output folder inputs, gaps, markers, and basic audio/video track state before an agent queues an export.
| Name | Type | Req | Description |
|---|---|---|---|
| checkGaps | boolean | – | When true, timeline gaps are reported as warnings. Defaults to true. |
| outputPath | string | – | Optional intended export output path. When provided, the parent folder is checked. |
| presetPath | string | – | Optional Adobe Media Encoder .epr preset path. When provided, the file is checked. |
| requireNonEmptyTimeline | boolean | – | When true, an empty timeline is an error. Defaults to true. |
| sequenceId | string | – | Optional sequence ID to validate. Defaults to the active sequence. |
No output schema declared.
No examples provided.
verify_premiere_connection ~52
Read-only readiness check for the live CEP bridge and Premiere Pro host. Run this before an editing workflow to confirm the bridge responds and report the Premiere version, project, and active sequence without changing the project.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Scout for Premiere Pro MCP server?
Scout for Premiere Pro 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. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · scout-premiere-mcp-0.3.0.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
What is the Scout for Premiere Pro MCP server?
Scout for Premiere Pro is an MCP server listed in the public MCP registry as io.github.tro2789/scout-premiere-mcp. Drive Adobe Premiere Pro from an AI agent: transcript search, markers, cuts, exports, 277 tools. This page covers its MCPB bundle (https://github.com/tro2789/scout-premiere-mcp/releases/download/v0.3.0/scout-premiere-mcp-0.3.0.mcpb).
Is the Scout for Premiere Pro MCP server safe to use?
Scout for Premiere Pro scores 48 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 Scout for Premiere Pro MCP server expose?
Scout for Premiere Pro exposes 277 tools: get_active_sequence, get_transcript, find_words, list_markers, place_markers, and 272 more. Their descriptions and schemas cost roughly 14,753 tokens of context every time the server is loaded.
What did VerifyMCP test on the Scout for Premiere Pro MCP server?
VerifyMCP ran 12 checks on Scout for Premiere Pro, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Scout for Premiere Pro: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.