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.

Scout for Premiere Pro

MCPB · SCOUT-PREMIERE-MCP-0.3.0.MCPB · SCANNED SEP 21

Drive Adobe Premiere Pro from an AI agent: transcript search, markers, cuts, exports, 277 tools.

+3 this week 47 Trust /100
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 Security13
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • No install/post-install scripts declared.Pass
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.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 20 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 Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

mcpb · scout-premiere-mcp-0.3.0.mcpb

Download bundle
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 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +3
    • Stability: unverified → 0.23 functional
  • 1 Sept 26 38

    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 Sept 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

Background: How many MCP packages publish verified provenance →

MCP tools · 277 exposed · ~14,753 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
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.

NameTypeReqDescription
sequenceIdstringyesThe ID of the sequence
settingsobjectyesSettings 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.

NameTypeReqDescription
inPointnumberyesThe in point in seconds
outPointnumberyesThe out point in seconds
sequenceIdstringyesThe 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).

NameTypeReqDescription
baseDbnumberyesSustained level in dB (e.g. -25 for music bed under voice)
clipEndTimenumberClip end time anchor for last keyframe; if omitted, last duck window endTime + 1s is used
clipIdstringyesThe ID of the music/SFX clip to apply ducking to
clipStartTimenumberClip start time anchor for first keyframe (default 0)
duckingWindowsarrayyesWindows where the clip should duck below baseDb. Empty array = sustained baseDb only.
fadeSecondsnumberRamp 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.

NameTypeReqDescription
clipIdstringyesThe ID of the clip
maintainAudiobooleanWhether to maintain audio pitch when changing speed
speednumberyesSpeed 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.

NameTypeReqDescription
clipIdstringyesThe ID of the clip to split
splitTimenumberyesThe 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.

NameTypeReqDescription
clipIdstringyesThe ID of the clip to stabilize
methodstringStabilization method
smoothnessnumberStabilization 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.

NameTypeReqDescription
sequenceIdstringyesThe sequence ID (GUID) as returned in the "id" field by list_sequences or get_active_sequence
trackIndexnumberyesThe index of the video track
visiblebooleanyesWhether 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.

NameTypeReqDescription
clipIdstringyesThe ID of the clip on the timeline to trim
durationnumberAlternative: set the desired timeline duration in seconds; cannot be combined with outPoint
inPointnumberThe new in point in seconds from the start of the clip
outPointnumberThe 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.

NameTypeReqDescription
colorNew colour. Marker colour — a name (green, red, purple, orange, yellow, white, blue, cyan) or an index 0-7. Defaults to green.
commentstringNew comment
markerIdstringyesThe ID of the marker to update
namestringNew name for the marker
sequenceIdstringyesThe 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.

NameTypeReqDescription
checkGapsbooleanWhen true, timeline gaps are reported as warnings. Defaults to true.
outputPathstringOptional intended export output path. When provided, the parent folder is checked.
presetPathstringOptional Adobe Media Encoder .epr preset path. When provided, the file is checked.
requireNonEmptyTimelinebooleanWhen true, an empty timeline is an error. Defaults to true.
sequenceIdstringOptional 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.

Common questions

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 47 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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.