OFAC Sanctions Screening — Fuzzy SDN List Matching

Name: OFAC Sanctions Screening — Fuzzy SDN List Matching
Author: easysolutions906

@easysolutions906

About OFAC Sanctions Screening — Fuzzy SDN List Matching

Screen names against the US Treasury OFAC SDN list with advanced fuzzy matching. 18,700+ sanctioned entities. Jaro-Winkler, phonetic, and token-set algorithms. Essential for KYC/AML compliance.

#ofac #sanctions #compliance #aml #kyc #screening #mcp

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "ofac": {
      "command": "npx",
      "args": [
        "-y",
        "@easysolutions906/mcp-ofac"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is OFAC Sanctions Screening — Fuzzy SDN List Matching?

An MCP server for screening names against the US Treasury OFAC SDN (Specially Designated Nationals) list using production-grade fuzzy matching. It combines Jaro-Winkler, phonetic, token-set, and exact substring algorithms. Designed for any company processing USD transactions that needs regulatory compliance without the cost of enterprise screening tools.

How to use OFAC Sanctions Screening — Fuzzy SDN List Matching?

Install globally via npx @easysolutions906/mcp-ofac. For Claude Desktop or Cursor, add the MCP server configuration with the same npx command. Once running, use the five built-in tools (ofac_screen, ofac_screen_batch, ofac_entity, ofac_search, ofac_stats) to screen names, get entity details, search the list, or view statistics. Optionally set the PORT environment variable to run as an HTTP server with REST endpoints.

Key features of OFAC Sanctions Screening — Fuzzy SDN List Matching

Fuzzy matching pipeline with Jaro-Winkler, token-set, and Double Metaphone
Screens against 18,712 SDN entries across 73 sanctions programs
Supports single name screening and batch screening of up to 100 names
Each result includes confidence score, match type, and detailed breakdown
Built-in audit trail with list version and timestamp for compliance
Free tier available; paid plans from $4.99/month

Use cases of OFAC Sanctions Screening — Fuzzy SDN List Matching

Screening customer names during onboarding against the OFAC SDN list
Batch verifying existing customer databases for sanctions compliance
Investigating entity details, aliases, and sanctions programs by SDN UID
Searching the SDN list by keyword, entity type, or sanctions program
Generating compliance audit trails with data freshness and timestamps

FAQ from OFAC Sanctions Screening — Fuzzy SDN List Matching

How does this compare to enterprise sanctions screening tools?

Enterprise tools cost $10,000–100,000/year; this server offers the same capability at a fraction of the cost, with matching algorithms and compliance documentation built in.

What runtime dependencies are needed?

Requires Node.js to run via npx. No other runtime dependencies are mentioned in the README.

Where does the sanctions data live?

The data is bundled with the package (18,712 entries as of 03/13/2026). You can rebuild it from the latest OFAC feed using npm run build-data.

What are the usage limits?

Free plan: 10 screens/day, 5 per batch, 5 requests/min. Paid plans range from 100 to 50,000 screens/day with higher rate limits.

What transport options are supported?

Default is stdio (for Claude Desktop, Cursor). Set the PORT environment variable to enable Streamable HTTP mode on the /mcp endpoint. REST API endpoints are also available separately.