Ext Ops Panel
Open dashboard
Comparison

Hyperbrowser vs sh.clearfront/clearfront

Hyperbrowser is an MCP server published by hyperbrowserai. Marketplaces we read that list it: 1 (Docker MCP Catalog). sh.clearfront/clearfront is an MCP server published by clearfront.sh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceHyperbrowsersh.clearfront/clearfront
Docker MCP Catalog Listed
Version: sha256:11ed80138c33
Forks (GitHub): 75
Pulls (Docker Hub): 41 144
Stars (Docker Hub): 3
Stars (GitHub): 789
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.7.3
Forks (GitHub): 2
Stars (GitHub): 9
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 sh.clearfront/clearfront
FactHyperbrowsersh.clearfront/clearfront
Marketplaces that list it11
Stars (GitHub) (differs)789 (better)9 (worse)
Pulls (Docker Hub) (differs)41 144No figure on Docker Hub
Forks (GitHub) (differs)75 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/hyperbrowser)On your machine (clearfront)
Transportstdiostdio
Tools it declares (differs)10Not published
Environment variables it asks for (differs)1, secrets among them: 15, secrets among them: 5
Licence (differs)MITNot stated
Repository (differs)github.com/hyperbrowserai/mcpgithub.com/scottmartinanderson/clearfront
Changes in the last 7 days00
First seen2026-10-112026-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

Hyperbrowser

In its own words, on Docker MCP Catalog:

A MCP server implementation for hyperbrowser.

sh.clearfront/clearfront

In its own words, on Official MCP Registry:

OSINT sweep of a digital footprint: breaches, accounts, data brokers, domains and IPs

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)

sh.clearfront/clearfront As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "HIBP_API_KEY=<YOUR_HIBP_API_KEY>" --env "IPINFO_TOKEN=<YOUR_IPINFO_TOKEN>" --env "SHODAN_API_KEY=<YOUR_SHODAN_API_KEY>" --env "VIRUSTOTAL_API_KEY=<YOUR_VIRUSTOTAL_API_KEY>" --transport stdio clearfront -- uvx clearfront

Requires: ANTHROPIC_API_KEY (secret), HIBP_API_KEY (secret), IPINFO_TOKEN (secret), SHODAN_API_KEY (secret), VIRUSTOTAL_API_KEY (secret)

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

Tools each declares

The marketplaces of sh.clearfront/clearfront publish no list of tools, so we do not compare tools.

Settings each asks for

Only Hyperbrowser asks for

  • HYPERBROWSER_API_KEY (secret)

Only sh.clearfront/clearfront asks for

  • ANTHROPIC_API_KEY (secret)
  • HIBP_API_KEY (secret)
  • IPINFO_TOKEN (secret)
  • SHODAN_API_KEY (secret)
  • VIRUSTOTAL_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Hyperbrowser · What it can do: sh.clearfront/clearfront · 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