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