OFAC SDN Sanctions Screening — Delisted History Check
Pricing
from $0.01 / 1,000 results
OFAC SDN screening that tells FORMERLY_SANCTIONED apart from NO_MATCH. OFAC deletes a delisted party rather than flagging it, so the current SDN.XML answers both identically — this walks OFAC's publication-delta feed and returns the designation date, the removal date and the programmes.
You can access the OFAC SDN Sanctions Screening — Delisted History Check programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in API & Integrations in Apify Console.
{ "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,malekh/ofac-sdn-sanctions-screening-delisted-history" } }}The configuration above connects to the hosted Apify MCP server with the OFAC SDN Screening — Was This Party Ever Sanctioned? Actor already loaded. It uses OAuth, so your client opens a browser window to sign you in to Apify on first use. No API token is needed. Clients without OAuth support can authenticate with an Authorization: Bearer header carrying an API token from API & Integrations in Apify Console.
Get a ready-to-use configuration for your MCP client with the OFAC SDN Screening — Was This Party Ever Sanctioned? Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,malekh/ofac-sdn-sanctions-screening-delisted-history.
You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.