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

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

0 this week 48 Trust /100

Last scanned (14 hours ago)

Scores higher than 78% of MCPB 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 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.

What we tested

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 →

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.

  • 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
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 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 →

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
delete_preview_files ~18

Premiere Pro expanded operation: delete preview files.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

delete_sequence ~30

Deletes a sequence from the project.

NameTypeReqDescription
sequenceIdstringyesThe ID of the sequence to delete

No output schema declared.

No examples provided.

deselect_all_clips ~21

Premiere Pro expanded operation: deselect all clips.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

detach_proxy ~16

Premiere Pro expanded operation: detach proxy.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

detect_scene_edits ~115

Detects scene changes in selected clips and optionally adds cuts or markers.

NameTypeReqDescription
actionstring–Action to take at detected edit points
allowUnsafeSynchronousboolean–Actually invoke Premiere scene detection synchronously; can block CEP for a long time
applyCutsToLinkedAudioboolean–Whether to apply cuts to linked audio
sensitivitystring–Detection sensitivity (e.g., "Low", "Medium", "High")
sequenceIdstringyesThe ID of the sequence

No output schema declared.

No examples provided.

detect_silence ~234

Analyzes a media file's audio for silent stretches using ffmpeg's silencedetect filter, run locally via child_process -- NOT via Premiere's scripting API, which has no audio-level/RMS reading capability at all (confirmed: every audio tool in this codebase only writes levels, never reads them). Requires ffmpeg on PATH; returns an explicit error if it is not found rather than failing silently. This is DETECTION ONLY -- it does not cut or modify anything. Use the returned intervals with split_clip/ripple_delete/razor_timeline_at_time if you want to remove the silence.

NameTypeReqDescription
mediaPathstring–Direct filesystem path to the media file to analyze
minDurationSecondsnumber–Minimum duration in seconds for a quiet stretch to be reported as silence (default 1.5)
noiseThresholdDbnumber–Silence threshold in dBFS, e.g. -30 (default -30). Audio quieter than this is considered silent.
projectItemIdstring–Project item ID to resolve to a media path instead of passing mediaPath directly

No output schema declared.

No examples provided.

duplicate_clip ~53

Duplicates a clip on the timeline.

NameTypeReqDescription
clipIdstringyesThe ID of the clip to duplicate
offsetnumber–Time offset in seconds for the duplicate (default: places immediately after original)

No output schema declared.

No examples provided.

duplicate_sequence ~137

Creates a copy of an existing sequence with a new name. Set clearContents=true to get an EMPTY copy that inherits the source sequence's exact settings (frame rate, resolution, track layout) — the reliable way to auto-create a correctly-specced blank target, since create_sequence ignores frame rate.

NameTypeReqDescription
clearContentsboolean–When true, remove all clips from the copy so it is empty but keeps the source's frame rate/resolution/track layout. Default false (full copy).
newNamestringyesThe name for the new sequence copy
sequenceIdstringyesThe ID of the sequence to duplicate

No output schema declared.

No examples provided.

enable_all_clips ~153

Enable every clip on every video and audio track of the active sequence (sets disabled=false). Useful when a previous Multi-Cam edit, Lift, or manual disable left a bunch of clips muted/hidden and the user wants to restore them all at once instead of clicking each. The whole batch is a single undo entry (Ctrl+Z rolls it back). Calling on a clip that's already enabled is a no-op, so this is safe to run on any sequence — there is no 'enabled some, disabled some' mode. No arguments. The result always includes activeSequence {name, id} — the sequence this call actually ran against. Compare it across calls to detect the user switching sequences in Premiere mid-session.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

enable_disable_clip ~48

Enables or disables a clip on the timeline.

NameTypeReqDescription
clipIdstringyesThe ID of the clip
enabledbooleanyesWhether to enable (true) or disable (false)

No output schema declared.

No examples provided.

encode_file ~16

Premiere Pro expanded operation: encode file.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

encode_project_item ~18

Premiere Pro expanded operation: encode project item.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

execute_extendscript ~135

Run arbitrary ExtendScript inside Premiere Pro via the Scout CEP helper and return the script's string result. The QE DOM is available (app.enableQE() has been called). The script must be self-contained — each call is an independent eval with no shared state beyond Premiere's DOM. Return a JSON-shaped string for structured results. POWER TOOL: this can do anything Premiere scripting can, including destructive changes with no undo grouping — prefer the named tools when one exists, and back up the sequence before structural timeline edits.

