Firecrawl MCP Server vs YaCy peer-to-peer search
Firecrawl MCP Server is an MCP server published by firecrawl. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). YaCy peer-to-peer search is an MCP server published by pad01g. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 MCP Server |  YaCy peer-to-peer search |
|---|---|---|
| Official MCP Registry | Listed Version: 3.36.0 Downloads/month (npm): 625 831 Downloads/week (npm): 102 401 Forks (GitHub): 920 Stars (GitHub): 7 705 Not marked · First seen |
Listed Version: 1.0.0 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
| Fact | Firecrawl MCP Server | YaCy peer-to-peer search |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 7 705 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 920 (better) | 0 (worse) |
| Last release (differs) | 2026-10-27 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (ghcr.io/pad01g/yacy-search-mcp:1.0.0) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 5, secrets among them: 1 |
| Parts of the bundle (differs) | 18 | Not a bundle |
| Licence (differs) | ISC | Not stated |
| Repository (differs) | github.com/firecrawl/firecrawl-mcp-server | github.com/pad01g/yacy_search_server |
| Changes in the last 7 days (differs) | 5 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago | no remote endpoint we check |
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 MCP Server
Firecrawl, the context API for AI agents: search, scrape, interact with the web, plus paper search.
YaCy peer-to-peer search
Web search, crawling and ranking evaluation on your own YaCy peer: no API key, no central service.
How to run each
Firecrawl MCP Server As a remote MCP server
claude mcp add --transport http firecrawl-mcp-server https://mcp.firecrawl.dev/v2/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: FIRECRAWL_API_KEY (secret), Authorization header
YaCy peer-to-peer search As a local MCP server: Docker image
claude mcp add --env "YACY_ADMIN_PASSWORD=<YOUR_YACY_ADMIN_PASSWORD>" --env "YACY_URL=<YOUR_YACY_URL>" --transport stdio yacy-search -- docker run -i --rm -e YACY_ADMIN_PASSWORD -e YACY_URL ghcr.io/pad01g/yacy-search-mcp:1.0.0Requires: YACY_ADMIN_PASSWORD (secret), YACY_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Firecrawl MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Firecrawl MCP Server asks for
FIRECRAWL_API_KEY (secret)
Only YaCy peer-to-peer search asks for
YACY_ADMIN_PASSWORD (secret)YACY_ADMIN_USERYACY_ALLOW_TRUST_SETTINGSYACY_CRAWL_ALLOW_PRIVATEYACY_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Firecrawl MCP Server · What it can do: YaCy peer-to-peer search · Compare two other plugins
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.