davinci-resolve-mcp (samuelgursky/davinci-resolve-mcp) is an MCP server listed on the M8ven Trust Index. It scores 63 out of 100, grade C. It declares 390 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
63/100
8 days ago

davinci-resolve-mcp

MCP server integration for DaVinci Resolve Studio

→ samuelgursky/davinci-resolve-mcp· npm: davinci-resolve-mcp· listed on mcp_so

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

samuelgursky

Source: mcp.so · also listed on github_topic, npm, github_code

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

mcp.soGitHubnpmGitHub

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Known vulnerabilities in dependencies: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
390 tools verified — handlers match their declared behaviour
1 read-only tool verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: DAVINCI_MCP_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 high1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highadm-zip@0.5.17GHSA-xcpc-8h2w-3j85

adm-zip: Crafted ZIP file triggers 4GB memory allocation

highfast-xml-parser@5.9.3GHSA-8r6m-32jq-jx6q

fast-xml-parser: Repeated DOCTYPE declarations reset entity expansion limits

lowuuid@9.0.1GHSA-w5hq-g745-h8pq

uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configDAVINCI_RESOLVE_MCP_INSTALL_ROOT
configDAVINCI_RESOLVE_MCP_PYTHON
configPYTHON
configXDG_DATA_HOME
configRESOLVE_SCRIPT_API
configRESOLVE_SCRIPT_LIB
configPYTHONHOME
configDRP_MEDIA_TEMPLATE_DIR
🔐 secretDAVINCI_MCP_TOKEN
configDAVINCI_MCP_HOST
configDAVINCI_MCP_PORT
configNO_COLOR
configWT_SESSION
configTERM_PROGRAM
configXDG_CONFIG_HOME
configCODEX_HOME
configRESOLVE_SCRIPT_HOST
configRESOLVE_SCRIPT_TIMEOUT
configDAVINCI_MCP_REPO
configDAVINCI_MCP_PYTHON
configCLAUDE_DESKTOP_CONFIG
configRESOLVE_APP
configRESOLVE_SCRIPT_MODULES
configDAVINCI_RESOLVE_BRIDGE1 forces the bridge instead: it becomes the only
configPYTHON3HOMEenvironment variable, then /usr/local/bin/python3. Homebrew,
configDAVINCI_RESOLVE_MCP_UPDATE_CHANNEL
configDAVINCI_RESOLVE_MCP_OLLAMA_URL
configDAVINCI_RESOLVE_MCP_EMBED_MODEL
configPROGRAMDATAinstalling, listing and serving from both %% and %APPDATA% on
configPROGRAMFILES
configDAVINCI_RESOLVE_MCP_STATE_DIR
// quality suggestions

Tool annotations

6/390 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

384/390 tools missing one or more hints — setup (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); resolve_control (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); layout_presets (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +381 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

6 tools perform destructive updates without destructiveHint — gallery_stills deletes at line 27575 (os.rmdir(folder_path)); fusion_comp deletes at line 29305 (os.remove(settings_path)); fuse_plugin deletes at line 29537 (os.unlink(path))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool test coverage

Only 95/390 tools referenced in tests (24%)

Write tests that reference each tool by name so every tool has at least one test.

Production dependencies are patched

0 critical, 2 high severity in production deps — adm-zip@0.5.17 (high), fast-xml-parser@5.9.3 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

2/8 production deps stale: fzstd@2024-03-15 (2.5y), zstd-codec@2024-07-27 (2.1y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/samuelgursky/davinci-resolve-mcp?variant=verified)](https://m8ven.ai/mcp/samuelgursky/davinci-resolve-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 0b00099de5398f91825992ae8866c4018c788e16
code hash: c1a1f7ff335831f2e72e0d4e4ee701f1202ba3705e0f3ae3a1c02bf2fea0ecd1
verified: 9/2/2026, 8:02:42 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client