# OFAC Sanctions Service MCP

> The OFAC Sanctions Service MCP connects your AI agent directly to the authoritative sanctions data published by OFAC. You can verify if individuals, groups, or entities appear on major lists like the SDN list, check historical versions of these records, and track when the underlying compliance data was last updated. It gives you deep, traceable insights into global financial risk.

## Overview
- **Category:** the-unthinkable
- **Price:** Free
- **Tags:** sanctions-screening, risk-management, regulatory-compliance, aml-checks, data-verification, watch-list

## Description

Need to know if a client or counterparty is sanctioned? This MCP lets your AI agent query the official OFAC Sanctions List Service (SLS) directly from within your workflow. Instead of downloading massive CSVs and manually cross-referencing data sheets, you ask your agent natural language questions about sanctions lists.

For example, you can list all available sanctions registries to know what data sets exist. You can also check the current status by calling `get_list_last_updated` to confirm that the information you're using is genuinely up-to-date. If compliance requires historical checks, the MCP allows deep diving into versions, letting you track both the full list metadata and only the specific changes (deltas) between versions.

This level of structured access makes manual audits faster. By connecting this service through Vinkius, your agent can handle complex data tasks—from getting total entity counts within a version to accessing detailed profiles for any specific sanctioned party. It turns what used to be a massive administrative chore into a simple conversational query.

## Tools

### get_sls_about
Retrieves general information about the OFAC Sanctions List Service API.

### get_delta_version_metadata
Gets metadata detailing only the changes (deltas) between two specific versions of a list.

### get_entity_details
Accesses detailed profile information for any specific sanctioned entity ID.

### get_version_entry_count
Returns the total number of entities present in a specified version of a sanctions list.

### get_full_version_metadata
Retrieves complete metadata for an entire, specific version of a sanctions list.

### get_list_last_updated
Checks the exact date and time that any given sanctions list was last updated by OFAC.

### list_version_entities
Lists all entity identifiers contained within a specific version of a sanctions list.

### list_sanctions_lists
Provides a catalog of all available sanctioned lists, such as SDN or NONSDN.

### list_version_tags
Fetches descriptive tags and labels applied to a specific sanctions list version.

### list_list_versions
Lists all available historical versions for any given sanctions list.

## Prompt Examples

**Prompt:** 
```
When was the SDN sanctions list last updated?
```

**Response:** 
```
Checking update status... The SDN sanctions list was last updated today at 10:15 AM UTC. Would you like to see the entry count for the latest version?
```

**Prompt:** 
```
Get the details for entity ID '12345' in the latest SDN version.
```

**Response:** 
```
Inspecting entity 12345... This record belongs to 'Example Global Group'. It has 3 known aliases and is associated with 2 addresses in Zurich. Shall I retrieve the full version metadata for this list?
```

**Prompt:** 
```
List all historical versions available for the SDN list.
```

**Response:** 
```
Retrieving version history... I found 12 historical versions for the SDN list, ranging from January 2023 to the current version published today. Would you like to check the delta (changes) between the last two versions?
```

## Capabilities

### Verify Entity Status
Fetch detailed profile information on specific entities, including known aliases and addresses.

### Check List Currency
Determine the exact timestamp of when any sanctions list was last updated by OFAC.

### Audit List Scope
Retrieve a full catalog of all available sanctions lists, such as SDN or NONSDN.

### Track Data History
View the version history and metadata for any given sanctions list, including specific changes between versions.

### Count Records
Get an exact total count of entities contained within a specific version of a sanctions list for reporting purposes.

## Use Cases

### Screening a New Client Against Multiple Lists
A risk analyst needs to know if a client is flagged by OFAC. They ask their agent to call `list_sanctions_lists` first, then use the result to check for details using `get_entity_details`, providing a comprehensive and immediate risk report.

### Preparing Quarterly Regulatory Reports
A compliance officer must prove that their checks are always based on current data. They use `get_list_last_updated` to document the exact time of the last official update for audit purposes, satisfying regulatory demands.

### Investigating a Historical Sanction Change
A legal team needs to know exactly when an entity's status changed. They use `list_list_versions` and then `get_delta_version_metadata` to isolate the precise changes, rather than reviewing entire list versions.

### Building a Data Validation Pipeline
A risk analyst needs to confirm that their dataset matches an official version. They use `list_version_entities` and then `get_version_entry_count` to validate the scope against the authoritative source.

## Benefits

- Stop wasting time manually checking if a list is current. Use `get_list_last_updated` to get the precise timestamp of the latest OFAC update, ensuring your compliance checks rely on fresh data.
- Don't just check for existence; understand *why* an entity is flagged. With `get_entity_details`, you pull detailed profiles including aliases and addresses in one go.
- Audit risk over time by listing all historical versions using `list_list_versions`. You can then track specific changes between two points in time with `get_delta_version_metadata`.
- Need a quick count for reporting? Instead of manually counting lines, use `get_version_entry_count` to get the exact total number of entities contained within any list version.
- Quickly understand your compliance scope by calling `list_sanctions_lists` to see every available registry, eliminating guesswork about which lists you need to check.

## How It Works

The bottom line is, you get real-time access to authoritative compliance data without ever leaving your chat window.

1. Subscribe to the OFAC Sanctions Service MCP and provide your API key, if required.
2. Connect this MCP to your preferred AI client (Claude, Cursor, etc.) in Vinkius.
3. Tell your agent exactly what you need—for instance, 'What are all the available sanctions lists?' or 'Check the entry count for version X'.

## Frequently Asked Questions

**How do I check if an entity is on any sanctions list using the OFAC Sanctions Service MCP?**
You use `list_sanctions_lists` to see all available lists, then provide a name or ID. The agent handles the full screening process across the appropriate registries.

**What is the difference between full and delta metadata using OFAC Sanctions Service MCP?**
Full version metadata (`get_full_version_metadata`) provides everything in a list for that date. Delta metadata (`get_delta_version_metadata`) only shows what changed since the previous official release, saving you time.

**Can I find out when the SDN sanctions list was last updated with OFAC Sanctions Service MCP?**
Yes, calling `get_list_last_updated` provides the exact date and time the specific sanctioned list was modified by OFAC.

**How do I list all historical versions using this MCP?**
Use the `list_list_versions` tool. This gives you a catalog of every archived version, allowing you to pick and choose which date range you need for your audit.

**Is the data from OFAC Sanctions Service MCP real-time?**
The data reflects the most current versions published by OFAC. Always confirm currency using `get_list_last_updated` to ensure you're working with the latest official release.