MCPSERV.CLUB
madupay

Sanctions MCP Server

MCP Server

Real‑time sanctions screening via OFAC and global lists

Stale(50)
2stars
2views
Updated Sep 22, 2025

About

The Sanctions MCP Server offers a Node.js API for instant compliance checks, screening individuals and organizations against OFAC SDN, UN, OFSI, and other major sanctions lists. It supports customizable risk thresholds and multiple identifiers for precise risk assessment.

Capabilities

Resources
Access data sources
Tools
Execute functions
Prompts
Pre-built templates
Sampling
AI model interactions

Sanctions MCP Server Demo

The Sanctions MCP Server brings robust sanctions screening capabilities directly into AI‑driven workflows. By wrapping the OFAC API, it offers a unified interface for querying major global sanctions lists—including OFAC SDN, UN, and OFSI—through the Model Context Protocol. This eliminates the need for developers to write custom integrations against each list, allowing Claude and other AI assistants to perform compliance checks with a single API call.

At its core, the server accepts detailed entity data—whether an individual or an organization—and returns a structured response that includes match details, risk scores, and the originating sanctions source. Developers can fine‑tune the screening by setting a minimum risk threshold and selecting which lists to query, ensuring that only relevant matches surface. This flexibility is especially valuable in regulated industries where compliance teams must balance thoroughness against operational efficiency.

Key capabilities include:

  • Multi‑entity support: Screen both people and companies with the same endpoint.
  • Rich identification options: Names, addresses, passports, nationalities, and other identifiers can be supplied.
  • Custom risk thresholds: Adjust the sensitivity of matches to match internal policy.
  • Source filtering: Choose from SDN, NONSDN, DPL, UN, OFSI, and more to align with jurisdictional requirements.

Real‑world use cases span from onboarding new clients—verifying that a prospective customer is not on any sanctions list—to monitoring third‑party vendors and conducting periodic risk reviews. By integrating this server into an AI assistant’s toolset, teams can query sanctions status in natural language (“Is Tech Solutions Ltd in Tehran sanctioned?”) and receive actionable, context‑rich responses without leaving the conversational interface.

The MCP design ensures seamless integration into existing AI workflows. Once configured, Claude can invoke the sanctions tool as a first‑class resource, receiving structured JSON that developers can further process or embed in dashboards. The server’s lightweight Node.js implementation keeps latency low, making real‑time compliance checks feasible even in high‑volume environments. Overall, the Sanctions MCP Server provides a powerful, flexible, and developer‑friendly bridge between AI assistants and global sanctions data.