Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for people building agents that need dependable website retrieval and extraction instead of brittle one-off scraping scripts.
Where this stands now
firecrawl/firecrawl-mcp-server ranks #131 of 2304 tracked Radar items by composite score (8.5 against a section median of 5.2). The section currently carries 1197 Bronze, 645 Gold, 462 Silver. RepoRadar has retained observations for this record since 2026-06-20 (99 days in the current window). Signal extremes versus the section: momentum at the 79th percentile.
Who should use it
Who should skip it
Skip firecrawl/firecrawl-mcp-server if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
firecrawl/firecrawl-mcp-server is tracked by RepoRadar as an MCP server in the Radar section. First seen 2026-06-20; the source record was last checked on 2026-06-20. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. firecrawl/firecrawl-mcp-server leads on workflow potential (9.6) and practical usefulness (9.0); its lowest signal is novelty (6.0), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The firecrawl/firecrawl-mcp-server record combines a 8.5/10 composite score with separate popularity (58.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Prompts and fetched page content may transit a third-party service, so do not point it at private or regulated data before reviewing the data path; Scraping internal or authenticated sites through an external service can leak content or trigger policy problems if you treat it like a generic browser.