Resolve MCP Server

resolve-mcp PyPI v0.1.6

Published by jenkinsm13 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server with 215+ tools for DaVinci Resolve scripting API (v20.3)

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Shell/command execution in server code (resolve_mcp/ffprobe.py)MTC-SRC-002

In the server's implementation (`resolve_mcp/ffprobe.py:14`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: result = subprocess.run( [ "ffprobe", "-v", "error", "-select

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server resolve_mcp/ffprobe.py

high Shell/command execution in server code (resolve_mcp/transcode.py)MTC-SRC-002

In the server's implementation (`resolve_mcp/transcode.py:18`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: result = subprocess.run( ["ffmpeg", "-hide_banner", "-encoders"], capture_output=

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server resolve_mcp/transcode.py

Tools 121

Each tool and what it can reach — statically extracted from the published source.

  • resolve_browse_storageingests untrusted inputreads sensitive data
  • resolve_get_project_settingsingests untrusted input
  • build_statusno sensitive capability
  • build_timelineno sensitive capability
  • ingest_footageno sensitive capability
  • ingest_statusno sensitive capability
  • resolve_add_color_groupno sensitive capability
  • resolve_add_from_storageno sensitive capability
  • resolve_add_marker_atno sensitive capability
  • resolve_add_markersno sensitive capability
Show 111 more tools ↓
  • resolve_add_render_jobno sensitive capability
  • resolve_add_trackno sensitive capability
  • resolve_analyze_timelineno sensitive capability
  • resolve_apply_lutno sensitive capability
  • resolve_apply_project_presetno sensitive capability
  • resolve_auto_sync_audiono sensitive capability
  • resolve_build_from_markersno sensitive capability
  • resolve_build_statusno sensitive capability
  • resolve_build_timelineno sensitive capability
  • resolve_copy_gradeno sensitive capability
  • resolve_create_binno sensitive capability
  • resolve_create_compound_clipno sensitive capability
  • resolve_create_projectno sensitive capability
  • resolve_create_subtitlesno sensitive capability
  • resolve_delete_all_render_jobsno sensitive capability
  • resolve_delete_clipsno sensitive capability
  • resolve_delete_clips_from_timelineno sensitive capability
  • resolve_delete_color_groupno sensitive capability
  • resolve_delete_layout_presetno sensitive capability
  • resolve_delete_marker_atno sensitive capability
  • resolve_delete_markersno sensitive capability
  • resolve_delete_render_jobno sensitive capability
  • resolve_delete_timelinesno sensitive capability
  • resolve_delete_trackno sensitive capability
  • resolve_duplicate_timelineno sensitive capability
  • resolve_edit_binno sensitive capability
  • resolve_export_burn_in_presetno sensitive capability
  • resolve_export_frameno sensitive capability
  • resolve_export_layout_presetno sensitive capability
  • resolve_export_projectno sensitive capability
  • resolve_export_render_presetno sensitive capability
  • resolve_export_timelineno sensitive capability
  • resolve_get_audio_track_infono sensitive capability
  • resolve_get_cdlno sensitive capability
  • resolve_get_clip_infono sensitive capability
  • resolve_get_clip_source_infono sensitive capability
  • resolve_get_current_render_settingsno sensitive capability
  • resolve_get_infono sensitive capability
  • resolve_get_item_propertiesno sensitive capability
  • resolve_get_lutno sensitive capability
  • resolve_get_marker_datano sensitive capability
  • resolve_get_node_countno sensitive capability
  • resolve_get_playheadno sensitive capability
  • resolve_get_product_nameno sensitive capability
  • resolve_get_project_idno sensitive capability
  • resolve_get_project_presetsno sensitive capability
  • resolve_get_render_formatsno sensitive capability
  • resolve_get_render_modeno sensitive capability
  • resolve_get_render_presetsno sensitive capability
  • resolve_get_render_resolutionsno sensitive capability
  • resolve_get_render_statusno sensitive capability
  • resolve_get_timeline_infono sensitive capability
  • resolve_get_timeline_settingsno sensitive capability
  • resolve_get_versionno sensitive capability
  • resolve_get_voice_isolationno sensitive capability
  • resolve_grab_stillno sensitive capability
  • resolve_import_burn_in_presetno sensitive capability
  • resolve_import_layout_presetno sensitive capability
  • resolve_import_mediano sensitive capability
  • resolve_import_render_presetno sensitive capability
  • resolve_ingest_binno sensitive capability
  • resolve_insert_audio_at_playheadno sensitive capability
  • resolve_inspect_itemno sensitive capability
  • resolve_is_renderingno sensitive capability
  • resolve_link_clipsno sensitive capability
  • resolve_list_binsno sensitive capability
  • resolve_list_clips_on_trackno sensitive capability
  • resolve_list_color_groupsno sensitive capability
  • resolve_list_database_foldersno sensitive capability
  • resolve_list_markersno sensitive capability
  • resolve_list_projectsno sensitive capability
  • resolve_list_render_jobsno sensitive capability
  • resolve_list_timelinesno sensitive capability
  • resolve_list_volumesno sensitive capability
  • resolve_load_layout_presetno sensitive capability
  • resolve_load_projectno sensitive capability
  • resolve_load_render_presetno sensitive capability
  • resolve_move_clipsno sensitive capability
  • resolve_navigate_database_folderno sensitive capability
  • resolve_refresh_lut_listno sensitive capability
  • resolve_relink_clipsno sensitive capability
  • resolve_reset_gradesno sensitive capability
  • resolve_save_layout_presetno sensitive capability
  • resolve_save_projectno sensitive capability
  • resolve_save_render_presetno sensitive capability
  • resolve_search_clipsno sensitive capability
  • resolve_set_cdlno sensitive capability
  • resolve_set_clip_colorno sensitive capability
  • resolve_set_clip_color_on_timelineno sensitive capability
  • resolve_set_clip_enabledno sensitive capability
  • resolve_set_clip_metadatano sensitive capability
  • resolve_set_current_timelineno sensitive capability
  • resolve_set_item_propertiesno sensitive capability
  • resolve_set_playheadno sensitive capability
  • resolve_set_project_settingno sensitive capability
  • resolve_set_render_format_and_codecno sensitive capability
  • resolve_set_render_modeno sensitive capability
  • resolve_set_render_settingsno sensitive capability
  • resolve_set_timeline_settingno sensitive capability
  • resolve_set_timeline_start_timecodeno sensitive capability
  • resolve_set_track_enabledno sensitive capability
  • resolve_set_track_lockedno sensitive capability
  • resolve_set_track_nameno sensitive capability
  • resolve_set_voice_isolationno sensitive capability
  • resolve_smart_reframeno sensitive capability
  • resolve_stabilize_clipno sensitive capability
  • resolve_start_renderno sensitive capability
  • resolve_stop_renderno sensitive capability
  • resolve_switch_pageno sensitive capability
  • resolve_update_layout_presetno sensitive capability
  • resolve_update_marker_datano sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.6 latest A 93/100 2 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/resolve-mcp/badge.svg)](https://mcptrustchecker.com/registry/resolve-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/resolve-mcp"><img src="https://mcptrustchecker.com/registry/resolve-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/resolve-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan resolve-mcp --online --registry pypi

Use the free API → How scoring works

More in Design & Media