# Pitfall Log / 踩坑日志

项目：firecrawl/firecrawl-mcp-server

摘要：发现 29 个潜在踩坑项，其中 2 个为 high/blocking；最高优先级：安装坑 - 来源证据：Using n8n to connect to firecrawl-mcp-server throws a 404 error。

## 1. 安装坑 · 来源证据：Using n8n to connect to firecrawl-mcp-server throws a 404 error

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Using n8n to connect to firecrawl-mcp-server throws a 404 error
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/firecrawl/firecrawl-mcp-server/issues/64 | 来源讨论提到 docker 相关条件，需在安装/试用前复核。

## 2. 安全/权限坑 · 失败模式：security_permissions: Proposal: Free AI Agent identity verification for Firecrawl MCP

- 严重度：high
- 证据强度：source_linked
- 发现：Developers should check this security_permissions risk before relying on the project: Proposal: Free AI Agent identity verification for Firecrawl MCP
- 对用户的影响：Developers may expose sensitive permissions or credentials: Proposal: Free AI Agent identity verification for Firecrawl MCP
- 证据：failure_mode_cluster:github_issue | https://github.com/firecrawl/firecrawl-mcp-server/issues/243 | Proposal: Free AI Agent identity verification for Firecrawl MCP

## 3. 安装坑 · 失败模式：installation: Project is on 3.20.2 (2026-06-01) but has no tags or releases since 3.2.0 (2025-09-26)

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: Project is on 3.20.2 (2026-06-01) but has no tags or releases since 3.2.0 (2025-09-26)
- 对用户的影响：Developers may fail before the first successful local run: Project is on 3.20.2 (2026-06-01) but has no tags or releases since 3.2.0 (2025-09-26)
- 证据：failure_mode_cluster:github_issue | https://github.com/firecrawl/firecrawl-mcp-server/issues/255 | Project is on 3.20.2 (2026-06-01) but has no tags or releases since 3.2.0 (2025-09-26)

## 4. 安装坑 · 失败模式：installation: stdio: every tool call returns "Unauthorized" in 3.18.0+ with FIRECRAWL_API_KEY (regression f...

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: stdio: every tool call returns "Unauthorized" in 3.18.0+ with FIRECRAWL_API_KEY (regression from 3.17.0)
- 对用户的影响：Developers may fail before the first successful local run: stdio: every tool call returns "Unauthorized" in 3.18.0+ with FIRECRAWL_API_KEY (regression from 3.17.0)
- 证据：failure_mode_cluster:github_issue | https://github.com/firecrawl/firecrawl-mcp-server/issues/246 | stdio: every tool call returns "Unauthorized" in 3.18.0+ with FIRECRAWL_API_KEY (regression from 3.17.0)

## 5. 安装坑 · 失败模式：installation: v1.12.0

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v1.12.0
- 对用户的影响：Upgrade or migration may change expected behavior: v1.12.0
- 证据：failure_mode_cluster:github_release | https://github.com/firecrawl/firecrawl-mcp-server/releases/tag/v1.12.0 | v1.12.0

## 6. 安装坑 · 来源证据：Your project is now listed on CodeGuilds

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Your project is now listed on CodeGuilds
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/firecrawl/firecrawl-mcp-server/issues/271 | 来源讨论提到 npm 相关条件，需在安装/试用前复核。

## 7. 配置坑 · 失败模式：configuration: v1.2.3: Optimize Batch Processing

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: v1.2.3: Optimize Batch Processing
- 对用户的影响：Upgrade or migration may change expected behavior: v1.2.3: Optimize Batch Processing
- 证据：failure_mode_cluster:github_release | https://github.com/firecrawl/firecrawl-mcp-server/releases/tag/v1.2.3 | v1.2.3: Optimize Batch Processing

## 8. 配置坑 · 失败模式：configuration: v1.2.4: Configurable Settings & Enhanced Documentation

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: v1.2.4: Configurable Settings & Enhanced Documentation
- 对用户的影响：Upgrade or migration may change expected behavior: v1.2.4: Configurable Settings & Enhanced Documentation
- 证据：failure_mode_cluster:github_release | https://github.com/firecrawl/firecrawl-mcp-server/releases/tag/v1.2.4 | v1.2.4: Configurable Settings & Enhanced Documentation

