Browser runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 12 Aug 2026.
MCP server for loading authenticated web pages using Chrome DevTools Protocol
What the code does
We read the source, 22 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const fn = new Function(`return (async () => { ${userScript} })();`);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Browser
same job, measured the same wayMCP server for Chrome DevTools
MCP server for Chrome DevTools
MCP server for Chrome DevTools
MCP server for Safari DevTools — browser debugging and automation for AI coding agents
MCP server for AI web browser automation using Browserbase and Stagehand
Your real, logged-in Chrome as an MCP server: 59 token-efficient web-dev tools. ChromeOS included.
MCP server for Chrome Web Store — extension upload, publish, status, and rollout
Automated web QA via Chrome DevTools MCP — a11y, security, visual, env diff, CI; Aegis redaction.
Browser — questions
Answers built from our own checks of this server.