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