toolsdk-mcp-registry

The registry is designed to execute external MCP servers, which could be contributed by anyone. While it attempts to provide isolation via sandbox environments (Sandock, Daytona, E2B), a critical security risk exists due to the explicit fallback to 'LOCAL' execution if a sandbox fails or for non-Node.js runtimes when using a sandbox provider. This means that a malicious MCP server, if executed locally (e.g., due to sandbox misconfiguration or failure), could lead to arbitrary code execution on the host system. The `CONTRIBUTING.md` encourages open contributions, increasing the risk if proper sandbox isolation is not strictly enforced without any local fallback for untrusted code. Hardcoded secrets are avoided in favor of environment variables.