# Pitfall Log

Project: mcp-use/mcp-use

Summary: Found 29 structured pitfall item(s), including 4 high/blocking item(s). Top priority: Installation risk - Installation risk requires verification.

## 1. Installation risk - Installation risk requires verification

- Severity: high
- Evidence strength: source_linked
- Finding: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/mcp-use/mcp-use/issues/1727

## 2. Installation risk - Installation risk requires verification

- Severity: high
- Evidence strength: source_linked
- Finding: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/mcp-use/mcp-use/issues/1726

## 3. Configuration risk - Configuration risk requires verification

- Severity: high
- Evidence strength: source_linked
- Finding: Project evidence flags a configuration risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/mcp-use/mcp-use/issues/1724

## 4. Security or permission risk - Security or permission risk requires verification

- Severity: high
- Evidence strength: source_linked
- Finding: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/mcp-use/mcp-use/issues/947

## 5. Installation risk - Installation risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Developers should check this installation risk before relying on the project: Example: Chart Library MCP for financial pattern analysis
- User impact: Developers may fail before the first successful local run: Example: Chart Library MCP for financial pattern analysis
- Evidence: failure_mode_cluster:github_issue | https://github.com/mcp-use/mcp-use/issues/1286

## 6. Installation risk - Installation risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/mcp-use/mcp-use/issues/1286

## 7. Configuration risk - Configuration risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Project evidence flags a configuration risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: capability.host_targets | github_repo:956472076 | https://github.com/mcp-use/mcp-use

## 8. Configuration risk - Configuration risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Developers should check this configuration risk before relying on the project: @mcp-use/cli 3.5.0
- User impact: Upgrade or migration may change expected behavior: @mcp-use/cli 3.5.0
- Evidence: failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/%40mcp-use/cli%403.5.0

## 9. Configuration risk - Configuration risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Developers should check this configuration risk before relying on the project: Refactor HttpConnector and StdioConnector with per-connector configuration
- User impact: Developers may misconfigure credentials, environment, or host setup: Refactor HttpConnector and StdioConnector with per-connector configuration
- Evidence: failure_mode_cluster:github_issue | https://github.com/mcp-use/mcp-use/issues/947

## 10. Configuration risk - Configuration risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Developers should check this configuration risk before relying on the project: mcp-use 1.32.0
- User impact: Upgrade or migration may change expected behavior: mcp-use 1.32.0
- Evidence: failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/mcp-use%401.32.0

## 11. Configuration risk - Configuration risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Developers should check this configuration risk before relying on the project: mcp-use 1.32.1-canary.2
- User impact: Upgrade or migration may change expected behavior: mcp-use 1.32.1-canary.2
- Evidence: failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/mcp-use%401.32.1-canary.2

## 12. Capability evidence risk - Capability evidence risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: README/documentation is current enough for a first validation pass.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: capability.assumptions | github_repo:956472076 | https://github.com/mcp-use/mcp-use

## 13. Runtime risk - Runtime risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Project evidence flags a runtime risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/mcp-use/mcp-use/issues/1723

## 14. Maintenance risk - Maintenance risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Developers should check this migration risk before relying on the project: Stateful StreamableHTTP transport hangs in mcp-use dev — tool result never reaches client (SSE response dropped, works with enableJsonResponse)
- User impact: Developers may hit a documented source-backed failure mode: Stateful StreamableHTTP transport hangs in mcp-use dev — tool result never reaches client (SSE response dropped, works with enableJsonResponse)
- Evidence: failure_mode_cluster:github_issue | https://github.com/mcp-use/mcp-use/issues/1724

## 15. Maintenance risk - Maintenance risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | github_repo:956472076 | https://github.com/mcp-use/mcp-use

## 16. Security or permission risk - Security or permission risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: no_demo
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: downstream_validation.risk_items | github_repo:956472076 | https://github.com/mcp-use/mcp-use

## 17. Security or permission risk - Security or permission risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: no_demo
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: risks.scoring_risks | github_repo:956472076 | https://github.com/mcp-use/mcp-use

## 18. Capability evidence risk - Capability evidence risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this capability risk before relying on the project: Confusing Logs for empty `resources/` folder
- User impact: Developers may hit a documented source-backed failure mode: Confusing Logs for empty `resources/` folder
- Evidence: failure_mode_cluster:github_issue | https://github.com/mcp-use/mcp-use/issues/1727

## 19. Capability evidence risk - Capability evidence risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this capability risk before relying on the project: Refactor: adaptor deduplicate across MCP adapters
- User impact: Developers may hit a documented source-backed failure mode: Refactor: adaptor deduplicate across MCP adapters
- Evidence: failure_mode_cluster:github_issue | https://github.com/mcp-use/mcp-use/issues/1726

## 20. Capability evidence risk - Capability evidence risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this capability risk before relying on the project: fix(cli): send unsubscribe on Ctrl+C in resources subscribe
- User impact: Developers may hit a documented source-backed failure mode: fix(cli): send unsubscribe on Ctrl+C in resources subscribe
- Evidence: failure_mode_cluster:github_issue | https://github.com/mcp-use/mcp-use/issues/1723

## 21. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: issue_or_pr_quality=unknown。
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | github_repo:956472076 | https://github.com/mcp-use/mcp-use

## 22. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: release_recency=unknown。
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | github_repo:956472076 | https://github.com/mcp-use/mcp-use

## 23. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: @mcp-use/cli 3.5.1
- User impact: Upgrade or migration may change expected behavior: @mcp-use/cli 3.5.1
- Evidence: failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/%40mcp-use/cli%403.5.1

## 24. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: @mcp-use/cli 3.5.2-canary.2
- User impact: Upgrade or migration may change expected behavior: @mcp-use/cli 3.5.2-canary.2
- Evidence: failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/%40mcp-use/cli%403.5.2-canary.2

## 25. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: @mcp-use/inspector 10.0.0
- User impact: Upgrade or migration may change expected behavior: @mcp-use/inspector 10.0.0
- Evidence: failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/%40mcp-use/inspector%4010.0.0

## 26. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: @mcp-use/inspector 10.0.1-canary.2
- User impact: Upgrade or migration may change expected behavior: @mcp-use/inspector 10.0.1-canary.2
- Evidence: failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/%40mcp-use/inspector%4010.0.1-canary.2

## 27. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: @mcp-use/inspector 9.0.1
- User impact: Upgrade or migration may change expected behavior: @mcp-use/inspector 9.0.1
- Evidence: failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/%40mcp-use/inspector%409.0.1

## 28. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: mcp-use 1.31.1
- User impact: Upgrade or migration may change expected behavior: mcp-use 1.31.1
- Evidence: failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/mcp-use%401.31.1

## 29. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: mcp-use 1.32.1-canary.1
- User impact: Upgrade or migration may change expected behavior: mcp-use 1.32.1-canary.1
- Evidence: failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/mcp-use%401.32.1-canary.1