batch_screen — US OFAC Sanctions Screening MCP MCP Tool
batch_screen
(batch screen) is one of 3 tools on the
US OFAC Sanctions Screening MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call batch_screen from your client
- Claude Code US OFAC Sanctions Screening MCP batch_screen run in your project directory
- Claude Desktop US OFAC Sanctions Screening MCP batch_screen ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor US OFAC Sanctions Screening MCP batch_screen ~/.cursor/mcp.json
- VS Code US OFAC Sanctions Screening MCP batch_screen .vscode/mcp.json
- Zed US OFAC Sanctions Screening MCP batch_screen ~/.config/zed/settings.json
- Windsurf US OFAC Sanctions Screening MCP batch_screen ~/.codeium/windsurf/mcp_config.json
- Cline US OFAC Sanctions Screening MCP batch_screen ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI US OFAC Sanctions Screening MCP batch_screen ~/.gemini/settings.json
- Grok US OFAC Sanctions Screening MCP batch_screen .mcp.json (in your project root)
- ChatGPT US OFAC Sanctions Screening MCP batch_screen Settings → Connectors → Advanced → Developer mode
- Claude.ai US OFAC Sanctions Screening MCP batch_screen Settings → Connectors → Add custom connector
- LangChain US OFAC Sanctions Screening MCP batch_screen pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http us-sanctions-screen-mcp https://us-sanctions-screen-mcp.donniertf.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 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.