io.github.browserbase/mcp-server-browserbase vs io.github.theluckystrike/price-tracker-drop-alert-watch
io.github.browserbase/mcp-server-browserbase is an MCP server published by browserbase. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). io.github.theluckystrike/price-tracker-drop-alert-watch is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  io.github.browserbase/mcp-server-browserbase |  io.github.theluckystrike/price-tracker-drop-alert-watch |
|---|---|---|
| Official MCP Registry | Listed Version: 2.1.1 Downloads/month (npm): 13 299 Downloads/week (npm): 1 152 Forks (GitHub): 371 Stars (GitHub): 3 397 Not marked · First seen |
Listed Version: 0.22.9 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:f90cb76e34ba Forks (GitHub): 371 Pulls (Docker Hub): 38 548 Stars (Docker Hub): 1 Stars (GitHub): 3 397 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
| Fact | io.github.browserbase/mcp-server-browserbase | io.github.theluckystrike/price-tracker-drop-alert-watch |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 3 397 (better) | 2 (worse) |
| Pulls (Docker Hub) (differs) | 38 548 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 371 (better) | 1 (worse) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs | Remote server or your machine | Remote server or your machine |
| Transport (differs) | stdio, Streamable HTTP | Streamable HTTP, stdio |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/browserbase/mcp-server-browserbase | github.com/theluckystrike/mcp-servers |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-28 | Responded 2 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
io.github.browserbase/mcp-server-browserbase
MCP server for AI web browser automation using Browserbase and Stagehand
io.github.theluckystrike/price-tracker-drop-alert-watch
Check a shop page price now, keep a watch list, see history and target alerts. All data stays local.
How to run each
io.github.browserbase/mcp-server-browserbase As a local MCP server: npm package
claude mcp add --env "BROWSERBASE_API_KEY=<YOUR_BROWSERBASE_API_KEY>" --env "BROWSERBASE_PROJECT_ID=<YOUR_BROWSERBASE_PROJECT_ID>" --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --transport stdio mcp-server-browserbase -- npx -y @browserbasehq/mcp-server-browserbaseRequires: BROWSERBASE_API_KEY (secret), BROWSERBASE_PROJECT_ID, GEMINI_API_KEY (secret)
io.github.theluckystrike/price-tracker-drop-alert-watch As a remote MCP server
claude mcp add --transport http price-tracker-drop-alert-watch https://mcp.zovo.one/mcp/price-tracker --header "Authorization: Bearer <YOUR_TOKEN>"Requires: MCP_LICENSE_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of io.github.theluckystrike/price-tracker-drop-alert-watch responded at the last daily check. How we check endpoints
Tools each declares
The marketplaces of io.github.theluckystrike/price-tracker-drop-alert-watch publish no list of tools, so we do not compare tools.
Settings each asks for
Only io.github.browserbase/mcp-server-browserbase asks for
BROWSERBASE_API_KEY (secret)BROWSERBASE_PROJECT_ID (secret)GEMINI_API_KEY (secret)
Only io.github.theluckystrike/price-tracker-drop-alert-watch asks for
MCP_LICENSE_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.browserbase/mcp-server-browserbase · What it can do: io.github.theluckystrike/price-tracker-drop-alert-watch · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.