Ext Ops Panel
Open dashboard
Comparison

commerce-readiness vs io.github.browserbase/mcp-server-browserbase

commerce-readiness is a plugin bundle for AI coding tools published by Rohit Bajaj, Julekha Khatun. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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). As of our marketplace pass on 2026-10-15. 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
Marketplacecommerce-readinessio.github.browserbase/mcp-server-browserbase
Community marketplace orcaqubits/agentic-commerce-claude-plugins Listed
Version: 1.0.0
Forks (GitHub): 18
Stars (GitHub): 39
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.1.1
Downloads/month (npm): 19 182
Downloads/week (npm): 2 969
Forks (GitHub): 372
Stars (GitHub): 3 400
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:f90cb76e34ba
Forks (GitHub): 372
Pulls (Docker Hub): 38 075
Stars (Docker Hub): 1
Stars (GitHub): 3 400
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

commerce-readiness vs io.github.browserbase/mcp-server-browserbase
Factcommerce-readinessio.github.browserbase/mcp-server-browserbase
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)39 (worse)3 400 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub38 075
Forks (GitHub) (differs)18 (worse)372 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedstdio, Streamable HTTP
Tools it declares (differs)Not published6
Environment variables it asks for (differs)Not published3, secrets among them: 2
Hooks it runs (differs)1Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)MITApache-2.0
Repository (differs)github.com/orcaqubits/agentic-commerce-claude-pluginsgithub.com/browserbase/mcp-server-browserbase
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

commerce-readiness

In its own words, on Community GitHub marketplaces:

Agentic Commerce Readiness Audit — executable stdlib-Python probes that score a live site on agent access, protocol discovery (UCP/ACP/A2A), catalog structured data (Product/ProductGroup JSON-LD), checkout transactability (ACP/UCP REST, MCP tools/list, NLWeb /ask), payment surfaces (handlers, delegate_payment, AP2, HTTP 402), and trust (OAuth, signing keys, TLS), mapping every gap to the marketplace skill that closes it

io.github.browserbase/mcp-server-browserbase

In its own words, on Official MCP Registry:

MCP server for AI web browser automation using Browserbase and Stagehand

How to run each

commerce-readiness As a Claude Code plugin

Claude Code
/plugin marketplace add orcaqubits/agentic-commerce-claude-plugins
/plugin install commerce-readiness@agentic-commerce

io.github.browserbase/mcp-server-browserbase As a local MCP server: npm package

Claude Code
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-browserbase

Requires: BROWSERBASE_API_KEY (secret), BROWSERBASE_PROJECT_ID, GEMINI_API_KEY (secret)

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

Tools each declares

The marketplaces of commerce-readiness publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of commerce-readiness publish no settings it asks for, so we do not compare settings.

What it can do: commerce-readiness · What it can do: io.github.browserbase/mcp-server-browserbase · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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.

Where the data comes from: how the catalog is built