## 9. 配置坑 · 来源证据：MCP tool descriptions teach models the wrong calling convention, causing systematic tool-call failures

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：MCP tool descriptions teach models the wrong calling convention, causing systematic tool-call failures
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/firecrawl/firecrawl-mcp-server/issues/279 | 来源类型 github_issue 暴露的待验证使用条件。

## 10. 能力坑 · 能力判断依赖假设

- 严重度：medium
- 证据强度：source_linked
- 发现：README/documentation is current enough for a first validation pass.
- 对用户的影响：假设不成立时，用户拿不到承诺的能力。
- 证据：capability.assumptions | https://www.npmjs.com/package/firecrawl-mcp | README/documentation is current enough for a first validation pass.

## 11. 运行坑 · 运行可能依赖外部服务

- 严重度：medium
- 证据强度：source_linked
- 发现：项目说明出现 external service/cloud/webhook/database 等运行依赖关键词。
- 对用户的影响：本地安装成功不等于能力可用，外部服务不可用会阻断体验。
- 证据：packet_text.keyword_scan | https://www.npmjs.com/package/firecrawl-mcp | matched external service / cloud / webhook / database keyword

## 12. 维护坑 · 维护活跃度未知

- 严重度：medium
- 证据强度：source_linked
- 发现：未记录 last_activity_observed。
- 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。
- 证据：evidence.maintainer_signals | https://www.npmjs.com/package/firecrawl-mcp | last_activity_observed missing

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 证据：downstream_validation.risk_items | https://www.npmjs.com/package/firecrawl-mcp | no_demo; severity=medium

## 14. 安全/权限坑 · 存在评分风险

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 对用户的影响：风险会影响是否适合普通用户安装。
- 证据：risks.scoring_risks | https://www.npmjs.com/package/firecrawl-mcp | no_demo; severity=medium

## 15. 安全/权限坑 · 来源证据：Proposal: Free AI Agent identity verification for Firecrawl MCP

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Proposal: Free AI Agent identity verification for Firecrawl MCP
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/firecrawl/firecrawl-mcp-server/issues/243 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 16. 安全/权限坑 · 来源证据：[Regulatory Signals] firecrawl-mcp is listed on the MCP Trust Registry — claim it

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：[Regulatory Signals] firecrawl-mcp is listed on the MCP Trust Registry — claim it
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/firecrawl/firecrawl-mcp-server/issues/274 | 来源类型 github_issue 暴露的待验证使用条件。

## 17. 安全/权限坑 · 来源证据：stdio: every tool call returns "Unauthorized" in 3.18.0+ with FIRECRAWL_API_KEY (regression from 3.17.0)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：stdio: every tool call returns "Unauthorized" in 3.18.0+ with FIRECRAWL_API_KEY (regression from 3.17.0)
- 对用户的影响：可能阻塞安装或首次运行。
- 证据：community_evidence:github | https://github.com/firecrawl/firecrawl-mcp-server/issues/246 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 18. 能力坑 · 失败模式：capability: Provided docker container cannot be connected to, because MCP server only listens to ipv6 ::1...

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Provided docker container cannot be connected to, because MCP server only listens to ipv6 ::1 while NGINX proxies traffic to ipv4 loopback
- 对用户的影响：Developers may hit a documented source-backed failure mode: Provided docker container cannot be connected to, because MCP server only listens to ipv6 ::1 while NGINX proxies traffic to ipv4 loopback
- 证据：failure_mode_cluster:github_issue | https://github.com/firecrawl/firecrawl-mcp-server/issues/251 | Provided docker container cannot be connected to, because MCP server only listens to ipv6 ::1 while NGINX proxies traffic to ipv4 loopback

