Remotion MCP Editor
An always-on, data-driven Remotion editing and rendering engine exposed through Streamable HTTP MCP. Agents edit validated timeline data; the service never exposes source-code or shell access.
Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
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
maverick-software
Source: Glama
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
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
fastify vulnerable to X-Forwarded-* spoofing under trustProxy hop-count
fastify vulnerable to schema validation bypass via root primitive coercion mismatch
Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock
DATA_DIRSet , REMOTION_TOKEN_SHA256, and REMOTION_LICENSE_KEY, then start npm run start:api and npm run start:worker in separate terminals.LOG_LEVELREMOTION_LICENSE_KEYSet DATA_DIR, REMOTION_TOKEN_SHA256, and , then start npm run start:api and npm run start:worker in separate terminals.REMOTION_SERVE_URLREMOTION_TOKEN_SHA256Set DATA_DIR, , and REMOTION_LICENSE_KEY, then start npm run start:api and npm run start:worker in separate terminals.Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
11/11 tools missing one or more hints — get_service_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_projects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_project (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 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.
Tool inputs are validated
10/11 tool handlers declare input schemas (91%)
Declare an inputSchema with zod/joi/yup on every tool definition.
License file
No license file
Add a LICENSE file (MIT, Apache-2.0, etc.).
Tool test coverage
Only 0/11 tools referenced in tests (0%)
Write tests that reference each tool by name so every tool has at least one test.
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.
[](https://m8ven.ai/mcp/maverick-software/remotion-mcp-editor)?variant=verified to the badge URL.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