video-editing-ai-mcp

The materials explicitly state that no keys or environment variables are required; based on current information, there is no direct exposure to API tokens or account secrets. Still, check whether later installation docs introduce optional third-party credentials.

No remote endpoints are declared, and the description does not indicate mandatory online processing or uploading user content; based on the available facts, no explicit data-egress path is visible. Because the README is missing, monitor for any undocumented network activity at runtime.

The system checks explicitly indicate executes-code capability; as a video-editing MCP, it is reasonable to expect local invocation of processing pipelines, scripts, or related binaries. This local execution is a normal capability for such a tool, and there is currently no evidence of unusually excessive privileges beyond its stated function.

Video editing, subtitle generation, thumbnail planning, and aspect-ratio conversion typically require reading input video/audio and writing output files, so local media file read/write access should be expected. The available materials do not show access beyond relevant working directories, but the missing README leaves fine-grained permission boundaries unclear.

The project is open-source and MIT-licensed, both of which are positive signals that reduce overall risk; however, it comes from a third-party registry, has 0 stars, unknown maintenance status, and no README, which weakens confidence in auditability and ongoing maintenance. No high-risk red flags such as closed-source distribution, spoofed origin, or clearly malicious packaging are evident.