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 (17 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
save_project_as ~50

Saves the current project with a new name and location.

NameTypeReqDescription
locationstringyesThe absolute directory path where the project should be saved
namestringyesThe new name for the project

No output schema declared.

No examples provided.

scene_edit_detection ~18

Premiere Pro expanded operation: scene edit detection.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_project_items ~18

Premiere Pro expanded operation: search project items.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

select_all_clips ~19

Premiere Pro expanded operation: select all clips.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

select_clips_by_color ~21

Premiere Pro expanded operation: select clips by color.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

select_clips_by_name ~21

Premiere Pro expanded operation: select clips by name.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

select_clips_in_range ~21

Premiere Pro expanded operation: select clips in range.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

select_disabled_clips ~19

Premiere Pro expanded operation: select disabled clips.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

select_item ~16

Premiere Pro expanded operation: select item.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_active_sequence ~32

Sets the active sequence in the project.

NameTypeReqDescription
sequenceIdstringyesThe ID of the sequence to activate

No output schema declared.

No examples provided.

set_all_tracks_targeted ~21

Premiere Pro expanded operation: set all tracks targeted.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_anti_alias_quality ~21

Premiere Pro expanded operation: set anti alias quality.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_blend_mode ~19

Premiere Pro expanded operation: set blend mode.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_clip_anchor_point ~20

Premiere Pro expanded operation: set clip anchor point.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_clip_opacity ~19

Premiere Pro expanded operation: set clip opacity.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_clip_pan ~18

Premiere Pro expanded operation: set clip pan.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_clip_position ~18

Premiere Pro expanded operation: set clip position.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_clip_properties ~47

Sets Motion properties of a clip (opacity, scale, rotation, position).

NameTypeReqDescription
clipIdstringyesThe ID of the clip
propertiesobjectyesProperties to set

No output schema declared.

No examples provided.

set_clip_properties_batch ~125

Applies Motion properties (opacity/scale/rotation/position) to MANY clips in a single round-trip — the fast path for per-speaker framing across a whole rebuilt edit. ~50x faster than one set_clip_properties call per clip. Returns a per-clip result array; each result carries an `applied` map ({opacity,scale,rotation,position}) and `success` is true only when EVERY requested property was actually found and set (a missing Motion property is reported, not silently ignored).

NameTypeReqDescription
itemsarrayyesList of clip + properties pairs

No output schema declared.

No examples provided.

set_clip_rotation ~18

Premiere Pro expanded operation: set clip rotation.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_clip_scale ~18

Premiere Pro expanded operation: set clip scale.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_clip_selection ~18

Premiere Pro expanded operation: set clip selection.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_clip_speed_qe ~21

Premiere Pro expanded operation: set clip speed qe.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_clip_start_time ~20

Premiere Pro expanded operation: set clip start time.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_clip_volume ~18

Premiere Pro expanded operation: set clip volume.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_color_label ~135

Sets the color label on a project item.

NameTypeReqDescription
colorIndexnumberyesColor label index 0-15 (0=Violet, 1=Iris, 2=Caribbean, 3=Lavender, 4=Cerulean, 5=Forest, 6=Rose, 7=Mango, 8=Purple, 9=Blue, 10=Teal, 11=Magenta, 12=Tan, 13=Green, 14=Brown, 15=Yellow)
projectItemIdstringyesThe ID of the project item

No output schema declared.

No examples provided.

set_color_value ~18

Premiere Pro expanded operation: set color value.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_effect_property ~18

Premiere Pro expanded operation: set effect property.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_footage_interpretation ~69

Sets footage interpretation settings (frame rate, pixel aspect ratio) for a project item.

NameTypeReqDescription
frameRatenumber–Override frame rate
pixelAspectRationumber–Override pixel aspect ratio
projectItemIdstringyesThe ID of the project item

No output schema declared.

No examples provided.

set_frame_blend ~19

Premiere Pro expanded operation: set frame blend.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_graphics_white_luminance ~24

Premiere Pro expanded operation: set graphics white luminance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_item_in_out ~20

Premiere Pro expanded operation: set item in out.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_keyframe_interpolation ~21

Premiere Pro expanded operation: set keyframe interpolation.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_metadata ~58

Sets a project metadata value on a project item.

NameTypeReqDescription
keystringyesThe metadata key/field name
projectItemIdstringyesThe ID of the project item
valuestringyesThe metadata value to set

No output schema declared.

No examples provided.

set_offline ~17

Premiere Pro expanded operation: set offline.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_override_frame_rate ~20

Premiere Pro expanded operation: set override frame rate.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_override_pixel_aspect_ratio ~23

Premiere Pro expanded operation: set override pixel aspect ratio.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_playhead_position ~54

Sets the playhead (CTI) position in the specified sequence.

NameTypeReqDescription
sequenceIdstringyesThe ID of the sequence
timenumberyesThe time in seconds to move the playhead to

No output schema declared.

No examples provided.

set_poster_frame ~19

Premiere Pro expanded operation: set poster frame.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_project_panel_metadata ~20

Premiere Pro expanded operation: set project panel metadata.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_project_scratch_disk ~21

Premiere Pro expanded operation: set project scratch disk.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_scale_to_frame_size ~22

Premiere Pro expanded operation: set scale to frame size.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_scale_width_height ~20

Premiere Pro expanded operation: set scale width height.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_scratch_disk_path ~21

Premiere Pro expanded operation: set scratch disk path.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_sequence_audio_settings ~20

Premiere Pro expanded operation: set sequence audio settings.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_sequence_display_format ~20

Premiere Pro expanded operation: set sequence display format.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_sequence_field_type ~20

Premiere Pro expanded operation: set sequence field type.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_sequence_in_out_points ~62

Sets the in and/or out points on a sequence timeline.

NameTypeReqDescription
inPointnumber–The in point in seconds
outPointnumber–The out point in seconds
sequenceIdstringyesThe ID of the sequence

No output schema declared.

No examples provided.

set_sequence_pixel_aspect_ratio ~23

Premiere Pro expanded operation: set sequence pixel aspect ratio.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_sequence_resolution ~18

Premiere Pro expanded operation: set sequence resolution.

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.