Skip to content
mcp/skillhub

Chrome Web Store MCP Server

by pipeworx-ioio.github.pipeworx-io/chrome-web-storev0.1.0

Chrome Web Store — public extension listing data: a single extension by id, free-text search, and…

0remoteofficial registry

context tax

not measurable

security

97/100

cold start

hosted

freshness

Active4d ago

Our reading of Chrome Web Store, from the data

Chrome Web Store is a browser automation MCP server from pipeworx-io, listed in the official MCP Registry.

We haven't measured its tool list yet, so its token cost is unknown.

Maintenance is active: the last public signal was 4 days ago (2026-10-15). For comparison, 67% of browser automation servers are active or maintained.

With 0 GitHub stars it ranks #560 of 1,199 browser automation servers we index.

It runs as a hosted endpoint, so there is nothing to install.

Install Chrome Web Store MCP server

Install in Claude Code

claude mcp add --transport http chrome-web-store https://gateway.pipeworx.io/chrome-web-store/mcp

Remote endpoints

  • streamable-httphttps://gateway.pipeworx.io/chrome-web-store/mcp

Security signals

97/100 — no known issues found as of 2026-10-19, from the checks below. This is not a guarantee of safety; review what a server can do before connecting it.

Deductions

  • No security policy (SECURITY.md)-3

Checks

  • ✓Repository hygiene (archived, activity, license, security policy)
  • ○Package metadata (install scripts, provenance) — pending
  • ○Tool descriptions (prompt-injection and hidden-text heuristics) — pending
  • ○Source scan (secrets, CVEs, risky code) by vectra-guard — pending

Scan it yourself before installing with vectra-guard, the open-source agent security CLI. Scoring rules

Freshness

Active — last maintenance signal 4d ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    2026-10-15 · 4d ago · GitHub

  2. Latest release

    no data · GitHub

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-10-15 · 4d ago · official registry · v0.1.0

How it compares in Browser Automation

Against the most-starred browser automation servers we index. Token cost is per model turn, measured from each server's live tool list.

ServerStarsToolsTokens / turnFreshnessRuns
Chrome Web Store (this)0—not measuredActivehosted
Browser Use118,444—not measuredActivelocal
Scrapling88,517—not measuredActivelocal
Browser39,318—not measuredActivelocal + hosted
Playwright38,349—not measuredActivelocal
Browser36,690—not measuredActive—
All browser automation MCP servers

FAQ

›How do I install the Chrome Web Store MCP server in Claude Code?

Run: claude mcp add --transport http chrome-web-store https://gateway.pipeworx.io/chrome-web-store/mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Chrome Web Store require an API key?

No required environment variables are declared in its published metadata.

›Can I use Chrome Web Store as a remote (hosted) MCP server?

Yes. It is a hosted MCP server; connect to its URL with any client that supports remote MCP.

›Is Chrome Web Store in the official MCP registry?

Yes, as io.github.pipeworx-io/chrome-web-store.

Sources and method

Official MCP Registry entry
updated 2026-10-15
GitHub repository
fetched 2026-10-19
Last checked against all sources
2026-10-19

The description, packages and links come from the maintainer's own published metadata. Token cost, security signals, freshness and the reading above are MCPSkillHub's own measurements; see the methodology. Spot an error? Request a correction or claim the listing.

Alternatives to Chrome Web Store

Other browser automation MCP servers.

View all