F
Warning
0/100
1 day ago

davinci-resolve-mcp

Enables AI assistants to control DaVinci Resolve Studio via MCP, providing full scripting API coverage plus workflow helpers for editing, media organization, rendering, grading, and more.

Warning. Serious findings were identified. Review the full report before connecting. 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

realmikeshu

Source: Glama

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 →

Install from

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

// key findings
🚨
Reads files from sensitive locations
Touches: ~/.config/davinci-resolve-mcp/host-model-probe.json, ~/.config/davinci-resolve-mcp
⚠️
Known vulnerabilities in dependencies: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
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.
configAAF_PROBE_PYTHON
configDAVINCI_RESOLVE_MCP_INSTALL_ROOT
configDAVINCI_RESOLVE_MCP_PYTHON
configPGPASSWORD
configPYTHON
configXDG_DATA_HOME
configRESOLVE_SCRIPT_API
configRESOLVE_SCRIPT_LIB
configPYTHONHOME
🔐 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
// quality suggestions

Tool annotations

6/389 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

383/389 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), +380 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 25369 (os.remove(f["path"])); fusion_comp deletes at line 26884 (os.remove(settings_path)); fuse_plugin deletes at line 27115 (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 88/389 tools referenced in tests (23%)

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

No access to sensitive paths

Reads sensitive paths: ~/.config/davinci-resolve-mcp/host-model-probe.json, ~/.config/davinci-resolve-mcp

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

Shell command execution

16 child_process/subprocess calls in production code — runs shell commands (bin/davinci-resolve-mcp.mjs:183, bin/davinci-resolve-mcp.mjs:236, bin/davinci-resolve-mcp.mjs:321)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets never reach shell commands

1 secret value passed to shell commands — possible command injection

Never pass secrets through shell commands. Use library APIs that accept credentials as arguments.

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.4y), 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 8 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/realmikeshu-davinci-resolve-mcp-s8iy9v?variant=verified)](https://m8ven.ai/mcp/realmikeshu-davinci-resolve-mcp-s8iy9v)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 64a24460ca7821a97e77116effcb9d7d98c12675
code hash: 6ec841041adb30405981705eea6c2ff42eb3dc692163367360ed025d50295700
verified: 8/18/2026, 9:15:30 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