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