# Cross-Border Sanctions Resolution MCP Server (`nexgenwatch/cross-border-sanctions-resolution-mcp`) Actor

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.

- **URL**: https://apify.com/nexgenwatch/cross-border-sanctions-resolution-mcp.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Agents, Business
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 tool calls

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Cross-Border Sanctions Resolution MCP Server

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

| tool | what it answers |
|---|---|
| `resolve_party` | Is this name on any of the three lists, and on what basis? |
| `list_regimes` | Which lists are loaded, how many parties each holds, and how fresh each is |
| `get_party` | The full record for one listed party, by the list's own identifier |

### Sources — public, logged-out, no key

| regime | source |
|---|---|
| `US-OFAC-SDN` | `sanctionslistservice.ofac.treas.gov/.../SDN.XML` |
| `EU-FSD` | `webgate.ec.europa.eu/fsd/fsf/public/files/xmlFullSanctionsList_1_1` |
| `UK-OFSI` | `ofsistorage.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

| Event | Price |
|---|---|
| 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.

# Actor input Schema

## `note` (type: `string`):

This Actor runs as an MCP server in Standby mode. Connect an MCP client to the server URL with path /mcp; there is no batch input to fill in.

## Actor input object example

```json
{
  "note": "standby"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "note": "standby"
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/cross-border-sanctions-resolution-mcp").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "note": "standby" }

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/cross-border-sanctions-resolution-mcp").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "note": "standby"
}' |
apify call nexgenwatch/cross-border-sanctions-resolution-mcp --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/cross-border-sanctions-resolution-mcp"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/eNuDGsUZC8wgFgfI3/builds/qeMjKidvzUjaeRkG9/openapi.json