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