<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chrome-Devtools-Mcp on SoloSoft</title><link>https://www.solosoft.dev/tags/chrome-devtools-mcp/</link><description>Recent content in Chrome-Devtools-Mcp on SoloSoft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 15 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.solosoft.dev/tags/chrome-devtools-mcp/index.xml" rel="self" type="application/rss+xml"/><item><title>Chrome DevTools MCP Refuses to Screenshot /etc — and Opens file:///etc/hostname Without Complaint</title><link>https://www.solosoft.dev/post/chrome-devtools-mcp-defaults-audit/</link><pubDate>Sun, 15 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/post/chrome-devtools-mcp-defaults-audit/</guid><description>&lt;p&gt;Chrome DevTools MCP is the tool Google ships so that a coding agent can drive your actual Chrome: click, type, read the console, inspect network traffic, record a performance trace. It has 56,306 stars, 4,759 forks, and 10,023,171 npm downloads in the last month. The README&amp;rsquo;s quickstart is four lines of JSON, and the project&amp;rsquo;s own security policy is unusually candid for a Google repo — it names its trusted inputs, declines to treat prompt injection as a vulnerability, and tells you to use an OS sandbox if you plan to look at code you did not write.&lt;/p&gt;
&lt;p&gt;Candid policy documents are worth testing rather than quoting. So I installed &lt;code&gt;chrome-devtools-mcp@1.13.0&lt;/code&gt;, wrote a small MCP stdio client, pointed the server at a real Chromium build, and ran the defaults.&lt;/p&gt;</description></item></channel></rss>