mcp-duckgo

SUSPICIOUS / HIGH RISK (operational): The manifest's behavior is plausibly legitimate for search/fetch features, but the combination of runtime npx execution (unpinned) and forwarding of arbitrary user inputs/URLs to an external MCP server creates meaningful supply-chain and data-exfiltration risks. Recommended mitigations before use: (1) Eliminate or restrict runtime npx execution — use pinned, vetted packages or packaged SDKs and avoid executing code fetched at runtime. (2) Require explicit documentation and vetting of the MCP server operator; prefer official APIs or self-hosted fetchers. (3) Implement URL allowlist/denylist and sanitize or redact sensitive inputs. (4) Add version pinning, integrity checks, and telemetry/alerting for unexpected network contacts. If these mitigations cannot be confirmed, block or quarantine this skill.