Oya Browser vs io.github.fastslack/e2e-runner
Oya Browser is an MCP server published by OyadotAI. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). io.github.fastslack/e2e-runner is an MCP server published by fastslack. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-18. 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 |  Oya Browser |  io.github.fastslack/e2e-runner |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.198 Forks (GitHub): 278 Stars (GitHub): 352 Not marked · First seen |
Listed Version: 1.3.0 Downloads/month (npm): 179 Downloads/week (npm): 48 Forks (GitHub): 1 Stars (GitHub): 7 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.5.1 Forks (GitHub): 1 Stars (GitHub): 7 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 | Oya Browser | io.github.fastslack/e2e-runner |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 352 (better) | 7 (worse) |
| Forks (GitHub) (differs) | 278 (better) | 1 (worse) |
| Last release (differs) | 2026-10-18 | Not published |
| Where it runs (differs) | Remote server (oyabrowser.com/mcp/pool) | On your machine (@matware/e2e-runner) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | 9 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/oyadotai/oya-browser | github.com/fastslack/mtw-e2e-runner |
| Changes in the last 7 days (differs) | 20 or more | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 14 h ago, requires a key | no remote endpoint we check |
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
Oya Browser
Real Chrome for agents: start a browser, read pages as numbered markdown, click, type, hand off.
io.github.fastslack/e2e-runner
JSON-driven E2E test runner with parallel Chrome pool execution and 16 MCP tools.
How to run each
Oya Browser As a remote MCP server
claude mcp add --transport http oya-browser https://oyabrowser.com/mcp/pool --header "Authorization: Bearer <YOUR_API_KEY>"Requires: Authorization header
io.github.fastslack/e2e-runner As a local MCP server: npm package
claude mcp add --transport stdio e2e-runner -- npx -y @matware/e2e-runnerCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Oya Browser has a remote endpoint we check. How we check endpoints
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: Oya Browser · What it can do: io.github.fastslack/e2e-runner · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.