NameTypeReqDescription
scriptstringyesExtendScript source to evaluate. Its final expression's string coercion is the result.

No output schema declared.

No examples provided.

export_aaf ~131

Exports a sequence as an AAF file for interchange with other editing/audio applications.

NameTypeReqDescription
bitsPerSamplenumber–Audio bits per sample (default: 16)
explodeToMonoboolean–Whether to explode audio to mono (default: false)
mixDownVideoboolean–Whether to mix down video (default: true)
outputPathstringyesThe absolute file path for the exported AAF file
sampleRatenumber–Audio sample rate (default: 48000)
sequenceIdstringyesThe ID of the sequence to export

No output schema declared.

No examples provided.

export_as_fcp_xml ~53

Exports a sequence as Final Cut Pro XML.

NameTypeReqDescription
outputPathstringyesThe absolute file path for the exported XML file
sequenceIdstringyesThe ID of the sequence to export

No output schema declared.

No examples provided.

export_as_project ~18

Premiere Pro expanded operation: export as project.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

export_frame ~78

Exports a single frame from a sequence as an image file.

NameTypeReqDescription
formatstring–The image format
outputPathstringyesThe absolute path where the image file will be saved
sequenceIdstringyesThe ID of the sequence
timenumberyesThe time in seconds to export the frame from

No output schema declared.

No examples provided.

export_markers_csv ~182

Write a CSV of every marker matching `prefix` to a file in the Scout plugin's UXP data folder. Columns: startSec, endSec, durationSec, startTimecode (HH:MM:SS), label, reason. Returns the absolute path of the written file. Common usage: prefix='Scout/Quote:' filename='scout-quotes.csv' for quote pulls, or prefix='Scout/Broll:' filename='scout-broll-cues.csv' for B-roll cues. The result always includes activeSequence {name, id} — the sequence this call actually ran against. Compare it across calls to detect the user switching sequences in Premiere mid-session.

NameTypeReqDescription
filenamestring–Output filename in the UXP data folder. Default 'scout-markers.csv'.
prefixstringyesMarker name prefix to include (required).

No output schema declared.

No examples provided.

export_omf ~19

Premiere Pro expanded operation: export omf.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

export_sequence ~238

Renders and exports a sequence to a video file. This is for creating the final video.

NameTypeReqDescription
allowOverwriteboolean–Allow writing to an existing output file. Defaults to false.
formatstring–Deprecated hint only; the .epr preset controls codec/container.
outputPathstringyesThe absolute path where the final video file will be saved
presetNamestring–Exact user preset display name or filename stem. Must resolve to exactly one discovered .epr preset.
presetPathstring–Absolute path to an export preset file (.epr). Required unless presetName uniquely resolves through get_encoder_presets.
qualitystring–Deprecated hint only; the .epr preset controls quality.
removeOnCompletionboolean–Pass AME removeOnCompletion. Defaults to true to preserve existing queue behavior.
resolutionstring–Deprecated hint only; the .epr preset controls resolution.
sequenceIdstringyesThe ID of the sequence to export
sourceRangestring–Export source range. Defaults to entire. Requested ranges are never silently substituted.

No output schema declared.

No examples provided.

extract_selection ~16

Premiere Pro expanded operation: extract selection.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

find_items_by_media_path ~22

Premiere Pro expanded operation: find items by media path.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

find_project_item_by_name ~58

Searches for project items by name. Useful for finding media files, sequences, or bins.

NameTypeReqDescription
namestringyesThe name to search for (case-insensitive partial match)
typestring–Filter by item type

No output schema declared.

No examples provided.

find_words ~297

Search the active sequence's transcript for a word or phrase and get WORD-ACCURATE sequence times for each match — the MCP equivalent of clicking a word in Premiere's Text panel. Returns startSec/endSec of the matched words plus timecodes (HH:MM:SS:FF; drop-frame HH:MM:SS;FF on 29.97/59.94 sequences), surrounding context, speaker, and whether the match ends a sentence (eos - a natural cut boundary). Use this to snap marker/cut points precisely instead of relying on get_transcript's sentence-level segment starts. Matching is case- and punctuation-insensitive. Optionally restrict to a sequence-time window with startSec/endSec. Requires transcribed clips, same as get_transcript. The result always includes activeSequence {name, id} — the sequence this call actually ran against. Compare it across calls to detect the user switching sequences in Premiere mid-session.