## 19. 能力坑 · 失败模式：capability: Your project is now listed on CodeGuilds

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Your project is now listed on CodeGuilds
- 对用户的影响：Developers may hit a documented source-backed failure mode: Your project is now listed on CodeGuilds
- 证据：failure_mode_cluster:github_issue | https://github.com/firecrawl/firecrawl-mcp-server/issues/254 | Your project is now listed on CodeGuilds

## 20. 能力坑 · 失败模式：conceptual: Using n8n to connect to firecrawl-mcp-server throws a 404 error

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this conceptual risk before relying on the project: Using n8n to connect to firecrawl-mcp-server throws a 404 error
- 对用户的影响：Developers may hit a documented source-backed failure mode: Using n8n to connect to firecrawl-mcp-server throws a 404 error
- 证据：failure_mode_cluster:github_issue | https://github.com/firecrawl/firecrawl-mcp-server/issues/64 | Using n8n to connect to firecrawl-mcp-server throws a 404 error

## 21. 维护坑 · issue/PR 响应质量未知

- 严重度：low
- 证据强度：source_linked
- 发现：issue_or_pr_quality=unknown。
- 对用户的影响：用户无法判断遇到问题后是否有人维护。
- 证据：evidence.maintainer_signals | https://www.npmjs.com/package/firecrawl-mcp | issue_or_pr_quality=unknown

## 22. 维护坑 · 发布节奏不明确

- 严重度：low
- 证据强度：source_linked
- 发现：release_recency=unknown。
- 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。
- 证据：evidence.maintainer_signals | https://www.npmjs.com/package/firecrawl-mcp | release_recency=unknown

## 23. 维护坑 · 失败模式：maintenance: Added Deep Research (Alpha)

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: Added Deep Research (Alpha)
- 对用户的影响：Upgrade or migration may change expected behavior: Added Deep Research (Alpha)
- 证据：failure_mode_cluster:github_release | https://github.com/firecrawl/firecrawl-mcp-server/releases/tag/v1.4.1 | Added Deep Research (Alpha)

## 24. 维护坑 · 失败模式：maintenance: Added llms.txt generator

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: Added llms.txt generator
- 对用户的影响：Upgrade or migration may change expected behavior: Added llms.txt generator
- 证据：failure_mode_cluster:github_release | https://github.com/firecrawl/firecrawl-mcp-server/releases/tag/v1.7.2 | Added llms.txt generator

## 25. 维护坑 · 失败模式：maintenance: Official Release - v1.3.3

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: Official Release - v1.3.3
- 对用户的影响：Upgrade or migration may change expected behavior: Official Release - v1.3.3
- 证据：failure_mode_cluster:github_release | https://github.com/firecrawl/firecrawl-mcp-server/releases/tag/v.1.3.3 | Official Release - v1.3.3

## 26. 维护坑 · 失败模式：maintenance: v2.0.0

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v2.0.0
- 对用户的影响：Upgrade or migration may change expected behavior: v2.0.0
- 证据：failure_mode_cluster:github_release | https://github.com/firecrawl/firecrawl-mcp-server/releases/tag/v2.0.0 | v2.0.0

## 27. 维护坑 · 失败模式：maintenance: v3.0.0

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v3.0.0
- 对用户的影响：Upgrade or migration may change expected behavior: v3.0.0
- 证据：failure_mode_cluster:github_release | https://github.com/firecrawl/firecrawl-mcp-server/releases/tag/v3.0.0 | v3.0.0

## 28. 维护坑 · 失败模式：maintenance: v3.2.0

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v3.2.0
- 对用户的影响：Upgrade or migration may change expected behavior: v3.2.0
- 证据：failure_mode_cluster:github_release | https://github.com/firecrawl/firecrawl-mcp-server/releases/tag/v3.2.0 | v3.2.0

## 29. 维护坑 · 失败模式：maintenance: v3.2.1

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v3.2.1
- 对用户的影响：Upgrade or migration may change expected behavior: v3.2.1
- 证据：failure_mode_cluster:github_release | https://github.com/firecrawl/firecrawl-mcp-server/releases/tag/v3.2.1 | v3.2.1