firecrawl@3.39.0
VERIFIED· install onlyPublisher claims: "Search, scrape, and interact with the web for AI agents. Turn any URL into clean Markdown or structured JSON, search the live web and specialized indexes, parse documents, crawl and map sites, and watch pages for changes." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
API_KEYFIRECRAWL_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)Also client.example, status.example, peopledatalabs.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names client.example, status.example, peopledatalabs.com as well as its own vendor. The guard injects API_KEY, 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 only into requests to firecrawl.dev (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 3.36.0
vet-skills diff firecrawl 3.36.0 3.39.0This version reaches for something 3.36.0 did not: 4 new hosts (client.example, firecrawl.dev, peopledatalabs.com, status.example) · 9 new credential variables (API_KEY, FIRECRAWL_API_KEY, FIRECRAWL_MCP_SEARCH_OAUTH_ONLY, FIRECRAWL_OAUTH_INTROSPECT_CACHE_TTL_MS, …). Compared from the two recorded runs, not from source.
- New hosts
- client.example, firecrawl.dev, peopledatalabs.com, status.example
- New credential variables
- API_KEY, 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
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-11 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
...env,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if (input.endsWith('.json')) return JSON.parse(readFileSync(input, 'utf8'));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....env,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const child = spawnServer({ ...BASE_ENV, PORT: String(port), ...env });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env: { ...process.env, ...BASE_ENV, ...env },Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose....env,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.run: echo "version=$(node -p "require('./package.json').version")" >> "$GITHUB_OUTPUT"Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(formatDiff(differences, inputs));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.run: echo "version=$(node -p "require('./package.json').version")" >> "$GITHUB_OUTPUT"Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.const { client, init } = await startStdio(t, { ...BASE_ENV, ...env });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose....env,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.