Ext Ops Panel
Open dashboard
Comparison

Firecrawl vs Build My Digital website scanner

Firecrawl is an MCP server published by firecrawl. Marketplaces we read that list it: 1 (Docker MCP Catalog). Build My Digital website scanner is an MCP server published by buildmydigital.co.uk. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
MarketplaceFirecrawlBuild My Digital website scanner
Docker MCP Catalog Listed
Version: sha256:28e677a10704
Forks (GitHub): 915
Pulls (Docker Hub): 141 047
Stars (Docker Hub): 20
Stars (GitHub): 7 666
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.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

Firecrawl vs Build My Digital website scanner
FactFirecrawlBuild My Digital website scanner
Marketplaces that list it11
Stars (GitHub) (differs)7 666No figure on GitHub
Pulls (Docker Hub) (differs)141 047No figure on Docker Hub
Forks (GitHub) (differs)915No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/firecrawl)Remote server (buildmydigital.co.uk/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)26Not published
Environment variables it asks for (differs)8, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/mendableai/firecrawl-mcp-serverNot stated
Changes in the last 7 days (differs)10
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days 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

Firecrawl

In its own words, on Docker MCP Catalog:

Official Firecrawl MCP server, the context API for AI agents: search, scrape, and interact with the web, plus parse, crawl, map, Agent and Monitor, from any MCP client.

Build My Digital website scanner

In its own words, on Official MCP Registry:

Scans any public website for SEO, AI search, trust, conversion and speed, and lists our prices.

How to run each

Firecrawl As a local MCP server: Docker image

Claude Code
claude mcp add --env "FIRECRAWL_API_KEY=<YOUR_FIRECRAWL_API_KEY>" --transport stdio firecrawl -- docker run -i --rm -e FIRECRAWL_API_KEY mcp/firecrawl

Requires: FIRECRAWL_API_KEY (secret)

Build My Digital website scanner As a remote MCP server

Claude Code
claude mcp add --transport http scanner https://buildmydigital.co.uk/mcp/

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

Only Build My Digital website scanner has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Build My Digital website scanner publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Build My Digital website scanner publish no settings it asks for, so we do not compare settings.

What it can do: Firecrawl · What it can do: Build My Digital website scanner · 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