audit_passport — TracePass MCP Prompt

audit_passport is one of 5 prompts on the TracePass MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke audit_passport from your client

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

Other prompts on this server

• onboard_product
• explain_dpp_requirements
• compliance_gap_check
• review_epcis_events

TracePass also offers 2 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.