Firecrawl vs SearXNG HTTP MCP
Firecrawl is an MCP server published by firecrawl. Marketplaces we read that list it: 1 (Docker MCP Catalog). SearXNG HTTP MCP is an MCP server published by whw23. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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
| Marketplace |  Firecrawl |  SearXNG HTTP MCP |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:28e677a10704 Forks (GitHub): 915 Pulls (Docker Hub): 141 762 Stars (Docker Hub): 20 Stars (GitHub): 7 666 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2026.55.0 Forks (GitHub): 1 Stars (GitHub): 12 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
| Fact | Firecrawl | SearXNG HTTP MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 7 666 (better) | 12 (worse) |
| Pulls (Docker Hub) (differs) | 141 762 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 915 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/firecrawl) | On your machine (ghcr.io/whw23/searxng-http-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 26 | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 1 | 1, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 3 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/mendableai/firecrawl-mcp-server | github.com/whw23/searxng_http_mcp |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-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
Firecrawl
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.
SearXNG HTTP MCP
Self-contained SearXNG metasearch MCP server. One Docker image, 200+ engines, privacy-first.
How to run each
Firecrawl As a local MCP server: Docker image
claude mcp add --env "FIRECRAWL_API_KEY=<YOUR_FIRECRAWL_API_KEY>" --transport stdio firecrawl -- docker run -i --rm -e FIRECRAWL_API_KEY mcp/firecrawlRequires: FIRECRAWL_API_KEY (secret)
SearXNG HTTP MCP As a local MCP server: Docker image
claude mcp add --env "API_KEY=<YOUR_API_KEY>" --transport stdio searxng-http-mcp -- docker run -i --rm -e API_KEY run --memory 512m --cpus 1 ghcr.io/whw23/searxng-http-mcp --stdioRequires: 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 SearXNG HTTP MCP publish no list of tools, so we do not compare tools.
Settings each asks for
Only Firecrawl asks for
FIRECRAWL_API_KEY (secret)FIRECRAWL_API_URLFIRECRAWL_CREDIT_CRITICAL_THRESHOLDFIRECRAWL_CREDIT_WARNING_THRESHOLDFIRECRAWL_RETRY_BACKOFF_FACTORFIRECRAWL_RETRY_INITIAL_DELAYFIRECRAWL_RETRY_MAX_ATTEMPTSFIRECRAWL_RETRY_MAX_DELAY
Only SearXNG HTTP MCP asks for
API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Firecrawl · What it can do: SearXNG HTTP 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. 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.