Sanctions MCP Server

What does “Sanctions” MCP Server do?

The Sanctions MCP Server is a tool designed to connect AI assistants with comprehensive sanctions screening capabilities. By leveraging the OFAC API, this MCP Server allows AI-driven workflows to screen individuals and organizations against major global sanctions lists, such as OFAC SDN, UN, and OFSI. Developers can use the server to perform risk assessments, customize screening parameters (like minimum match scores), and select specific sanctions lists for compliance needs. This enhances development workflows by enabling automated, reliable compliance checks, entity screening, and detailed match reporting directly within AI-powered environments.

List of Prompts

No explicit prompt templates are mentioned in the repository.

List of Resources

No explicit MCP resources are described in the repository.

List of Tools

• Sanctions Screening Tool
  Screens individuals and organizations against major global sanctions lists using various identifiers (name, address, ID documents, etc.). Allows specification of minimum match score and source lists. Returns detailed match information, scores, and source data.

Use Cases of this MCP Server

• Compliance and Risk Assessment
  Automate screening of individuals and organizations to ensure compliance with international sanctions regulations, reducing manual effort and errors.
• KYC (Know Your Customer) Workflows
  Integrate automated sanctions checks into onboarding processes for banks, fintechs, and other regulated entities.
• Transaction Monitoring
  Screen transaction parties in real-time to prevent prohibited dealings and enhance anti-money laundering (AML) systems.
• Custom Risk Threshold Management
  Customize minimum match scores and select specific sanctions sources for tailored compliance and risk management.
• Bulk Entity Screening
  Process and screen large sets of entities (people or organizations) efficiently within AI-powered applications.

How to set it up

Windsurf

No specific setup instructions for Windsurf are provided in the repository.

Claude

1. Prerequisites:
   • Install Node.js v20 or higher
   • Install npm or yarn
   • Obtain your OFAC API key (if required)
2. Clone repository:

   git clone https://github.com/madupay/mcp-sanctions
   cd mcp-sanctions
   npm install
   

3. Configure claude_desktop_config.json:
   Add the following snippet, updating paths and API key:

   {
     "mcpServers": {
       "sanctions": {
         "command": "/path/to/your/node",
         "args": ["/path/to/your/mcp-sanctions/index.js"],
         "env": {
           "OFAC_API_API_KEY": "YOUR_API_KEY_HERE"
         }
       }
     }
   }
   

4. Save and restart Claude Desktop
   Restart the application for changes to take effect.
5. Verify the sanctions screening capability is enabled.

Securing API Keys

API keys (such as OFAC_API_API_KEY) should be stored in the env section of your MCP server configuration:

"env": {
  "OFAC_API_API_KEY": "YOUR_API_KEY_HERE"
}

Cursor

No specific setup instructions for Cursor are provided in the repository.

Cline

No specific setup instructions for Cline are provided in the repository.

How to use this MCP inside flows

Using MCP in FlowHunt

To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:

{
  "sanctions": {
    "transport": "streamable_http",
    "url": "https://yourmcpserver.example/pathtothemcp/url"
  }
}

Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “sanctions” to whatever the actual name of your MCP server is and replace the URL with your own MCP server URL.

Overview

| Roots Support | ⛔ | Not mentioned |

Based on the available documentation and repository contents, the Sanctions MCP Server is straightforward and focused. It offers a specialized tool, clear setup instructions for Claude, and covers API key security, but lacks detailed information on prompt templates, multiple explicit resources, and broader platform integration.

Our opinion

MCP Score: 4/10
This MCP Server is practical and well-documented for its primary use case (sanctions screening), but lacks depth in MCP-specific features like prompts, resources, roots, and sampling support. It’s best for straightforward AI compliance integrations.

MCP Score