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 (15 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
get_metadata ~35

Gets project metadata and XMP metadata for a project item.

NameTypeReqDescription
projectItemIdstringyesThe ID of the project item

No output schema declared.

No examples provided.

get_mogrt_component ~21

Premiere Pro expanded operation: get mogrt component.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_next_edit_point ~20

Premiere Pro expanded operation: get next edit point.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_offline_media ~19

Premiere Pro expanded operation: get offline media.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_playhead_position ~38

Gets the current playhead (CTI) position in the specified sequence.

NameTypeReqDescription
sequenceIdstringyesThe ID of the sequence

No output schema declared.

No examples provided.

get_premiere_state ~20

Premiere Pro expanded operation: get premiere state.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_project_info ~26

Gets comprehensive information about the current project including name, path, settings, and status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_project_item_info ~20

Premiere Pro expanded operation: get project item info.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_project_panel_metadata ~20

Premiere Pro expanded operation: get project panel metadata.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_project_scratch_disks ~22

Premiere Pro expanded operation: get project scratch disks.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_qe_clip_info ~21

Premiere Pro expanded operation: get qe clip info.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_render_queue_status ~32

Reports whether render queue monitoring is available. This currently returns guidance for Adobe Media Encoder rather than live queue telemetry.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_selected_clips ~33

Gets all currently selected clips in the specified sequence.

NameTypeReqDescription
sequenceIdstringyesThe ID of the sequence

No output schema declared.

No examples provided.

get_sequence_count ~18

Premiere Pro expanded operation: get sequence count.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_sequence_in_out_points ~35

Gets the in and out points of a sequence timeline.

NameTypeReqDescription
sequenceIdstringyesThe ID of the sequence

No output schema declared.

No examples provided.

get_sequence_markers_by_type ~23

Premiere Pro expanded operation: get sequence markers by type.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_sequence_settings ~36

Gets the settings for a sequence (resolution, framerate, etc.).

NameTypeReqDescription
sequenceIdstringyesThe ID of the sequence

No output schema declared.

No examples provided.

get_sequence_structure ~18

Premiere Pro expanded operation: get sequence structure.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_source_monitor_info ~20

Premiere Pro expanded operation: get source monitor info.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_source_monitor_position ~20

Premiere Pro expanded operation: get source monitor position.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_target_tracks ~18

Premiere Pro expanded operation: get target tracks.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_timeline_gaps ~20

Premiere Pro expanded operation: get timeline gaps.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_timeline_summary ~19

Premiere Pro expanded operation: get timeline summary.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_total_clip_count ~20

Premiere Pro expanded operation: get total clip count.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_track_info ~18

Premiere Pro expanded operation: get track info.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_transcript ~175

Get the active sequence's transcript, stitched across all audio source clips and mapped into sequence-time. Each segment has start/end seconds (sequence-relative), text, and optional speaker label. Returns coverage info indicating what window of the sequence has transcript data. Optionally clip to a sequence-time window with startSec / endSec. Note: clips must be transcribed in Premiere first (Window > Text > Transcript > Transcribe sequence) or this returns ok:false. 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. Filter to segments overlapping [startSec, endSec].
startSecnumber–Optional. Filter to segments overlapping [startSec, endSec].

No output schema declared.

No examples provided.

get_unused_media ~18

Premiere Pro expanded operation: get unused media.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_used_media_report ~20

Premiere Pro expanded operation: get used media report.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_value_at_time ~20

Premiere Pro expanded operation: get value at time.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_version_info ~18

Premiere Pro expanded operation: get version info.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_workspaces ~18

Premiere Pro expanded operation: get workspaces.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_xmp_metadata ~20

Premiere Pro expanded operation: get xmp metadata.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

has_proxy ~16

Premiere Pro expanded operation: has proxy.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

import_edl ~72

Reports that CMX 3600 EDL import is unavailable through this dialog-safe MCP server. Premiere's EDL API opens an interactive sequence/source-media dialog that blocks CEP. Use import_fcp_xml for unattended timeline interchange instead.

NameTypeReqDescription
filePathstringyesThe absolute path to the .edl file

No output schema declared.

No examples provided.

import_fcp_xml ~106

Imports a Final Cut Pro 7 XML (XMEML) file into the current project. Premiere creates a new sequence with the cuts/clips defined in the XML. The import requests Premiere UI suppression, but malformed or unsupported XML can still be rejected by Premiere. Use legacy FCP7 XML, not modern FCPXML 1.x from Final Cut Pro X.

NameTypeReqDescription
filePathstringyesThe absolute path to the FCP7 XML file (.xml extension typical)

No output schema declared.

No examples provided.

import_folder ~71

Imports all media files from a folder into the current Premiere Pro project.

NameTypeReqDescription
binNamestring–The name of the bin to import the media into
folderPathstringyesThe absolute path to the folder containing media files
recursiveboolean–Whether to import from subfolders recursively

No output schema declared.

No examples provided.

import_image_sequence ~18

Premiere Pro expanded operation: import image sequence.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

import_media ~73

Imports a media file (video, audio, image) into the current Premiere Pro project.

NameTypeReqDescription
binNamestring–The name of the bin to import the media into. If not provided, it will be imported into the root.
filePathstringyesThe absolute path to the media file to import

No output schema declared.

No examples provided.

import_mogrt ~110

Imports a Motion Graphics Template (.mogrt) file into a sequence.

NameTypeReqDescription
audioTrackIndexnumber–The audio track index (default: 0)
mogrtPathstringyesThe absolute path to the .mogrt file
sequenceIdstringyesThe ID of the sequence
timenumberyesThe time in seconds where the MOGRT should be placed
videoTrackIndexnumber–The video track index (default: 0)

No output schema declared.

No examples provided.

import_mogrt_from_library ~125

Imports a Motion Graphics Template from a Creative Cloud Library.

NameTypeReqDescription
audioTrackIndexnumber–The audio track index (default: 0)
libraryNamestringyesThe name of the Creative Cloud Library
mogrtNamestringyesThe name of the MOGRT in the library
sequenceIdstringyesThe ID of the sequence
timenumberyesThe time in seconds where the MOGRT should be placed
videoTrackIndexnumber–The video track index (default: 0)

No output schema declared.

No examples provided.

import_sequences ~16

Premiere Pro expanded operation: import sequences.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

import_sequences_from_project ~55

Imports sequences from another Premiere Pro project file.

NameTypeReqDescription
projectPathstringyesThe absolute path to the source .prproj file
sequenceIdsarrayyesArray of sequence IDs to import from the source project

No output schema declared.

No examples provided.

insert_from_source ~18

Premiere Pro expanded operation: insert from source.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

inspect_dom_object ~18

Premiere Pro expanded operation: inspect dom object.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

invert_selection ~16

Premiere Pro expanded operation: invert selection.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lift_selection ~16

Premiere Pro expanded operation: lift selection.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

link_audio_video ~51

Links or unlinks audio and video components of a clip.

NameTypeReqDescription
clipIdstringyesThe ID of the clip
linkedbooleanyesWhether to link (true) or unlink (false)

No output schema declared.

No examples provided.

link_selection ~16

Premiere Pro expanded operation: link selection.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_available_audio_effects ~20

Lists all available audio effects in Premiere Pro.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_available_audio_transitions ~20

Lists all available audio transitions in Premiere Pro.

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.