Ext Ops Panel
Open dashboard
Comparison

ed3d-playwright vs Jet Browser Verifier

ed3d-playwright is a plugin bundle for AI coding tools published by Ed. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Jet Browser Verifier is an MCP server published by masakaai. 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
Marketplaceed3d-playwrightJet Browser Verifier
Community marketplace ed3dai/ed3d-plugins Listed
Version: 1.1.0
Forks (GitHub): 34
Stars (GitHub): 253
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.9.0
Forks (GitHub): 2
Stars (GitHub): 2
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

ed3d-playwright vs Jet Browser Verifier
Facted3d-playwrightJet Browser Verifier
Marketplaces that list it11
Stars (GitHub) (differs)253 (better)2 (worse)
Forks (GitHub) (differs)34 (better)2 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (@executeautomation/playwright-mcp-server)On your machine (ghcr.io/masakaai/jet-browser-mcp:0.9.0)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)4Not a bundle
Licence (differs)UNLICENSEDNot stated
Repository (differs)github.com/ed3dai/ed3d-pluginsgithub.com/masakaai/jet-browser
Changes in the last 7 days (differs)20
First seen (differs)2026-10-162026-10-11

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

ed3d-playwright

In its own words, on Community GitHub marketplaces:

Playwright automation toolkit with MCP integration, specialized agent for browser control, and best practice skills

Jet Browser Verifier

In its own words, on Official MCP Registry:

Verify an isolated WPE WebKit runtime with native-input, DOM, PNG, and cleanup evidence.

How to run each

ed3d-playwright As a Claude Code plugin

Claude Code
/plugin marketplace add ed3dai/ed3d-plugins
/plugin install ed3d-playwright@ed3d-plugins

Jet Browser Verifier As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio jet-browser -- docker run -i --rm --network none --mount type=bind,src=/var/run/docker.sock,dst=/var/run/docker.sock ghcr.io/masakaai/jet-browser-mcp:0.9.0

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

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: ed3d-playwright · What it can do: Jet Browser Verifier · 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. 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