Is Firecrawl MCP Server safe to use?

Firecrawl MCP Server has an HVTrust score of 70.1/100 (Grade B), ranked #139 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Firecrawl MCP Server?

Firecrawl MCP Server scores 70.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 7.2k GitHub stars and is categorized under MCP Servers.

Firecrawl MCP Server

firecrawl/firecrawl-mcp-server

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

MCP Servers JavaScript Grade B Listed MIT

70.1/100

Rank #139 of 1283

Compare Firecrawl MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-11 · 0d ago

Recent change

Rank

Is Firecrawl MCP Server safe? Firecrawl MCP Server scores 70.1/100 (Grade B), ranked #139 of 1283 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.3/10; 38% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#28 Anytype MCP — 70.8 (B) → #29 Canvas MCP — 70.4 (B) → #31 Exa MCP Server — 69.6 (B) → #32 Google Flights MCP (fli) — 69.6 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-08

Rank Moved

Rank dropped 12 spots (#115 → #127)

2026-07-25

Rank Moved

Rank rose 12 spots (#116 → #104)

2026-07-13

Provider Added

Runtime surface grew — new detected provider dependency: Firecrawl

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.3/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

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

83.4

Activity sub-score · out of 100

#30

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 B 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 →

Activity & Reach

Stars

7.2k

Forks

843

Last Push

2026-08-11

today

Commits (4 wk)

Downloads (7d)

102,944

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #139

Analysis

HVTrust Dimensions vs MCP Servers

70.1 / 100 · 100.0% confidence

Firecrawl MCP Server MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

7.3 / 25

2.3 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

3.4 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

18.9 / 20

6.4 above avg 12.5

AdoptionLog-scaled stars · package downloads

15.9 / 20

10.1 above avg 5.8

Activity Inputs

83.4 / 100

StarsRepository reach

23.1 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

21.7 / 25

CommunityFork signal

13.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.3 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

38%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 9

CII-Best-Practices 0

Code-Review 6

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

Is Firecrawl MCP Server safe?

Firecrawl MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Firecrawl MCP Server publish package provenance?

No published build provenance is currently detected for Firecrawl MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Firecrawl MCP Server have an OpenSSF Scorecard?

Firecrawl MCP Server has an OpenSSF Scorecard score of 4.3/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 1 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?

38% 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

1 detected

Public provider/service dependencies detected.

Firecrawl

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-07-13

Provider Added

Runtime surface grew — new detected provider dependency: Firecrawl

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Activity Resumed

Activity resumed

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

2026-08-08

Rank Moved

Rank dropped 12 spots (#115 → #127)

2026-07-25

Rank Moved

Rank rose 12 spots (#116 → #104)

2026-07-13

Provider Added

Runtime surface grew — new detected provider dependency: Firecrawl

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Activity Resumed

Activity resumed

2026-07-13

Grade Changed

Trust grade D → B

2026-07-13

Rank Moved

Rank rose 241 spots (#344 → #103)

2026-07-13

HVTrust Changed

HVTrust up 62.0pts (7.3 → 69.3)

2026-07-13

Activity Score Changed

Activity score up 83pts (0 → 83)

2026-07-12

Newly Listed

First tracked at rank #344

GitHub → npm: firecrawl-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON