OFAC SDN Screening

What the OFAC SDN Screening MCP server does

The OFAC SDN Screening MCP server checks a provided name against the U.S. Treasury OFAC SDN list. It is intended for workflows that need an initial sanctions-list check, such as reviewing a person or organization name before a later manual or compliance-led assessment.

The available description establishes one core purpose: name screening against the OFAC SDN list. It does not document additional data sources, broader sanctions lists, entity-resolution features, batch processing, or a particular matching method. Applications should therefore treat the server as a focused OFAC SDN screening capability rather than as a complete sanctions-compliance system.

How it works

An MCP client submits a name for screening, and the OFAC SDN Screening MCP server checks that name against the specified U.S. Treasury list. The result is information for the calling workflow to review. The supplied material does not define the response schema, matching thresholds, handling of aliases, treatment of punctuation or spelling variations, or whether the service returns source records and confidence information.

Because the screening result is informational, downstream software or reviewers must decide how to interpret it and what additional checks are appropriate. A result from the OFAC SDN Screening MCP server should not, by itself, be presented as a final compliance determination. The listing specifically distinguishes screening information from a compliance decision.

Limitations and notes

The OFAC SDN Screening MCP server is scoped to the U.S. Treasury OFAC SDN list described in the listing. No support is documented for other OFAC lists, non-U.S. sanctions programs, watchlists, customer records, or identity-verification data. The available material also does not state how current the underlying list is, how updates are delivered, or whether screening is performed locally or through a remote service.

Installation instructions, required environment variables, supported MCP clients, authentication requirements, licensing, and transport details are not provided in the available material. Confirm those details in the project documentation before deployment. In particular, do not assume that an informational name-screening result satisfies an organization's legal, regulatory, or internal compliance process. Use the server for the documented check, then apply the organization's own review procedures and controls.