search_sanctions — jp biz opportunity MCP Tool Read-only
search_sanctions
(search sanctions) is one of 6 tools on the
jp biz opportunity
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search_sanctions from your client
- Claude Code jp biz opportunity search_sanctions run in your project directory
- Claude Desktop jp biz opportunity search_sanctions ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor jp biz opportunity search_sanctions ~/.cursor/mcp.json
- VS Code jp biz opportunity search_sanctions .vscode/mcp.json
- Zed jp biz opportunity search_sanctions ~/.config/zed/settings.json
- Windsurf jp biz opportunity search_sanctions ~/.codeium/windsurf/mcp_config.json
- Cline jp biz opportunity search_sanctions ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI jp biz opportunity search_sanctions ~/.gemini/settings.json
- Grok jp biz opportunity search_sanctions .mcp.json (in your project root)
- ChatGPT jp biz opportunity search_sanctions Settings → Connectors → Advanced → Developer mode
- Claude.ai jp biz opportunity search_sanctions Settings → Connectors → Add custom connector
- LangChain jp biz opportunity search_sanctions pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http jp-biz-opportunity https://jp-biz-opportunity-62ko7b2uwa-an.a.run.app/mcpOther 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.