Firecrawl MCP Server
MCP server for Firecrawl — web search, scraping, and biomedical/arXiv paper search.
io.github.firecrawl/firecrawl-mcp-server
Publication
Published
Publisher
firecrawl
Publisher identity: Not verified
Primary source
Official MCP Registry record
https://github.com/firecrawl/firecrawl-mcp-server.gitStatic analysis · human review · publication
Security evidence
Scanner signals, coverage and review decisions describe different parts of this report.
- Scan status
- completed
- Coverage
- Sufficient source coverage
- Static risk signals
- 12/100 · medium
- Finding count
- 7
- Highest finding severity
- medium
- Human review
- Approved review
- Review freshness
- Stale review
- Publication
- Published
Scan coverage and reliability
The scan completed with enough source coverage for ToolRepute's current review workflow. This does not verify runtime behavior.
Reliability: Meets current requirements
- Scanner version
- V6
- Scan run
- 335
- Last scan date
- 2026-09-26
- Files scanned
- 47
- Bytes scanned
- 636,500
- Manifest
- Found
- Source commit
- Pinned
- Truncation
- No
Analyzed source
https://github.com/firecrawl/firecrawl-mcp-server.git
Analyzed commit: b6d8acd1fd6a7c8780a8273e0f79862f1c22b8d0
This assessment covers the available repository source. It does not inspect the hosted remote service or its runtime behavior.
Human review and publication
This historical decision does not establish current approval for the current review workflow. It may concern an older run, changed evidence or an older scanner.
- Review decision
- Approved review
- Review date
- 2026-09-26
- Reviewed scan run
- 335
- Reviewed commit
- b6d8acd1fd6a7c8780a8273e0f79862f1c22b8d0
Publication is a decision to display evidence under ToolRepute's current rules, not a security certification, endorsement or guarantee.
Internal reviewer identity, review notes and private metadata are not displayed.
Published findings
LowCommand-line executable declaredNPM_BIN_DECLAREDpackage.jsonFinding details and evidence
Command-line executable declared
Category: code execution
What was found
The package manifest exposes one or more command-line entry points.
Why it matters
Command-line entry points indicate code intended to execute on the user's system.
Evidence snippet
No public snippet is available. It was not recorded or is withheld to protect sensitive content.
Scanner interpretation
A static rule match is a signal for contextual inspection, not a confirmed vulnerability or malicious behavior.
Recommended check
Inspect the declared command-line entry point and its startup behavior, requested permissions and inputs before running it.
Limitations and legitimate-use context
Declaring a command-line tool is common and does not by itself indicate unsafe behavior.
Lownpm publish lifecycle script declaredNPM_PUBLISH_LIFECYCLE_SCRIPTpackage.jsonFinding details and evidence
npm publish lifecycle script declared
Category: code execution
What was found
The package declares a lifecycle script associated with preparation or publication.
Why it matters
Such scripts show automated code execution in the package workflow and provide useful review context.
Evidence snippet
prepare: npm run build
Scanner interpretation
A static rule match is a signal for contextual inspection, not a confirmed vulnerability or malicious behavior.
Recommended check
Check which preparation or publication workflow invokes the script and distinguish it from consumer installation.
Limitations and legitimate-use context
Publish-oriented scripts do not normally run when a consumer installs the package.
MediumSecret-like value in reference contentSECRET_GENERIC_LITERAL_NON_PRODUCTIONtests/mcp-smoke.test.mjs:1297Finding details and evidence
Secret-like value in reference content
Category: credential exposure
What was found
Static analysis detected a secret-like literal in contextual test, example, comment, or placeholder content.
Why it matters
Even contextual secret-like values should be checked to rule out accidental credential exposure.
Evidence snippet
No public snippet is available. It was not recorded or is withheld to protect sensitive content.
Scanner interpretation
A static rule match is a signal for contextual inspection, not a confirmed vulnerability or malicious behavior.
Recommended check
Determine whether the detected material is an intentional non-live fixture or a real credential. If exposure is confirmed, revoke or rotate it and remove it from source history; do not copy the value into public reports.
Limitations and legitimate-use context
This may be intentional test, example, or reference content and does not confirm an exposed live credential.
MediumSecret-like value in reference contentSECRET_GENERIC_LITERAL_NON_PRODUCTIONtests/mcp-smoke.test.mjs:2418Finding details and evidence
Secret-like value in reference content
Category: credential exposure
What was found
Static analysis detected a secret-like literal in contextual test, example, comment, or placeholder content.
Why it matters
Even contextual secret-like values should be checked to rule out accidental credential exposure.
Evidence snippet
No public snippet is available. It was not recorded or is withheld to protect sensitive content.
Scanner interpretation
A static rule match is a signal for contextual inspection, not a confirmed vulnerability or malicious behavior.
Recommended check
Determine whether the detected material is an intentional non-live fixture or a real credential. If exposure is confirmed, revoke or rotate it and remove it from source history; do not copy the value into public reports.
Limitations and legitimate-use context
This may be intentional test, example, or reference content and does not confirm an exposed live credential.
MediumSecret-like value in reference contentSECRET_GENERIC_LITERAL_NON_PRODUCTIONtests/mcp-smoke.test.mjs:3047Finding details and evidence
Secret-like value in reference content
Category: credential exposure
What was found
Static analysis detected a secret-like literal in contextual test, example, comment, or placeholder content.
Why it matters
Even contextual secret-like values should be checked to rule out accidental credential exposure.
Evidence snippet
No public snippet is available. It was not recorded or is withheld to protect sensitive content.
Scanner interpretation
A static rule match is a signal for contextual inspection, not a confirmed vulnerability or malicious behavior.
Recommended check
Determine whether the detected material is an intentional non-live fixture or a real credential. If exposure is confirmed, revoke or rotate it and remove it from source history; do not copy the value into public reports.
Limitations and legitimate-use context
This may be intentional test, example, or reference content and does not confirm an exposed live credential.
MediumSecret-like value in reference contentSECRET_GENERIC_LITERAL_NON_PRODUCTIONtests/mcp-smoke.test.mjs:3177Finding details and evidence
Secret-like value in reference content
Category: credential exposure
What was found
Static analysis detected a secret-like literal in contextual test, example, comment, or placeholder content.
Why it matters
Even contextual secret-like values should be checked to rule out accidental credential exposure.
Evidence snippet
No public snippet is available. It was not recorded or is withheld to protect sensitive content.
Scanner interpretation
A static rule match is a signal for contextual inspection, not a confirmed vulnerability or malicious behavior.
Recommended check
Determine whether the detected material is an intentional non-live fixture or a real credential. If exposure is confirmed, revoke or rotate it and remove it from source history; do not copy the value into public reports.
Limitations and legitimate-use context
This may be intentional test, example, or reference content and does not confirm an exposed live credential.
MediumSecret-like value in reference contentSECRET_GENERIC_LITERAL_NON_PRODUCTIONtests/mcp-smoke.test.mjs:3294Finding details and evidence
Secret-like value in reference content
Category: credential exposure
What was found
Static analysis detected a secret-like literal in contextual test, example, comment, or placeholder content.
Why it matters
Even contextual secret-like values should be checked to rule out accidental credential exposure.
Evidence snippet
No public snippet is available. It was not recorded or is withheld to protect sensitive content.
Scanner interpretation
A static rule match is a signal for contextual inspection, not a confirmed vulnerability or malicious behavior.
Recommended check
Determine whether the detected material is an intentional non-live fixture or a real credential. If exposure is confirmed, revoke or rotate it and remove it from source history; do not copy the value into public reports.
Limitations and legitimate-use context
This may be intentional test, example, or reference content and does not confirm an exposed live credential.
Reputation evidence
Insufficient evidence · low confidence · model v1
Evidence support score: 5/100. This is separate from risk, review and publication.
Assessment as of 2026-10-22. Live repository HEAD is not checked when this page loads.
Security evidence · 0/25LIMITED · low confidence
Reliable mapped v6 scope is not established; evidence age: recent.
Static support is capped at 18/25 before a risk deduction of ceil(riskScore/4); zero findings does not establish safety.
Last observed: 2026-09-26
- scan record 335: Scanner v6; completed; manifest found; sufficient scope true; 47 files / 636500 bytes; 7 findings; not truncated; scanner risk score 12.Commit b6d8acd1fd6a7c8780a8273e0f79862f1c22b8d0Source evidence
Static analysis covers a bounded source scope, not runtime, dependencies in full, or hosted behavior.
Source transparency · 5/25STALE · low confidence
Completed matching public GitHub acquisition: not established (+0).
Unique primary mapping: observed (+5).
Completed matching pinned commit: not established (+0).
Completed matching source mapping: not established (+0).
Matching manifest and sufficient untruncated scope: not established (+0).
Last observed: 2026-10-17
- source record 15307: Primary mapping is incomplete or changed. Live repository HEAD is not checked by page requests.Source evidence
- scan record 335: Scanner v6; completed; manifest found; sufficient scope true; 47 files / 636500 bytes; not truncated.Commit b6d8acd1fd6a7c8780a8273e0f79862f1c22b8d0Source evidence
A source mapping does not prove ownership. Repository availability and live HEAD are not rechecked here.
Review freshness · 0/25STALE · low confidence
Current artifact-bound approval earns 25; matching approval with unchecked live HEAD earns 8; stale, missing or rejected evidence earns 0.
Last observed: 2026-09-26
- review record 59: Decision: approved; reviewed run 335; NEXT-11 freshness: stale.
Page requests make no upstream probe. An old approval is not approval of changed evidence.
Registry consistency · 0/10UNKNOWN · low confidence
Unique primary, normalized active/latest official registry observation earns 10 within 30 days, 5 within 90, otherwise 0.
Last observed: 2026-10-17
- registry record 15307: Normalized official record: false; active: true; latest: true; observation age: recent.
Registry consistency is a source-record observation, not identity verification or a security endorsement.
Publisher identity confidence · 0/15UNKNOWN · low confidence
No verified legal, domain or repository-ownership binding is available; free text and the registry verification flag earn no credit.
Last observed: Not available
Publisher name and registry namespace cannot establish legal identity or ownership.
Recorded assessment history (1)
History starts with explicit captures in model v1. Past source and review state cannot be fully reconstructed. Page reads do not save snapshots; changes in the live assessment appear in history only after an explicit capture.
- 2026-10-11 · model v1 · 5/100 · low confidence · scan 335b6d8acd1fd6a7c8780a8273e0f79862f1c22b8d0
Recorded signal breakdown
- Security evidence: 0/25 · LIMITED
- Source transparency: 5/25 · STALE
- Review freshness: 0/25 · STALE
- Registry consistency: 0/10 · UNKNOWN
- Publisher identity confidence: 0/15 · UNKNOWN
Reputation reflects ToolRepute-observed evidence only; it is not a guarantee of security.
Signals may be incomplete or stale. Runtime and hosted behavior may differ from scanned source.
Publisher identity has no verified binding. Repository ownership and legal identity are not established.
This score measures support in the available evidence, not the probability that a tool is safe.
Registry data
Version
3.30.3
Packages
1
Remote endpoints
1
Enrichment
complete
Last fetched
2026-10-17
Registry inclusion identifies the source record. It is not a ToolRepute security endorsement.
Normalized sources
Structured from the Official MCP Registry record.
Enriched 2026-10-17
Packages
firecrawl-mcp
Remote endpoints
streamable-http · mcp.firecrawl.dev
https://mcp.firecrawl.dev/v2/mcpMore reviewed MCP servers
Continue exploring integrations with published ToolRepute reviews.