Gemini CLI sanctions screening mcp server sanctions_resolve_entity
How to: Gemini CLI sanctions screening mcp server sanctions_resolve_entity
Add sanctions screening mcp server to Gemini CLI
-
01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"sanctions-screening-mcp-server": {
"httpUrl": "https://sanctions-screening.caseyjhand.com/mcp"
}
}
}-
02
Save the file and restart Gemini CLI.
-
03
Ask for something sanctions_resolve_entity does. Gemini CLI lists the server's tools on connect and calls sanctions_resolve_entity itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that sanctions screening mcp server's identifier in your config matches the one above exactly.
Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs
Set these first
sanctions screening mcp server will not start until these are set, so sanctions_resolve_entity never becomes available.
-
MCP_LOG_LEVEL -
SANCTIONS_MIRROR_PATH -
SANCTIONS_FUZZY_MIN_SCORE -
SANCTIONS_NORMALIZE_INPUTS
Same tool, other clients
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.