Jurisdiction Rules — Sanctions Screening MCP Resource

Jurisdiction Rules is one of 5 resources on the Sanctions Screening MCP server. Connect the server and your client can attach it as context.

by client

How to attach Jurisdiction Rules from your client

• Claude Code Sanctions Screening Resource/Jurisdiction Rules run in your project directory
• Claude Desktop Sanctions Screening Resource/Jurisdiction Rules ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Sanctions Screening Resource/Jurisdiction Rules ~/.cursor/mcp.json
• VS Code Sanctions Screening Resource/Jurisdiction Rules .vscode/mcp.json
• Zed Sanctions Screening Resource/Jurisdiction Rules ~/.config/zed/settings.json
• Windsurf Sanctions Screening Resource/Jurisdiction Rules ~/.codeium/windsurf/mcp_config.json
• Cline Sanctions Screening Resource/Jurisdiction Rules ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Sanctions Screening Resource/Jurisdiction Rules ~/.gemini/settings.json
• Grok Sanctions Screening Resource/Jurisdiction Rules .mcp.json (in your project root)
• ChatGPT Sanctions Screening Resource/Jurisdiction Rules Settings → Connectors → Advanced → Developer mode
• Claude.ai Sanctions Screening Resource/Jurisdiction Rules Settings → Connectors → Add custom connector
• LangChain Sanctions Screening Resource/Jurisdiction Rules pip install langchain-mcp-adapters

Other resources on this server

• Capability Manifest
• Supported Booking Platforms
• Error Code Catalog
• Tool-chain cookbook

Sanctions Screening also offers 4 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.