firecrawl-mcp@3.40.0
VERIFIEDPublisher claims: "Firecrawl MCP server, the context API for AI agents: search, scrape, parse, crawl, map, and interact with the web, run Agent and Monitor jobs, and search scientific papers (PubMed, bioRxiv, medRxiv, arXiv). Works with Firecrawl cloud or a self-hosted inst" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Server started and answered tools/list.- Tested
- MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
- Not tested
- what the tools do when called with real credentials
Before you give it your token
- It will ask for
FIRECRAWL_API_KEYFIRECRAWL_MCP_SEARCH_OAUTH_ONLYFIRECRAWL_OAUTH_INTROSPECT_CACHE_TTL_MSFIRECRAWL_OAUTH_INTROSPECT_SECRETFIRECRAWL_OAUTH_ISSUERFIRECRAWL_OAUTH_TOKENMCP_DELEGATED_CREDENTIAL_SECRETMCP_OAUTH_ACCEPT_LEGACY_V2_MCP_AUDConfiguration, not credentials: CLOUD_SERVICE, FASTMCP_ENDPOINT, FASTMCP_HOST, FASTMCP_PORT, FASTMCP_STATELESS, FIRECRAWL_API_URL, FIRECRAWL_INTEGRATION, FIRECRAWL_MCP_ALLOWED_HOSTS, FIRECRAWL_MCP_RESOURCE_URL, FIRECRAWL_MCP_SEARCH_ENABLED, FIRECRAWL_MCP_SEARCH_ENDPOINT, FIRECRAWL_MCP_SEARCH_PORT, FIRECRAWL_MCP_SEARCH_RESOURCE_URL, HTTP_STREAMABLE_SERVER, JOB_PATH, SSE_LOCAL- Where it talks to
- firecrawl.dev (its own)
- What the honeypot saw
- no credential files read · no network
- What we could not test
- what the tools do when called with real credentials
Connect it with a scoped credential, under the guard. It asks for FIRECRAWL_API_KEY, FIRECRAWL_MCP_SEARCH_OAUTH_ONLY, FIRECRAWL_OAUTH_INTROSPECT_CACHE_TTL_MS, FIRECRAWL_OAUTH_INTROSPECT_SECRET, FIRECRAWL_OAUTH_ISSUER, FIRECRAWL_OAUTH_TOKEN, MCP_DELEGATED_CREDENTIAL_SECRET, MCP_OAUTH_ACCEPT_LEGACY_V2_MCP_AUD and talks to firecrawl.dev. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-12 and scored it 91/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 32 s · 2 scenarios · 0 deviationsStatic findings
…LARED_ORIGIN_HEADER, type DeferredResult, type ExtraToolsContext, type FirecrawlMcpServer, type FirecrawlMcpServerHooks, type FirecrawlMcpServerOptions, type FirecrawlMcpServerStartArgs, type HttpApp, type InstructionDefaults, keylessToolN…Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.…de in data.alexandria[0].data. Reuse workspaceId with command to filter response.json using jq, grep, head or sed; combine related projections and return small slices, not the full file. saveOutput:true retains large command output in virt…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…de in data.alexandria[0].data. Reuse workspaceId with command to filter response.json using jq, grep, head or sed; combine related projections and return small slices, not the full file. saveOutput:true retains large command output in virt…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for firecrawl-mcp@3.40.0 as of 2d ago. This is the package itself, not its dependencies.