Ext Ops Panel
Open dashboard
Comparison

Hyperbrowser vs io.github.Udhay-Adithya/neopat-mcp

Hyperbrowser is an MCP server published by hyperbrowserai. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.Udhay-Adithya/neopat-mcp is an MCP server published by Udhay-Adithya. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
MarketplaceHyperbrowserio.github.Udhay-Adithya/neopat-mcp
Docker MCP Catalog Listed
Version: sha256:11ed80138c33
Forks (GitHub): 75
Pulls (Docker Hub): 41 195
Stars (Docker Hub): 3
Stars (GitHub): 789
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.3
Downloads/month (PyPI): 0
Downloads/week (PyPI): 247
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 io.github.Udhay-Adithya/neopat-mcp
FactHyperbrowserio.github.Udhay-Adithya/neopat-mcp
Marketplaces that list it11
Stars (GitHub) (differs)789 (better)1 (worse)
Pulls (Docker Hub) (differs)41 195No figure on Docker Hub
Forks (GitHub) (differs)75 (better)0 (worse)
Last release (differs)Not published2026-10-14
Where it runs (differs)On your machine (mcp/hyperbrowser)On your machine (neopat-mcp)
Transportstdiostdio
Tools it declares (differs)10Not published
Environment variables it asks for (differs)1, secrets among them: 13, secrets among them: 2
Licence (differs)MITNot stated
Repository (differs)github.com/hyperbrowserai/mcpgithub.com/udhay-adithya/neopat-mcp
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-13

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.

io.github.Udhay-Adithya/neopat-mcp

In its own words, on Official MCP Registry:

Browse campus placement drives and apply, with confirmation.

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)

io.github.Udhay-Adithya/neopat-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --env "NEOPAT_PASSWORD=<YOUR_NEOPAT_PASSWORD>" --env "NEOPAT_TOKEN=<YOUR_NEOPAT_TOKEN>" --transport stdio neopat-mcp -- uvx neopat-mcp

Requires: NEOPAT_PASSWORD (secret), NEOPAT_TOKEN (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 io.github.Udhay-Adithya/neopat-mcp publish no list of tools, so we do not compare tools.

Settings each asks for

Only Hyperbrowser asks for

  • HYPERBROWSER_API_KEY (secret)

Only io.github.Udhay-Adithya/neopat-mcp asks for

  • NEOPAT_EMAIL
  • NEOPAT_PASSWORD (secret)
  • NEOPAT_TOKEN (secret)

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

What it can do: Hyperbrowser · What it can do: io.github.Udhay-Adithya/neopat-mcp · 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