review_epcis_events — TracePass MCP Prompt

review_epcis_events 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 review_epcis_events from your client

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

Other prompts on this server

• audit_passport
• onboard_product
• explain_dpp_requirements
• compliance_gap_check

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.