ExecuteAutomation Playwright vs 6Frame Verify
ExecuteAutomation Playwright is an MCP server published by executeautomation. Marketplaces we read that list it: 1 (Docker MCP Catalog). 6Frame Verify is an MCP server published by bret1976. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  ExecuteAutomation Playwright |  6Frame Verify |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:5ffcdfc3d929 Forks (GitHub): 539 Pulls (Docker Hub): 23 139 Stars (Docker Hub): 1 Stars (GitHub): 5 668 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.3.0 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 | ExecuteAutomation Playwright | 6Frame Verify |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 5 668 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 23 139 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 539 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | On your machine (mcp/mcp-playwright) | Remote server (siteverify.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 32 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/executeautomation/mcp-playwright | github.com/bret1976/6frame-verify |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (5 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
ExecuteAutomation Playwright
Playwright Model Context Protocol Server - Tool to automate Browsers and APIs in Claude Desktop, Cline, Cursor IDE and More 🔌.
6Frame Verify
Pre-launch website QA in 60s via real Chromium. $3/check; agents can pay in USDC (x402).
How to run each
ExecuteAutomation Playwright As a local MCP server: Docker image
claude mcp add --transport stdio playwright-mcp-server -- docker run -i --rm mcp/mcp-playwright6Frame Verify As a remote MCP server
claude mcp add --transport http 6frame-verify https://siteverify.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only 6Frame Verify has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of 6Frame Verify publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: ExecuteAutomation Playwright · What it can do: 6Frame Verify · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.