Ext Ops Panel
Open dashboard
Comparison

Hyperbrowser vs Site no Ar

Hyperbrowser is an MCP server published by hyperbrowserai. Marketplaces we read that list it: 1 (Docker MCP Catalog). Site no Ar is an MCP server published by sitenoar.dev. 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

Where each is published
MarketplaceHyperbrowserSite no Ar
Docker MCP Catalog Listed
Version: sha256:11ed80138c33
Forks (GitHub): 75
Pulls (Docker Hub): 41 410
Stars (Docker Hub): 3
Stars (GitHub): 789
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

Hyperbrowser vs Site no Ar
FactHyperbrowserSite no Ar
Marketplaces that list it11
Stars (GitHub) (differs)789No figure on GitHub
Pulls (Docker Hub) (differs)41 410No figure on Docker Hub
Forks (GitHub) (differs)75No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/hyperbrowser)Remote server (mcp.sitenoar.dev)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)10Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/hyperbrowserai/mcpNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-16
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

In its own words, on Docker MCP Catalog:

A MCP server implementation for hyperbrowser.

Site no Ar

In its own words, on Official MCP Registry:

Crie, edite e publique sites e apps web pelo seu agente de IA, com domínio próprio.

How to run each

Hyperbrowser As a local MCP server: Docker image

Claude Code
claude mcp add --env "HYPERBROWSER_API_KEY=<YOUR_HYPERBROWSER_API_KEY>" --transport stdio hyperbrowser -- docker run -i --rm -e HYPERBROWSER_API_KEY mcp/hyperbrowser

Requires: HYPERBROWSER_API_KEY (secret)

Site no Ar As a remote MCP server

Claude Code
claude mcp add --transport http sitenoar https://mcp.sitenoar.dev

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

Tools each declares

The marketplaces of Site no Ar publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Site no Ar publish no settings it asks for, so we do not compare settings.

What it can do: Hyperbrowser · What it can do: Site no Ar · 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.

Where the data comes from: how the catalog is built