mathias · MCP server
MCP server for Chrome DevTools
Not claimed by its maker. Is this yours? Prove it and answer the findings
Receipt history: every signed receipt for every version of this listing, and what changed between them.
MCP server for Chrome DevTools
Static scanned
Paste this into your client's MCP configuration.
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"-p",
"chrome-devtools-mcp@1.10.1",
"chrome-devtools"
]
}
}
}Or run it directly.
npx -y -p chrome-devtools-mcp@1.10.1 chrome-devtoolsPinned to 1.10.1, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
7,949,247 installs last month · build provenance signed · no published advisories · version current · checked 2026-10-06
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/chrome-devtools-mcp)Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.
MCP server that serves knowledge about your components based on your Storybook stories and documentation
Maintenance
MaintainedA release on 23 Sep 2026 (1.10.1), 0 days before this check on 23 Sep 2026. Anything later would only be more recent.
Read from the npm registry, read by the weekly version refresh.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured