sanctions_check — APEX EVM Reads MCP Tool
sanctions_check
(sanctions check) is one of 17 tools on the
APEX EVM Reads
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call sanctions_check from your client
- Claude Code APEX EVM Reads sanctions_check run in your project directory
- Claude Desktop APEX EVM Reads sanctions_check ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor APEX EVM Reads sanctions_check ~/.cursor/mcp.json
- VS Code APEX EVM Reads sanctions_check .vscode/mcp.json
- Zed APEX EVM Reads sanctions_check ~/.config/zed/settings.json
- Windsurf APEX EVM Reads sanctions_check ~/.codeium/windsurf/mcp_config.json
- Cline APEX EVM Reads sanctions_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI APEX EVM Reads sanctions_check ~/.gemini/settings.json
- Grok APEX EVM Reads sanctions_check .mcp.json (in your project root)
- ChatGPT APEX EVM Reads sanctions_check Settings → Connectors → Advanced → Developer mode
- Claude.ai APEX EVM Reads sanctions_check Settings → Connectors → Add custom connector
- LangChain APEX EVM Reads sanctions_check pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http apex-evm https://apexfaucet.xyz/api/mcp/evmOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 13 October 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.