VVonage API Bindings MCP ServerThis server integrates a variety of Vonage's APIs as tools to help developers work with their applications.
mcp-so:vonage-api-bindings-mcp-server_Vonage-Community
View sourceFirst Seen
Feb 18, 2026
Last Scanned
Feb 18, 2026
Findings
3
Score
84/100
Findings (3)
Benign heading "'@openai/agents:*'\n;\n// Verbose logging\n..." followed by dangerous content (category: credential_access)
cpaas
This server integrates a variety of Vonage's APIs as tools to help developers work with their applications.
Overview
Tools
Comments
Overview
What is Vonage API Bindings MCP Server?
The Vonage AP... Ensure section headings accurately reflect the content that follows. Remove headings that could mislead an LLM into treating content differently than intended.
Likely FP if the heading mismatch is due to inconsistent markdown formatting or a benign section title that happens to contain keywords like system or config.
Detects -y, --yes, or --auto-approve flags in MCP/skill install commands that bypass user confirmation
"-y" 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.
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.
Detects MCP server configs using npx to run packages without version pinning
"command": "npx" 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.
Likely FP if the MCP config is a local development setup example, though unpinned npx in production configs is a real supply chain risk.