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