ofac.wallet.screen — AurelianFlo MCP Prompt

ofac.wallet.screen is one of 5 prompts on the AurelianFlo MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke ofac.wallet.screen from your client

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

Other prompts on this server

• ofac.wallet.batch
• compliance_exposure_forecast
• compliance_queue_optimize
• report.artifact.render

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.