kernel-mcp-server

The server implements OAuth 2.0 authentication via Clerk, using environment variables for all sensitive keys (Clerk secret, Redis URL, API tokens). JWTs and refresh tokens are hashed before storage in Redis, with proper TTL management. Route protection is enforced via Clerk middleware. The 'execute_playwright_code' tool allows AI agents to submit arbitrary Playwright/TypeScript code, which is then executed remotely on the Kernel platform in a sandboxed environment, not on the MCP server itself. While this is a powerful feature, the risk is shifted to the robustness of Kernel's remote sandboxing rather than a direct vulnerability within this server's codebase. No 'eval' or direct obfuscation found. Network communications with external services are standard. The use of plain API keys (if not JWT-formatted) is less robust than JWTs but relies on TLS.