Firecrawl MCP server
3 tools · Last check that passed 27 Oct 2026, 01:50 UTC
Firecrawl's own remote MCP server gives an agent web scraping, search and document parsing, within daily limits with no sign-in. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 3 tools
| Tool | Counted as |
|---|---|
firecrawl_parse | Said to only read |
firecrawl_scrape | Said to only read |
firecrawl_search | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
13 of the last 13 checks passed
A check passes when the server lists its tools. Checked at https://mcp.firecrawl.dev/v2/mcp.
Recent changes
23 Oct 2026, 09:53 UTC, after a check on 22 Oct 2026, 09:45 UTC
Description rewritten on firecrawl_scrape. Inputs or outputs changed on firecrawl_scrape.
21 Oct 2026, 09:32 UTC, after a check on 20 Oct 2026, 09:42 UTC
Description rewritten on firecrawl_scrape, firecrawl_search. Inputs or outputs changed on firecrawl_search.
18 Oct 2026, 06:11 UTC, after a check on 16 Oct 2026, 18:19 UTC
Description rewritten on firecrawl_scrape, firecrawl_search. Inputs or outputs changed on firecrawl_scrape, firecrawl_search.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Firecrawl's tools change.
One email when Firecrawl's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- With a sign-in or an API key, the same server reaches the full tool set on the team's plan. Firecrawl's MCP documentation
- Its interact tool can click, type and fill forms in a real browser, so it acts on live pages. Firecrawl's MCP server README
- Scraped pages and search results come back to the agent, and text an agent reads can carry instructions for it. OWASP, prompt injection
How to limit it
With Firecrawl's own settings, as its documentation describes them. Stackduke has not tested them.
- Review and revoke connections from Firecrawl's MCP settings. Firecrawl's MCP documentation
- Never put an API key in the server address or in an agent chat, as Firecrawl advises. Firecrawl's MCP server README
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.