Video Editing Ai MCP Server

The server implements authentication via API keys and rate limiting, which are positive controls. However, several security concerns reduce confidence: the auth_middleware has weak credential storage (plaintext JSON files in ~/.meok), no actual API key validation happens in the main tools (checks are bypassable), the rate limiter uses a predictable hash-based approach vulnerable to timing attacks, and environment variable handling for monetization keys is loose. The server's functionality is benign (video metadata generation) with no dangerous I/O, but the authentication layer—critical for a monetized service—has implementation gaps that undermine its effectiveness. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.

7 files analyzed · 13 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.