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