BrowserTap MCP vs Caniuse
BrowserTap MCP is an MCP server published by LinVireo. Marketplaces we read that list it: 1 (Official MCP Registry). Caniuse is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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
| Marketplace |  BrowserTap MCP |  Caniuse |
|---|---|---|
| Official MCP Registry | Listed Version: 0.4.12 Downloads/month (PyPI): 306 Downloads/week (PyPI): 34 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
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
| Fact | BrowserTap MCP | Caniuse |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-31 |
| Where it runs (differs) | On your machine (browsertap-mcp) | Remote server (gateway.pipeworx.io/caniuse/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 0 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/linvireo/browsertap-mcp | github.com/pipeworx-io/mcp-caniuse |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days 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
BrowserTap MCP
MCP server that drives the real Chrome you already use, through an extension and CDP.
Caniuse
caniuse MCP — browser feature support tables
How to run each
BrowserTap MCP As a local MCP server: PyPI package
claude mcp add --transport stdio browsertap-mcp -- uvx browsertap-mcpCaniuse As a remote MCP server
claude mcp add --transport http caniuse https://gateway.pipeworx.io/caniuse/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Caniuse has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of BrowserTap MCP nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Only BrowserTap MCP asks for
BROWSERTAP_BRIDGE_PORTBROWSERTAP_MODEBROWSERTAP_PREFERRED_BROWSERBROWSERTAP_STATE_DIR
Only Caniuse asks for
PIPEWORX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: BrowserTap MCP · What it can do: Caniuse · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.