get_sanctions_entry — Zovo Sanctions Screening MCP Tool Read-only
get_sanctions_entry
(get sanctions entry) 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 get_sanctions_entry from your client
- Claude Code Zovo Sanctions Screening get_sanctions_entry run in your project directory
- Claude Desktop Zovo Sanctions Screening get_sanctions_entry ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Zovo Sanctions Screening get_sanctions_entry ~/.cursor/mcp.json
- VS Code Zovo Sanctions Screening get_sanctions_entry .vscode/mcp.json
- Zed Zovo Sanctions Screening get_sanctions_entry ~/.config/zed/settings.json
- Windsurf Zovo Sanctions Screening get_sanctions_entry ~/.codeium/windsurf/mcp_config.json
- Cline Zovo Sanctions Screening get_sanctions_entry ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Zovo Sanctions Screening get_sanctions_entry ~/.gemini/settings.json
- Grok Zovo Sanctions Screening get_sanctions_entry .mcp.json (in your project root)
- ChatGPT Zovo Sanctions Screening get_sanctions_entry Settings → Connectors → Advanced → Developer mode
- Claude.ai Zovo Sanctions Screening get_sanctions_entry Settings → Connectors → Add custom connector
- LangChain Zovo Sanctions Screening get_sanctions_entry 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.