Cross-Border Sanctions Resolution MCP Server avatar

Cross-Border Sanctions Resolution MCP Server

Pricing

from $50.00 / 1,000 tool calls

Go to Apify Store
Cross-Border Sanctions Resolution MCP Server

Cross-Border Sanctions Resolution MCP Server

Resolve a party name against the US OFAC SDN, EU consolidated and UK OFSI sanctions lists in one MCP call, with the match basis and each list's as-of date.

Pricing

from $50.00 / 1,000 tool calls

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

a day ago

Last modified

Categories

Share

Resolve a party name against the US OFAC SDN, EU consolidated and UK OFSI sanctions lists in one call. Every match states its basis, the list it came from, and that list's as-of date. Built for agents: it is an MCP server, not a scraper.

What it is not

This narrows a search. It is not a sanctions screening determination and does not discharge any screening obligation. Every response says so. There is no fuzzy similarity score, on purpose — a number like 0.87 invites a reader to treat it as a probability, and it is not one. A partial match is flagged requires_human_review: true and left for a human.

Tools

toolwhat it answers
resolve_partyIs this name on any of the three lists, and on what basis?
list_regimesWhich lists are loaded, how many parties each holds, and how fresh each is
get_partyThe full record for one listed party, by the list's own identifier

Sources — public, logged-out, no key

regimesource
US-OFAC-SDNsanctionslistservice.ofac.treas.gov/.../SDN.XML
EU-FSDwebgate.ec.europa.eu/fsd/fsf/public/files/xmlFullSanctionsList_1_1
UK-OFSIofsistorage.blob.core.windows.net/publishlive/2022format/ConList.csv

All three load at start-up and are served from memory, so a tool call answers in milliseconds rather than downloading 70 MB. If a list fails to load, every answer says so: responses carry coverage_complete and regimes_not_searched. A no-match against a partial corpus is never allowed to look like a clean no-match — that is the one failure that would matter most here.

Pricing

EventPrice
Server start (apify-actor-start)$0.05, charged once per server run by the platform
Tool call (mcp-tool-call)$0.05 flat per completed tool call

There are no other events. Errors and notices are not charged: a rejected input, an unloaded list, or an internal failure returns without billing. A sourced, dated no match is charged — it is the answer you asked for.

If a tool call cannot be billed correctly, the call fails rather than serving free. That is deliberate: a billing path that swallows its own errors bills nothing and reports nothing.

Matching

  • exact — the normalised name equals a listed name or alias
  • all-tokens — every meaningful word of your query appears in a listed name (handles word order and corporate suffixes like Ltd / GmbH / OOO)
  • partial — a majority of your words appear; always flagged for human review

Normalisation (accent folding, punctuation, corporate suffixes) is applied identically to the index and to your query, so the two can never disagree.