Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Firecrawl MCP Server

NPM · FIRECRAWL-MCP · SCANNED AUG 3

MCP server for Firecrawl — search, scrape, and interact with the web.

Available components

+9 this week 28 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security79
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects axios 1.16.1, reached via @mendable/firecrawl-js > axios. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (183 of 185), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · firecrawl-mcp

# add to Claude Code
claude mcp add firecrawl-firecrawl-mcp-server -- npx -y firecrawl-mcp
# add to Codex CLI
codex mcp add firecrawl-firecrawl-mcp-server -- npx -y firecrawl-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "firecrawl-firecrawl-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "firecrawl-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add firecrawl-firecrawl-mcp-server --command npx --arg -y --arg firecrawl-mcp
# ~/.hermes/config.yaml
mcp_servers:
  firecrawl-firecrawl-mcp-server:
    command: "npx"
    args: ["-y", "firecrawl-mcp"]
// mcp.json
{
  "mcpServers": {
    "firecrawl-firecrawl-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "firecrawl-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +28
    • CVE-2026-67320 affects this package: high security
    • CVE-2026-67314 affects this package: high security
    • CVE-2026-67321 affects this package: high security
    • CVE-2026-67317 affects this package: high security
    • CVE-2026-67319 affects this package: high security
    • CVE-2026-67313 affects this package: high security
    • CVE-2026-67316 affects this package: high security
    • CVE-2026-67312 affects this package: high security
    • CVE-2026-67315 affects this package: high security
    • CVE-2026-67318 affects this package: high security
    • Known CVEs: unverified → fail security
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • License: unverified → pass functional
    • Licence: MIT functional
  • 1 Aug 26 −9
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 +9
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Maintenance: unverified → pass functional
    • License: unverified → pass functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Licence: MIT functional
  • 29 Jul 26 −30
    • Malware scan: pass → unverified security
    • Tool coverage: 100 → unverified functional
    • Package version: 3.22.4 → 3.23.0 functional
  • 28 Jul 26 +11
    • Dependency health: partial → unverified functional
    • Tool coverage: unverified → 100 functional
    • First check of Schema quality: unverified functional
    • First check of Tool coverage: 9 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fail functional
  • 27 Jul 26 19

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Vulnerabilities 10 findings
ID CVE Severity Vector Fix available
GHSA-42h9-826w-cgv3 CVE-2026-67313 medium yes
GHSA-7q8q-rj6j-mhjq CVE-2026-67319 medium yes
GHSA-f4gw-2p7v-4548 CVE-2026-67315 medium yes
GHSA-gcfj-64vw-6mp9 CVE-2026-67320 high yes
GHSA-hcpx-6fm6-wx23 CVE-2026-67321 medium yes
GHSA-jqh4-m9w3-8hp9 CVE-2026-67317 medium yes
GHSA-mmx7-hfxf-jppx CVE-2026-67316 medium yes
GHSA-mwf2-3pr3-8698 CVE-2026-67318 medium yes
GHSA-pmv8-rq9r-6j72 CVE-2026-67312 medium yes
GHSA-xj6q-8x83-jv6g CVE-2026-67314 medium yes
Dependencies 183 packages

183 packages in the resolved dependency tree · 183 deprecated · 59 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.