Hyperbrowser vs Webcake Landing
Hyperbrowser is an MCP server published by hyperbrowserai. Marketplaces we read that list it: 1 (Docker MCP Catalog). Webcake Landing is an MCP server published by vuluu2k. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  Hyperbrowser |  Webcake Landing |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:11ed80138c33 Forks (GitHub): 75 Pulls (Docker Hub): 41 187 Stars (Docker Hub): 3 Stars (GitHub): 789 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.6.0 Downloads/month (npm): 1 512 Downloads/week (npm): 745 Forks (GitHub): 0 Stars (GitHub): 6 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 | Hyperbrowser | Webcake Landing |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 789 (better) | 6 (worse) |
| Pulls (Docker Hub) (differs) | 41 187 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 75 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (mcp/hyperbrowser) | Remote server (mcp.toolvn.io.vn/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 5, secrets among them: 2 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hyperbrowserai/mcp | github.com/vuluu2k/webcake-landing-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 12 h ago, requires a key |
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
Hyperbrowser
A MCP server implementation for hyperbrowser.
Webcake Landing
Build, validate, and persist Webcake landing-page source JSON: element schemas plus AI usage hints.
How to run each
Hyperbrowser As a local MCP server: Docker image
claude mcp add --env "HYPERBROWSER_API_KEY=<YOUR_HYPERBROWSER_API_KEY>" --transport stdio hyperbrowser -- docker run -i --rm -e HYPERBROWSER_API_KEY mcp/hyperbrowserRequires: HYPERBROWSER_API_KEY (secret)
Webcake Landing As a remote MCP server
claude mcp add --transport http webcake-landing-mcp https://mcp.toolvn.io.vn/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: PEXELS_API_KEY (secret), WEBCAKE_JWT (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Webcake Landing has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Webcake Landing publish no list of tools, so we do not compare tools.
Settings each asks for
Only Hyperbrowser asks for
HYPERBROWSER_API_KEY (secret)
Only Webcake Landing asks for
PEXELS_API_KEY (secret)WEBCAKE_API_BASEWEBCAKE_ENVWEBCAKE_JWT (secret)WEBCAKE_ORG_ID
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Hyperbrowser · What it can do: Webcake Landing · 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.