DDefangThe Defang Model Context Protocol (MCP)⁠ Server is tailored for developers who work primarily within integrated development environments (IDEs). It enables seamless cloud deployment from supported editors such as Cursor, Windsurf, VS Code, VS Code Insiders, and Claude, delivering a fully integrated experience without leaving your development environment.

mcp-so:defang_DefangLabs

View source
B
77/100

First Seen

Feb 19, 2026

Last Scanned

Feb 20, 2026

Findings

4

Score

77/100

HIGH 1
MEDIUM 1
LOW 2

Findings (4)

HIGH
Zero-width character obfuscation
L23

Detects zero-width characters used to hide content

FIX

Remove hidden directives embedded in markdown, HTML comments, or encoded text. All agent-facing text should be explicit and visible in the skill definition.

FP?

Likely FP if the match is a standard markdown formatting pattern or HTML comment used for documentation rather than concealing directives.

MEDIUM
Auto-confirm flag bypassing user verification
L62

Detects -y, --yes, or --auto-approve flags in MCP/skill install commands that bypass user confirmation

"-y"
FIX

Remove the -y/--yes auto-confirm flag from MCP server launch arguments. This flag bypasses user confirmation prompts and allows unattended execution of potentially dangerous operations.

FP?

Likely FP if the matched text is an isolated flag (-y or --yes) in documentation describing command-line options, not in an actual MCP config.

LOW
npx auto-install without confirmation
L38

Detects npx with -y flag that bypasses user confirmation for package installation

npx -y 
FIX

Replace npx -y with an explicit npm install step that pins the package to a specific version, then run it. Remove the -y flag to require user confirmation.

FP?

Likely FP if the npx command runs a well-known, trusted tool (e.g., create-react-app) in documentation context with no version pinning concern.

LOW
npx MCP server without version pin
L60

Detects MCP server configs using npx to run packages without version pinning

"command": "npx"
FIX

Pin the npx package in the MCP config to an exact version (e.g., @scope/server@1.2.3). Unpinned npx commands can silently fetch a compromised package version.

FP?

Likely FP if the MCP config is a local development setup example, though unpinned npx in production configs is a real supply chain risk.