chrome-mcp-docker

The server runs inside a Docker container and connects to a separate Chrome container. It uses `puppeteer-core` to interact with Chrome via the DevTools Protocol (CDP). The `Host` header spoofing (setting 'Host: localhost' when connecting to Chrome) is a necessary workaround for Docker's networking on `host.docker.internal` and is not a general security vulnerability. The `page.evaluate()` function is used internally by specific tools (e.g., `get_computed_styles`, `scroll`) for controlled operations, not exposed as a generic `eval` tool, limiting direct arbitrary code execution. Chrome runs with `--no-sandbox` in Docker, which is common but reduces internal browser isolation if a Chrome vulnerability were exploited. Overall, the design prioritizes isolated and controlled browser interaction.