Ext Ops Panel
Open dashboard
Comparison

Hyperbrowser vs org.sylin/ghostlight

Hyperbrowser is an MCP server published by hyperbrowserai. Marketplaces we read that list it: 1 (Docker MCP Catalog). org.sylin/ghostlight is an MCP server published by sylin.org. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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

Where each is published
MarketplaceHyperbrowserorg.sylin/ghostlight
Docker MCP Catalog Listed
Version: sha256:11ed80138c33
Forks (GitHub): 75
Pulls (Docker Hub): 41 184
Stars (Docker Hub): 3
Stars (GitHub): 789
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.3.14
Downloads/month (npm): 2 350
Downloads/week (npm): 143
Forks (GitHub): 0
Stars (GitHub): 1
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 org.sylin/ghostlight
FactHyperbrowserorg.sylin/ghostlight
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)789 (better)1 (worse)
Pulls (Docker Hub) (differs)41 184No figure on Docker Hub
Forks (GitHub) (differs)75 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/hyperbrowser)On your machine (ghostlight)
Transportstdiostdio
Tools it declares (differs)10Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle2
Licence (differs)MITNot stated
Repository (differs)github.com/hyperbrowserai/mcpgithub.com/sylin-org/ghostlight
Changes in the last 7 days (differs)02
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.

org.sylin/ghostlight

In its own words, on Official MCP Registry:

Visible local browser automation in signed-in Chromium, with optional policy and audit.

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)

org.sylin/ghostlight As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio ghostlight -- npx -y ghostlight

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

Tools each declares

The marketplaces of org.sylin/ghostlight publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of org.sylin/ghostlight publish no settings it asks for, so we do not compare settings.

What it can do: Hyperbrowser · What it can do: org.sylin/ghostlight · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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