Firecrawl MCP Server vs Decoy
Firecrawl MCP Server is an MCP server published by firecrawl. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). Decoy is an MCP server published by decoys.me. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 3.38.0 Downloads/month (npm): 517 013 Downloads/week (npm): 158 613 Forks (GitHub): 927 Stars (GitHub): 7 779 Not marked · First seen |
Listed Version: 1.4.0 Downloads/month (npm): 1 257 Downloads/week (npm): 561 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:3b22a74af198 Forks (GitHub): 927 Pulls (Docker Hub): 149 069 Stars (Docker Hub): 20 Stars (GitHub): 7 779 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 1.4.0 Downloads/month (npm): 1 257 Downloads/week (npm): 561 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
| Fact | Firecrawl MCP Server | Decoy |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 2 (worse) |
| Stars (GitHub) (differs) | 7 779 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 149 069 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 927 (better) | 0 (worse) |
| Last release (differs) | 2026-11-06 (better) | 2026-11-03 (worse) |
| Where it runs (differs) | Remote server or your machine | On your machine (decoy-mcp-server) |
| Transport (differs) | Streamable HTTP, stdio | Streamable HTTP |
| Tools it declares (differs) | 28 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 1, secrets among them: 0 |
| Parts of the bundle (differs) | 18 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/firecrawl/firecrawl-mcp-server | github.com/decoy-identity/decoy-mcp-server |
| Changes in the last 7 days (differs) | 9 | 3 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
| Endpoint at the last check (differs) | Responded 24 h 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.
Decoy
What your agents should know about you, shared by every agent. End-to-end encrypted.
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
Decoy
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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
The marketplaces of Decoy publish no list of tools, so we do not compare tools.
Settings each asks for
Only Firecrawl MCP Server asks for
FIRECRAWL_API_KEY (secret)FIRECRAWL_API_URL
Only Decoy asks for
PORT
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: Decoy · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.