# OpenSanctions MCP

> OpenSanctions connects your agent to a massive, global database of sanctions and Politically Exposed Persons (PEP) lists. Use this MCP to check names, companies, and vessels against major international watchlists like OFAC, EU, and UN. It's essential for any process requiring Know Your Customer (KYC) or Anti-Money Laundering (AML) compliance.

## Overview
- **Category:** security-compliance
- **Price:** Free
- **Tags:** sanctions-screening, pep-screening, aml, kyc, risk-management, compliance

## Description

When you need to know if a client, partner, or transaction is flagged by global regulators, OpenSanctions provides the answers. This MCP lets your agent query the world's largest collection of sanctions and PEP data through simple conversation—no API keys are required for non-commercial use.

It handles everything from searching individual names against Politically Exposed Persons lists to screening entire companies or vessels. You can get detailed profiles, including aliases, dates of birth, and full ownership structures. If your current workflow involves manually cross-referencing multiple government watchlists, this MCP cuts out all the friction. Simply connect it through Vinkius and let your agent do the heavy lifting. It aggregates data from major global regimes like OFAC, EU, and UN into one place, giving you a clear compliance picture instantly.

## Tools

### get_datasets
Lists all available sanctions data sets, showing dataset names, publishers, and the total number of entities contained in each.

### get_entity
Retrieves comprehensive details for a single entity using its unique ID, including aliases, addresses, and related datasets.

### match_pep
Screens an individual's name against Politically Exposed Persons (PEP) lists to check for political ties.

### match_sanctions
Runs fuzzy matching on a name to find potential matches in global sanctions databases, returning a sensitivity score.

### search_company
Searches the database specifically for companies, providing their registration numbers, jurisdiction, and current sanctions status.

### search_entities
Performs a flexible search across all entity types (Person, Company, Vessel) using free-text queries and fuzzy matching.

### search_person
Finds personal profiles by name, returning aliases, dates of birth, nationalities, and sanctions status for individuals.

### search_vessel
Searches for ships using names or IMO numbers, providing details on flags, owners, and any sanction hits.

## Prompt Examples

**Prompt:** 
```
Screen 'Vladimir Putin' against sanctions lists.
```

**Response:** 
```
Found multiple matches for Vladimir Putin in OFAC, EU and UK sanctions lists. Includes aliases, dates of birth, nationalities and sanctions details.
```

**Prompt:** 
```
Search for companies sanctioned in Russia.
```

**Response:** 
```
Found 50+ sanctioned companies with Russian connections. Includes Gazprom, Rosneft, Sberbank and many others across OFAC, EU and UK sanctions lists.
```

**Prompt:** 
```
What sanctions datasets are available?
```

**Response:** 
```
Available datasets: US OFAC (9,000+ entities), EU Consolidated List (6,000+), UN Security Council (700+), UK HMT (3,000+), and 40+ more global sanctions regimes.
```

## Capabilities

### Screening People
Checks individuals against sanctions lists and Politically Exposed Persons databases to flag potential risks.

### Investigating Companies
Searches for corporate entities, verifying registration details and checking their current sanction status.

### Checking Vessels
Retrieves detailed records on ships, including IMO numbers, owners, and any associated sanctions.

### Gathering Data Sets
Lists all available global sanctions datasets so you know exactly what information is being checked against.

## Use Cases

### Onboarding a new corporate client
A compliance officer needs to vet a potential partner. Instead of running three separate manual checks (company name, key executives' names, and jurisdiction), the agent uses `search_company` and then runs multiple individual screens using `search_person` and `match_sanctions`. It compiles all findings into one risk report.

### Investigating suspicious transactions
A financial analyst detects a shipment that might be flagged. They use `search_vessel` with the ship's name or IMO number to check ownership and sanctions status, confirming if the vessel is connected to any restricted parties.

### Auditing client portfolios
A risk manager needs to review 100 clients. They use `search_entities` with a schema filter for 'Person' and then iterate through them, running `match_pep` on each name to ensure no politically exposed individuals are involved.

### Understanding data scope
A researcher needs to know what compliance databases are available. They simply call `get_datasets`, which immediately provides a list of all global sanctions regimes and how many entities each database holds.

## Benefits

- Deep compliance checks: Instantly run `match_sanctions` or `match_pep` to check any name against OFAC, EU, and UN lists. You get a match score, not just a yes/no answer.
- Comprehensive entity views: Don't just search by name; use `search_entities` to filter results by type (Person, Company, Vessel) or country for precision.
- Know your data sources: The `get_datasets` tool lets you see exactly which sanctions regimes are available, giving you confidence in the compliance depth of the check.
- Full company profiles: Instead of basic searches, use `search_company` to get full details on a corporate entity, including registration numbers and sanctioned status.
- Vessel tracking: For maritime risk, run `search_vessel` with an IMO number. This is critical for understanding trade flow risks and sanctions violations.

## How It Works

The bottom line is that you talk naturally to your agent, and it handles the complex database queries for compliance checks.

1. Subscribe to the OpenSanctions MCP catalog.
2. Connect your preferred AI client (Claude, Cursor, etc.) through Vinkius.
3. Ask your agent to screen a name or entity against specific sanctions lists.

## Frequently Asked Questions

**Does OpenSanctions help with KYC/AML compliance?**
Yes, absolutely. The MCP is designed specifically for KYC and AML checks by screening identities against major global sanctions lists and PEP databases.

**Can I search for people using OpenSanctions MCP?**
You can use `search_person` to find individuals by name, or run a targeted check with `match_sanctions` to see if they are listed on sanctions lists.

**What is the difference between `search_entities` and `get_entity`?**
`search_entities` lets you look for potential matches using free text. `get_entity`, however, requires a specific ID to pull comprehensive details on an already identified entity.

**Does OpenSanctions require me to pay per API call?**
No, the MCP is available without needing an API key for non-commercial use. You just connect through Vinkius and start screening with your agent.

**Can I check vessels using OpenSanctions MCP?**
Yes, you can run `search_vessel` to look up ships by name or IMO number, checking them against sanctions databases for maritime risk management.