Ext Ops Panel
Open dashboard
Comparison

Hyperbrowser vs Follow On Tours – bespoke sports travel

Hyperbrowser is an MCP server published by hyperbrowserai. Marketplaces we read that list it: 1 (Docker MCP Catalog). Follow On Tours – bespoke sports travel is an MCP server published by followontours.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
MarketplaceHyperbrowserFollow On Tours – bespoke sports travel
Docker MCP Catalog Listed
Version: sha256:11ed80138c33
Forks (GitHub): 75
Pulls (Docker Hub): 41 504
Stars (Docker Hub): 3
Stars (GitHub): 791
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
Forks (GitHub): 0
Stars (GitHub): 0
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 Follow On Tours – bespoke sports travel
FactHyperbrowserFollow On Tours – bespoke sports travel
Marketplaces that list it11
Stars (GitHub) (differs)791 (better)0 (worse)
Pulls (Docker Hub) (differs)41 504No figure on Docker Hub
Forks (GitHub) (differs)75 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (mcp/hyperbrowser)Remote server (www.followontours.com/api/mcp)
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/mcpgithub.com/followontours/mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 46 h ago

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.

Follow On Tours – bespoke sports travel

In its own words, on Official MCP Registry:

Bespoke sports travel: cricket, golf, rugby, polo and playing tours. Tour operator, ABTOT 5718.

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)

Follow On Tours – bespoke sports travel As a remote MCP server

Claude Code
claude mcp add --transport http cricket-travel https://www.followontours.com/api/mcp

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

Only Follow On Tours – bespoke sports travel has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Follow On Tours – bespoke sports travel publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Follow On Tours – bespoke sports travel publish no settings it asks for, so we do not compare settings.

What it can do: Hyperbrowser · What it can do: Follow On Tours – bespoke sports travel · 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