DaVinci Resolve MCP

MCP server integration for DaVinci Resolve Studio

MCP Servers Python Grade C Listed MIT
54.2/100
Rank #645 of 1320
Compare DaVinci Resolve MCP

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-04 · 0d ago
Recent change
Rank +8

Is DaVinci Resolve MCP safe? DaVinci Resolve MCP scores 54.2/100 (Grade C), ranked #645 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.0/10; recent commits are unsigned; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 16 spots (#629 → #645)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-09-03
Grade Changed
Trust grade A → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/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.
81.7
Activity sub-score · out of 100
#317

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

Signals refreshed 2026-09-04 22:32 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
2.4k
Forks
283
Last Push
2026-09-04
today
Commits (4 wk)
282
Downloads (7d)
HN mentions (30d)
Open Issues
0
Rank Change
▼16
was #629

Analysis

HVTrust Dimensions vs MCP Servers

54.2 / 100 · 67.0% confidence

DaVinci Resolve MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.8 / 25
4.2 above avg 9.6
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
1.0 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
8.1 / 20
1.8 above avg 6.3

Activity Inputs

81.7 / 100
StarsRepository reach
20.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
11.4 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
5.0 / 10
OpenSSF Scorecard · scanned Aug 31, 2026
Signed Commits
0%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 6
CI-Tests -1
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 4
Signed-Releases -1
Token-Permissions 10
Vulnerabilities 0

Is DaVinci Resolve MCP safe?

Public trust evidence for DaVinci Resolve MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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 5.0/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?
0% 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-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.

Reputation Timeline

Signal history
Rank 4HVTrust 2Grade 2Listed 1Scorecard 1Surface 1
2026-09-04
Rank Moved
Rank dropped 16 spots (#629 → #645)
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)
2026-08-10
Newly Listed
First tracked at rank #109

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.2 Grade C
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.3 · Raw JSON