updated 2026-11-10 04:07 UTC

DaVinci Resolve MCP

Repository

MCP server integration for DaVinci Resolve Studio

MCP Servers Python Listed MIT

Is DaVinci Resolve MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.6 / 10
Provenance Attested
Signed commits 24%
Last push yesterday
Advisories None known
Compare DaVinci Resolve MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: DaVinci Resolve MCP scores 87.5/100 (Grade A), ranked #67 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.6/10; 24% of recent commits are signed; no published advisory affects its latest release (davinci-resolve-mcp); last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How DaVinci Resolve MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships DaVinci Resolve MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/samuelgursky/davinci-resolve-mcp, MIT, last pushed 2026-11-09. 24% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.6/10 (scanned Oct 26, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection6
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 1
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 1
    SAST 0
    Security-Policy 4
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 5

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: davinci-resolve-mcp 5.0.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-31 OSSF Scorecard: 5.0/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues DaVinci Resolve MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How DaVinci Resolve MCP compares in MCP Servers

  1. #19 MCP Hangar 87.7 +0.2
  2. #20 Canvas MCP 87.5 ±0
  3. #21 DaVinci Resolve MCP 87.5 this agent
  4. #22 PDF Reader MCP 87.3 −0.2
  5. #23 StackQL MCP Server 87.1 −0.4

Bars show each HVTrust score; the tick marks DaVinci Resolve MCP’s 87.5.

Where the 87.5 comes from

HVTrust dimensions vs the MCP Servers average

87.5 / 100 · 100.0% confidence

DaVinci Resolve MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
16.9 / 25
6.1 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
14.1 / 17
1.8 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.7 above avg 12.2
AdoptionLog-scaled stars · package downloads
13.7 / 20
6.1 above avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-10-23
Rank Moved
Rank rose 24 spots (#84 → #60)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.6/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View MCP Servers Report missing data
84.0
Activity sub-score · out of 100
#21
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
4.0k
Forks
469
Last Push
2026-11-09
yesterday
Commits (4 wk)
170
Downloads (7d)
6,651
npm
HN mentions (30d)
—
Open Issues
8
Rank Change
▼1
was #66

Analysis

Activity Inputs

84.0 / 100
StarsRepository reach
21.6 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.4 / 20

Common questions about DaVinci Resolve MCP

Public supply-chain signals for DaVinci Resolve MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but DaVinci Resolve MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does DaVinci Resolve MCP publish package provenance?
Yes. DaVinci Resolve MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does DaVinci Resolve MCP have an OpenSSF Scorecard?
DaVinci Resolve MCP has an OpenSSF Scorecard score of 6.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is DaVinci Resolve MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does DaVinci Resolve MCP use?
DaVinci Resolve MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are DaVinci Resolve MCP's commits signed?
24% of the last 100 commits to DaVinci Resolve MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
DaVinci Resolve MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to DaVinci Resolve MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none

Maintain DaVinci Resolve MCP?

For maintainers

HVTrust scores DaVinci Resolve MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 8HVTrust 4Grade 4Scorecard 1Surface 1Delisted 1Listed 1Provenance 1MCP 1Surface 1
2026-10-23
Rank Moved
Rank rose 24 spots (#84 → #60)
2026-09-30
Rank Moved
Rank rose 26 spots (#84 → #58)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 525 spots (#600 → #75)
2026-09-23
HVTrust Changed
HVTrust up 51.8pts (33.8 → 85.6)
2026-09-22
Newly Listed
First tracked at rank #600
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-05
Grade Changed
Trust grade C → A
2026-09-05
Rank Moved
Rank rose 567 spots (#650 → #83)
2026-09-05
HVTrust Changed
HVTrust up 29.5pts (54.2 → 83.7)
2026-09-04
Rank Moved
Rank dropped 21 spots (#629 → #650)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-09-03
Grade Changed
Trust grade A → C
2026-09-03
Rank Moved
Rank dropped 562 spots (#67 → #629)
2026-09-03
HVTrust Changed
HVTrust down 29.3pts (83.5 → 54.2)
2026-08-31
Scorecard Added
OSSF Scorecard: 5.0/10
2026-08-31
Grade Changed
Trust grade B → A
2026-08-31
Rank Moved
Rank rose 64 spots (#136 → #72)
2026-08-31
HVTrust Changed
HVTrust up 10.6pts (73.0 → 83.6)
2026-08-26
Rank Moved
Rank dropped 16 spots (#114 → #130)
GitHub → npm: davinci-resolve-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 87.5 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/davinci-resolve-mcp.svg)](https://hvtracker.net/agents/davinci-resolve-mcp)
HTML:
<a href="https://hvtracker.net/agents/davinci-resolve-mcp"><img src="https://hvtracker.net/badge/davinci-resolve-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON