updated 2026-10-11 04:08 UTC

Firecrawl MCP Server

Repository Website by firecrawl

🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.

MCP Servers JavaScript Listed MIT

Is Firecrawl MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 4.2 / 10
Provenance Attested
Signed commits 28%
Last push 2d ago
Advisories None known
Compare Firecrawl MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Firecrawl MCP Server scores 84.8/100 (Grade A), ranked #95 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.2/10; 28% of recent commits are signed; no published advisory affects its latest release (firecrawl-mcp); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Firecrawl MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Firecrawl MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/firecrawl/firecrawl-mcp-server, MIT, last pushed 2026-10-09. 28% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.2/10 (scanned Oct 2, 2026). The checks that decide who can get a change released:

    • Code Review5
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 5
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • npm firecrawl-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: firecrawl-mcp 3.29.1. No published advisory affects it (OSV, checked 2026-10-11).

Changes to this chain

  • 2026-09-30 Package provenance attestation detected

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Firecrawl MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Firecrawl MCP Server compares in MCP Servers

  1. #31 Finopsmcp 84.8 ±0
  2. #32 Markdown Vault MCP 84.8 ±0
  3. #33 Firecrawl MCP Server 84.8 this agent
  4. #34 Stripe Agent Toolkit 84.7 −0.1
  5. #35 Google Flights MCP (fli) 84.5 −0.3

Bars show each HVTrust score; the tick marks Firecrawl MCP Server’s 84.8.

Where the 84.8 comes from

HVTrust dimensions vs the MCP Servers average

84.8 / 100 · 100.0% confidence

Firecrawl MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.2 / 25
3.8 above avg 10.4
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.5 above avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.1 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.7 above avg 12.2
AdoptionLog-scaled stars · package downloads
16.2 / 20
8.8 above avg 7.4

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-10-10
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-10-10
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-10-10
Rank Moved
Rank dropped 14 spots (#83 → #97)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.2/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Firecrawl MCP Server View MCP Servers Report missing data
86.9
Activity sub-score · out of 100
#33
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-11 04:08 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
7.6k
Forks
903
Last Push
2026-10-09
2 days ago
Commits (4 wk)
249
Downloads (7d)
146,686
npm
HN mentions (30d)
—
Open Issues
91
Rank Change
▲2
was #97

Analysis

Activity Inputs

86.9 / 100
StarsRepository reach
23.3 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.7 / 20

Common questions about Firecrawl MCP Server

Public supply-chain signals for Firecrawl MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Firecrawl MCP Server carries less obvious unverified-evidence risk than projects with thin signals.
Does Firecrawl MCP Server publish package provenance?
Yes. Firecrawl MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Firecrawl MCP Server have an OpenSSF Scorecard?
Firecrawl MCP Server has an OpenSSF Scorecard score of 4.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Firecrawl MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Firecrawl MCP Server use?
Firecrawl MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Firecrawl MCP Server's commits signed?
28% of the last 100 commits to Firecrawl MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Firecrawl MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Firecrawl MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-10-10
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-10-10
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-09-30
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-30
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini
2026-09-30
Provenance Added
Package provenance attestation detected

Maintain Firecrawl MCP Server?

For maintainers

HVTrust scores Firecrawl MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 21HVTrust 3Grade 3Surface 2Provenance 1Surface 1Surface 1
2026-10-10
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-10-10
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-10-10
Rank Moved
Rank dropped 14 spots (#83 → #97)
2026-09-30
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-30
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini
2026-09-30
Provenance Added
Package provenance attestation detected
2026-09-30
Grade Changed
Trust grade B → A
2026-09-30
Rank Moved
Rank rose 185 spots (#253 → #68)
2026-09-30
HVTrust Changed
HVTrust up 12.3pts (73.9 → 86.2)
2026-09-28
Rank Moved
Rank rose 17 spots (#264 → #247)
2026-09-26
Rank Moved
Rank rose 28 spots (#299 → #271)
2026-09-23
Rank Moved
Rank dropped 187 spots (#121 → #308)
2026-09-21
Rank Moved
Rank rose 204 spots (#326 → #122)
2026-09-11
Rank Moved
Rank dropped 12 spots (#319 → #331)
2026-09-07
Rank Moved
Rank dropped 21 spots (#291 → #312)
2026-09-05
Rank Moved
Rank dropped 59 spots (#234 → #293)
2026-09-04
Grade Changed
Trust grade D → B
2026-09-04
Rank Moved
Rank rose 703 spots (#937 → #234)
2026-09-04
HVTrust Changed
HVTrust up 25.7pts (43.8 → 69.5)
2026-09-03
Rank Moved
Rank dropped 50 spots (#887 → #937)
2026-09-02
Grade Changed
Trust grade B → D
2026-09-02
Rank Moved
Rank dropped 681 spots (#206 → #887)
2026-09-02
HVTrust Changed
HVTrust down 26.5pts (70.2 → 43.7)
2026-08-31
Rank Moved
Rank dropped 24 spots (#175 → #199)
2026-08-26
Rank Moved
Rank dropped 14 spots (#148 → #162)
2026-08-24
Rank Moved
Rank dropped 10 spots (#139 → #149)
2026-08-19
Rank Moved
Rank dropped 12 spots (#136 → #148)
2026-08-17
Rank Moved
Rank rose 10 spots (#145 → #135)
2026-08-13
Rank Moved
Rank dropped 10 spots (#129 → #139)
2026-08-12
Rank Moved
Rank rose 10 spots (#139 → #129)
2026-08-08
Rank Moved
Rank dropped 12 spots (#115 → #127)
2026-07-25
Rank Moved
Rank rose 12 spots (#116 → #104)
GitHub → Website → npm: firecrawl-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 84.8 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/firecrawl-mcp-server.svg)](https://hvtracker.net/agents/firecrawl-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/firecrawl-mcp-server"><img src="https://hvtracker.net/badge/firecrawl-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON