Ext Ops Panel
Open dashboard
Comparison

Chrome DevTools MCP vs Browser URL Check

Chrome DevTools MCP is an MCP server published by ChromeDevTools. Marketplaces we read that list it: 5 (Official MCP Registry, Claude Code: claude-plugins-official, Copilot CLI: github/awesome-copilot, Community GitHub marketplaces, Claude Code: claude-plugins-community). Browser URL Check is an MCP server published by sadri-dridi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceChrome DevTools MCPBrowser URL Check
Official MCP Registry Listed
Version: 1.11.0
Downloads/month (npm): 7 942 550
Downloads/week (npm): 1 737 496
Forks (GitHub): 6 528
Stars (GitHub): 53 940
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Claude Code: claude-plugins-official Listed
Version: 1.11.0
Forks (GitHub): 6 528
Stars (GitHub): 53 940
Not marked · First seen
Not listed
Copilot CLI: github/awesome-copilot Listed
Version: 1.0.1
Forks (GitHub): 6 528
Stars (GitHub): 53 940
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 1.6.0
Forks (GitHub): 6 528
Stars (GitHub): 53 940
Not marked · First seen
Not listed

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Chrome DevTools MCP vs Browser URL Check
FactChrome DevTools MCPBrowser URL Check
Marketplaces that list it (differs)5 (better)1 (worse)
Stars (GitHub) (differs)53 940 (better)0 (worse)
Forks (GitHub) (differs)6 528 (better)0 (worse)
Last release (differs)2026-10-16Not published
Where it runs (differs)On your machine (chrome-devtools-mcp)Remote server (agent-observatory-sensor.nolimit-observatory.workers.dev/s/browser-url-ok/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)8Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/chromedevtools/chrome-devtools-mcpgithub.com/sadri-dridi/named-mcp-utilities
Changes in the last 7 days (differs)70
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 34 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Chrome DevTools MCP

In its own words, on Official MCP Registry:

MCP server for Chrome DevTools

Browser URL Check

In its own words, on Official MCP Registry:

Check whether a URL can be opened. No browser is launched.

How to run each

Chrome DevTools MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio chrome-devtools-mcp -- npx -y chrome-devtools-mcp

Browser URL Check As a remote MCP server

Claude Code
claude mcp add --transport http browser-url-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/browser-url-ok/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Browser URL Check has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Chrome DevTools MCP · What it can do: Browser URL Check · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built