screen_sanctions_name — Sanctions Check MCP Tool
screen_sanctions_name
(screen sanctions name) is one of 3 tools on the
Sanctions Check
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call screen_sanctions_name from your client
- Claude Code Sanctions Check screen_sanctions_name run in your project directory
- Claude Desktop Sanctions Check screen_sanctions_name ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Sanctions Check screen_sanctions_name ~/.cursor/mcp.json
- VS Code Sanctions Check screen_sanctions_name .vscode/mcp.json
- Zed Sanctions Check screen_sanctions_name ~/.config/zed/settings.json
- Windsurf Sanctions Check screen_sanctions_name ~/.codeium/windsurf/mcp_config.json
- Cline Sanctions Check screen_sanctions_name ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Sanctions Check screen_sanctions_name ~/.gemini/settings.json
- Grok Sanctions Check screen_sanctions_name .mcp.json (in your project root)
- ChatGPT Sanctions Check screen_sanctions_name Settings → Connectors → Advanced → Developer mode
- Claude.ai Sanctions Check screen_sanctions_name Settings → Connectors → Add custom connector
- LangChain Sanctions Check screen_sanctions_name pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sanctions-check https://public-domain-check-production.up.railway.app/sanctions/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.