preflight-security-audit — assay MCP Prompt
preflight-security-audit
is one of 2 prompts on the
assay
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke preflight-security-audit from your client
- Claude Code assay Prompt/preflight-security-audit run in your project directory
- Claude Desktop assay Prompt/preflight-security-audit ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor assay Prompt/preflight-security-audit ~/.cursor/mcp.json
- VS Code assay Prompt/preflight-security-audit .vscode/mcp.json
- Zed assay Prompt/preflight-security-audit ~/.config/zed/settings.json
- Windsurf assay Prompt/preflight-security-audit ~/.codeium/windsurf/mcp_config.json
- Cline assay Prompt/preflight-security-audit ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI assay Prompt/preflight-security-audit ~/.gemini/settings.json
- Grok assay Prompt/preflight-security-audit .mcp.json (in your project root)
- ChatGPT assay Prompt/preflight-security-audit Settings → Connectors → Advanced → Developer mode
- Claude.ai assay Prompt/preflight-security-audit Settings → Connectors → Add custom connector
- LangChain assay Prompt/preflight-security-audit pip install langchain-mcp-adapters
Other prompts on this server
assay also offers 10 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 14 November 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.