MMailmodo MCP ServerMailmodo MCP server to interact with Mailmodo APIs listed here. https://www.mailmodo.com/developers/8e957152b6128-getting-started-with-mailmodo-api

mcp-so:Mailmodo_Mailmodo

View source
A
92/100

First Seen

Feb 18, 2026

Last Scanned

Feb 20, 2026

Findings

3

Score

92/100

MEDIUM 1
LOW 2

Findings (3)

MEDIUM
Auto-confirm flag bypassing user verification
L55

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 MCP server without version pin
L53

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.

LOW
Runtime URL controlling behavior
L59

Detects URLs fetched at runtime that control or influence agent behavior without pinning

GET MAILMODO KEY from https:// + settings
FIX

Avoid loading configuration or behavior-controlling content from runtime URLs. Bundle required configurations locally or pin remote config to versioned, integrity-verified endpoints.

FP?

Likely FP if the URL in the match is a documentation link or example URL (e.g., example.com) rather than an actual runtime-fetched configuration endpoint.