vulnerability_check — ContrastAPI MCP Prompt

vulnerability_check is one of 3 prompts on the ContrastAPI MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke vulnerability_check from your client

• Claude Code ContrastAPI Prompt/vulnerability_check run in your project directory
• Claude Desktop ContrastAPI Prompt/vulnerability_check ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor ContrastAPI Prompt/vulnerability_check ~/.cursor/mcp.json
• VS Code ContrastAPI Prompt/vulnerability_check .vscode/mcp.json
• Zed ContrastAPI Prompt/vulnerability_check ~/.config/zed/settings.json
• Windsurf ContrastAPI Prompt/vulnerability_check ~/.codeium/windsurf/mcp_config.json
• Cline ContrastAPI Prompt/vulnerability_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI ContrastAPI Prompt/vulnerability_check ~/.gemini/settings.json
• Grok ContrastAPI Prompt/vulnerability_check .mcp.json (in your project root)
• ChatGPT ContrastAPI Prompt/vulnerability_check Settings → Connectors → Advanced → Developer mode
• Claude.ai ContrastAPI Prompt/vulnerability_check Settings → Connectors → Add custom connector
• LangChain ContrastAPI Prompt/vulnerability_check pip install langchain-mcp-adapters

Other prompts on this server

• security_audit
• contrast_triage

ContrastAPI also offers 3 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.