NameTypeReqDescription
endSecnumber–Optional. Only match words starting at/before this sequence time.
maxMatchesnumber–Optional. Max matches to return (default 8). totalMatches in the result reports the full count.
querystringyesWord or phrase to find, e.g. 'discovering this art by accident'. Multi-word queries match consecutive spoken words.
startSecnumber–Optional. Only match words starting at/after this sequence time.

No output schema declared.

No examples provided.

freeze_frame ~16

Premiere Pro expanded operation: freeze frame.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_active_sequence ~108

Read structural info about the active Premiere sequence: name, frame rate, total duration in seconds, first-frame timecode (zero point), and per-track summaries (index, name, clip count). No arguments. Use this first to confirm a sequence is open and to learn its duration before asking for transcripts or placing markers. The result always includes activeSequence {name, id} — the sequence this call actually ran against. Compare it across calls to detect the user switching sequences in Premiere mid-session.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_all_project_paths ~20

Premiere Pro expanded operation: get all project paths.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_bin_contents ~18

Premiere Pro expanded operation: get bin contents.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_capabilities ~89

Reports the local MCP runtime, installed bridge status, tool/resource/prompt catalog sizes, and supported versus experimental integration surfaces. Set checkConnection to true to run the read-only live Premiere connection check; otherwise no Premiere request is made.

NameTypeReqDescription
checkConnectionboolean–When true, run verify_premiere_connection and include its live result. Defaults to false so capability discovery is fast and non-invasive.

No output schema declared.

No examples provided.

get_clip_adjustment_layer ~21

Premiere Pro expanded operation: get clip adjustment layer.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_clip_at_playhead ~22

Premiere Pro expanded operation: get clip at playhead.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_clip_at_position ~73

Gets the clip at a specific time position on a track.

NameTypeReqDescription
sequenceIdstringyesThe ID of the sequence
timenumberyesThe time position in seconds
trackIndexnumberyesThe track index (0-based)
trackTypestringyesThe type of track

No output schema declared.

No examples provided.

get_clip_links ~18

Premiere Pro expanded operation: get clip links.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_clip_markers ~19

Premiere Pro expanded operation: get clip markers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_clip_properties ~122

Gets detailed properties of a clip, INCLUDING current Motion values (opacity/scale/rotation/position). Position is returned both normalized (0..1) and in PIXELS (`motion.position`, using the sequence frame size) so you can verify or copy framing without exporting a frame. Pass sequenceId when the clip ID came from list_sequence_tracks for a non-active sequence.

NameTypeReqDescription
clipIdstringyesThe ID of the clip
sequenceIdstring–Optional sequence ID to search. If omitted, searches the active sequence first, then all sequences.

No output schema declared.

No examples provided.

get_clip_speed ~18

Premiere Pro expanded operation: get clip speed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_color_label ~34

Gets the color label index of a project item.

NameTypeReqDescription
projectItemIdstringyesThe ID of the project item

No output schema declared.

No examples provided.

get_color_space ~18

Premiere Pro expanded operation: get color space.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_duplicate_media ~18

Premiere Pro expanded operation: get duplicate media.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_effect_properties ~18

Premiere Pro expanded operation: get effect properties.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_export_file_extension ~20

Premiere Pro expanded operation: get export file extension.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_footage_interpretation ~51

Gets the footage interpretation settings (frame rate, pixel aspect ratio, field type, etc.) for a project item.

NameTypeReqDescription
projectItemIdstringyesThe ID of the project item

No output schema declared.

No examples provided.

get_full_clip_info ~20

Premiere Pro expanded operation: get full clip info.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_full_project_overview ~21

Premiere Pro expanded operation: get full project overview.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_full_sequence_info ~20

Premiere Pro expanded operation: get full sequence info.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_graphics_white_luminance ~24

Premiere Pro expanded operation: get graphics white luminance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_insertion_bin ~19

Premiere Pro expanded operation: get insertion bin.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_item_info ~18

Premiere Pro expanded operation: get item info.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_keyframes ~60

Gets all keyframes for a clip component parameter.

NameTypeReqDescription
clipIdstringyesThe ID of the clip
componentNamestringyesThe display name of the component
paramNamestringyesThe display name of the parameter

No output schema declared.

No examples provided.

get_linked_items ~19

Premiere Pro expanded operation: get linked items.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

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 bundle

The 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.

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