Spark
Sign In
MCP Connector

Screen entities against global sanctions lists

An MCP server that screens individuals and organizations against OFAC and other sanctions lists.

Connect
Works with ofac
madupay
Own this? Claim it

Maintainer of this project? Claim this page to edit the listing.

90
Spark score
out of 100
Updated Apr 2025
Fresher alternatives ↓
Version 1.0.0
Models
universal
Add to Favorites

Why it matters

Automate sanctions screening by connecting to the OFAC API and checking individuals and organizations against major global sanctions lists.

Outcomes

What it gets done

01

Screen individuals and organizations against OFAC SDN, UN, OFSI, and other sanctions lists.

02

Configure customizable risk thresholds for match relevance.

03

Utilize multiple identification methods including names, addresses, and passport numbers.

04

Select specific sanctions lists for screening based on compliance needs.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/vb-mcp-sanctions | bash

Capabilities

Tools your agent gets

screen_entity

Screen individuals and organizations against global sanctions lists including OFAC SDN, UN, and OFSI

screen_by_name

Screen entities by name against sanctions lists with customizable risk threshold

screen_by_address

Screen entities by address against sanctions lists

screen_by_identity_document

Screen entities by identity document number against sanctions lists

Overview

mcp-sanctions MCP Server

An MCP server that screens individuals and organizations against OFAC and other global sanctions lists for compliance checks. Use it when a compliance or KYC workflow needs a sanctions-list check on a specific person or organization.

What it does

Screens individuals and organizations against major global sanctions lists - OFAC SDN, NONSDN, DPL, UN, OFSI, and more - via the OFAC API, returning match details, match scores, and source information for compliance risk assessment.

When to use - and when NOT to

Use this when Claude needs to check whether a specific person or organization appears on a sanctions list as part of KYC/compliance screening - for example "Can you check if John Smith born on 1980-01-15 from Syria is on any sanctions lists?" or a custom check against a specific list with a minimum match score. It is a screening tool against named sanctions lists, not a general due-diligence or legal-advice service, and match relevance depends on the risk threshold (minScore, default 95) you set.

Capabilities

  • Sanctions screening for individuals and organizations against OFAC SDN, UN, OFSI, and other major lists.
  • Customizable risk threshold (minScore, 0-100, default 95) to control match relevance.
  • Multiple identification methods: name, date of birth, gender, citizenship/nationality, address, contact info, and identification documents.
  • Source selection: choose which sanctions lists (sources, e.g. SDN, NONSDN, DPL, UN, OFSI) to check against.
  • Screens both person and organization entity types, accepting an array of cases to screen in one request.
  • Accepts an organization check too - for example "Is there a sanctioned entity called Tech Solutions Ltd based in Tehran, Iran?" - or a fully custom query like "Check if Maria Rodriguez with passport number AB123456 from Venezuela is on the OFAC SDN list with a minimum match score of 90."
  • Input schema accepts name, date of birth and gender (for individuals), citizenship/nationality, address details, contact information, and identification documents; the response is a JSON object with match details, match scores, source information, and full entity profiles for each hit, so Claude can reason about match confidence rather than just getting a yes/no answer.

How to install

Requires Node.js v20+, npm or yarn, and git. Clone the repository, run npm install, then add it to claude_desktop_config.json:

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

Restart Claude Desktop after saving the configuration to enable sanctions screening.

Who it's for

Compliance and risk teams building AI-assisted KYC or sanctions-screening workflows who want individual and organization checks against OFAC and other major sanctions lists available directly inside Claude, without building a custom OFAC API integration themselves.

Source README

Sanctions MCP Server

A powerful sanctions screening API MCP Server, leveraging OFAC API to provide comprehensive risk assessments for individuals and organizations.

🎉 Ready for integration with Claude through the Model Context Protocol 🎉

https://github.com/user-attachments/assets/41ea6318-5b17-4da1-8d6d-8cb60b5342ea

Key Features

  • Sanctions Screening: Screen individuals and organizations against major global sanctions lists including OFAC SDN, UN, OFSI, and more
  • Customizable Risk Threshold: Set minimum risk scores to determine match relevance
  • Comprehensive Entity Support: Screen both individuals and organizations with detailed information
  • Multiple Identification Methods: Support for various identifiers including names, addresses, identification documents, and more
  • Source Selection: Choose which sanctions lists to check against based on your compliance needs

How to Use

You can run the Sanctions MCP Server using Node.js directly.

Requirements

  1. Node.js v20 or higher
  2. npm or yarn for dependency management
  3. git

Installation

1. Clone the repository
git clone https://github.com/yourusername/mcp-ofac
cd mcp-ofac
2. Install dependencies
npm install
3. Configure claude_desktop_config.json

Add the following configuration to your claude_desktop_config.json file. Make sure to:

  • Update the paths to match your local Node.js installation and repository location
  • Add your OFAC API key if required
{
  "mcpServers": {
    "sanctions": {
      "command": "/path/to/your/node",
      "args": ["/path/to/your/mcp-ofac/index.js"],
      "env": {
        "OFAC_API_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Usage Examples

Screening an Individual

You can ask Claude to screen individuals against sanctions lists:

"Can you check if John Smith born on 1980-01-15 from Syria is on any sanctions lists?"

Screening an Organization

You can ask Claude to check organizations:

"Is there a sanctioned entity called Tech Solutions Ltd based in Tehran, Iran?"

Custom Screening Parameters

You can specify custom parameters for more targeted screening:

"Check if Maria Rodriguez with passport number AB123456 from Venezuela is on the OFAC SDN list with a minimum match score of 90."

How the Tool Works

The Sanctions MCP Server processes screening requests with the following parameters:

  • cases: Array of entities to screen (individuals or organizations) with identifying information
  • type: Entity type ("person" or "organization")
  • minScore: Minimum score threshold for matches (0-100, default: 95)
  • sources: Which sanctions lists to check against (SDN, NONSDN, DPL, UN, OFSI, etc.)

The tool returns detailed match information, including sanctioned entity details, match scores, and source information.

Data Format

Input Schema

The server accepts detailed entity information including:

  • Name
  • Date of birth (for individuals)
  • Gender (for individuals)
  • Citizenship/Nationality
  • Address details
  • Contact information
  • Identification documents

Response Format

The server returns a JSON response with:

  • Match details
  • Match scores
  • Source information
  • Entity profiles

Restart Claude Desktop

After configuring your claude_desktop_config.json, restart Claude Desktop to apply the changes and enable the sanctions screening capability.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.