OFAC Sanctions Service MCP. Audit entity profiles and list history from OFAC.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
OFAC Sanctions Service. Connect your AI agent directly to authoritative sanctions data from OFAC. Use this server to track Specially Designated Nationals (SDN) lists, check entity profiles, and monitor version history for compliance auditing.
What your AI agents can do
Get delta version metadata
Gets metadata detailing only the changes (additions/removals) between two versions of a sanctions list.
Get entity details
Retrieves detailed profile information, including known aliases and addresses, for a specific sanctioned entity ID.
Get full version metadata
Gets comprehensive metadata describing the full state of a sanctions list at a given version point.
The agent retrieves identifiers for all sanctions lists managed by OFAC, including SDN and Non-SDN.
You check the timestamp to confirm when any specific sanctions list was last updated.
The agent pulls detailed profile information for a given entity, including known aliases and addresses.
You get metadata showing only the changes—the additions or deletions—between two specific versions of a list.
The system retrieves all structural and version metadata for a specified, complete snapshot of a sanctions list.
You get the total count of entities contained within any given version of a sanctions list for reporting.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
OFAC Sanctions Service MCP Server: 10 Tools for Compliance
Use these tools to perform deep audits of sanctions list versions, track specific entity details, and manage compliance reporting directly through your AI client.
019d75e3get delta version metadata
Gets metadata detailing only the changes (additions/removals) between two versions of a sanctions list.
019d75e3get entity details
Retrieves detailed profile information, including known aliases and addresses, for a specific sanctioned entity ID.
019d75e3get full version metadata
Gets comprehensive metadata describing the full state of a sanctions list at a given version point.
019d75e3get list last updated
Checks and reports the exact timestamp when any specified sanctions list was last updated by OFAC.
019d75e3get sls about
Retrieves basic informational details about the overall Sanctions List Service API itself.
019d75e3get version entry count
Determines and returns the total number of entities present in a specified version of a sanctions list.
019d75e3list list versions
Lists all available historical versions for any given sanctioned list, providing version identifiers.
019d75e3list sanctions lists
Returns a list of all sanctions lists currently maintained by OFAC (e.g., SDN, NONSDN).
019d75e3list version entities
Lists the specific entity IDs that are included within a defined version of a sanctions list.
019d75e3list version tags
Retrieves all descriptive tags and labels associated with a particular historical or current version.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with OFAC Sanctions Service, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You connect your AI agent directly to the OFAC Sanctions List Service (SLS). This server gives you authoritative access to sanctions data, letting your agent check entity profiles and track compliance history against Specially Designated Nationals (SDN) lists.
How It Works
Your agent doesn't just look up names; it handles the full audit trail. First off, if you need to know what OFAC maintains, you can ask the service to list all current sanctions lists, which returns identifiers for everything from SDN to NONSDN.
When you’re checking a specific list, your agent checks when that data last got updated by OFAC using get_list_last_updated, giving you the exact timestamp. For general information about the Sanctions List Service API itself, it pulls basic details via get_sls_about.
Tracking History and Changes
The system keeps meticulous records of every version change. To see what lists are available historically, your agent runs list_list_versions, which returns all available historical versions for any list you specify. If you need to know the scope of a specific version—say, how many entities were on it—you run get_version_entry_count.
You can also get a full breakdown of what's contained in that snapshot by calling list_version_entities.
For structural metadata, your agent retrieves all data for a complete snapshot using get_full_version_metadata, detailing the entire state of the list at one point. If you only care about what changed between two versions, it runs get_delta_version_metadata, which pulls only the additions or deletions—the actual changes—between those specific version points.
To categorize a given version, your agent can pull all associated descriptive tags and labels using list_version_tags.
Deep Entity Inspection
When you have an entity ID, you've got two ways to dig deep. One way is to get detailed profile information—including known aliases and addresses—for that specific sanctioned entity via get_entity_details. If you want to see what lists are active right now, your agent first runs list_sanctions_lists to pull those identifiers.
These tools let your AI client perform complex compliance checks without you ever having to manually download or parse massive files. It's structured data verification, period.
How OFAC Sanctions Service MCP Works
- 1 Subscribe to the OFAC Sanctions Service and provide your required API key.
- 2 (Optional) Pass necessary parameters, like entity IDs or target list names, to your agent client.
- 3 Ask your AI client a question (e.g., 'What changed in the SDN list last week?'). The agent calls the appropriate tool and returns structured data.
The bottom line is that you talk naturally to your agent, and it uses these specific tools to pull verified compliance data from OFAC's API.
Who Is OFAC Sanctions Service MCP For?
Compliance Officers who need continuous visibility into regulatory changes. Legal Counsel needing verifiable proof of due diligence. Risk Analysts required to automate the audit trail and track list versioning. If your job involves checking names against global watchlists, this server is necessary.
Uses list_sanctions_lists to verify if a client belongs on a sanctions list and uses get_sls_about for API status checks.
Monitors specific lists using list_version_tags or checking historical versions with list_list_versions to prove due diligence timelines.
Automates reports by calling get_version_entry_count and comparing list deltas using get_delta_version_metadata for audit purposes.
What Changes When You Connect
- Pinpoint Version Changes: Instead of downloading full files, use
get_delta_version_metadatato see exactly what was added or removed between two versions. This saves massive processing time and bandwidth. - Validate Data Timeliness: Always confirm the data is current by calling
get_list_last_updated. You know immediately if your screening results are based on stale information, which is critical for compliance reports. - Get Comprehensive Entity Profiles: Don't just get a name. Use
get_entity_detailsto pull full metadata—aliases and addresses—giving you the deep context needed for risk scoring. - Audit List Scope: Need to know how big a list was? Call
list_version_entitiesto get the count, or useget_version_entry_countto quantify the total number of records in any version. - Build Audit Trails: Use
list_list_versionsandget_full_version_metadatatogether. This lets you programmatically build a full audit history proving exactly what the list looked like on any given date. - Categorize Risk: Supplement your checks by calling
list_version_tags. You can filter or categorize entities based on descriptive labels applied to specific list versions.
Real-World Use Cases
Due Diligence Audit for a Client Onboarding
A compliance officer needs to prove that the client's name was checked against sanctions lists on three different dates. They ask their agent to first run list_list_versions to find the date range, then use get_delta_version_metadata for two specific versions, and finally runs get_entity_details on a potential match to gather all relevant aliases. The problem is solved with one continuous agent workflow.
Monitoring an Active Sanctions List
A legal team wants to know if the SDN list changed overnight. They run get_list_last_updated first. If it updated, they then call list_version_tags and get_delta_version_metadata to quickly summarize what new risk categories or entities were added, avoiding manual file comparison.
Cross-Referencing Entity Data
A risk analyst has an entity ID but needs to know its full context. They use get_entity_details and then follow up by running list_version_entities to see if that specific ID exists in any current list version, cross-referencing the data points.
Reporting on List Size Over Time
A compliance officer must write a report showing how large a particular watchlist has grown over the last quarter. They iterate through dates using list_list_versions and call get_version_entry_count for each version, generating an accurate size metric without manual data entry.
The Tradeoffs
Assuming a single endpoint exists
Asking the agent to 'Just give me all sanctions info.' This fails because no single function captures version history, entity details, and list discovery simultaneously.
→
You must orchestrate the calls. Start by running list_sanctions_lists to narrow scope, then use list_version_tags or get_full_version_metadata to define your exact parameters.
Only checking the name match
Running only a basic lookup without verifying the list version. You might think an entity is flagged, but it could be based on outdated data.
→
Always check two things: first, use get_list_last_updated to verify freshness; second, always specify the desired version metadata using list_version_tags in your prompt.
Confusing versions and deltas
Asking for 'the changes' without specifying which two versions you are comparing. The API won't know what delta to calculate.
→
You must provide the start and end points. Use list_list_versions to get IDs, then feed those into get_delta_version_metadata.
When It Fits, When It Doesn't
Use this server if your core requirement is auditable compliance data—meaning you need to prove when an entity was flagged and what the list looked like at that exact moment. You must be able to differentiate between a full historical record, a change set (delta), or just the current status.
Don't use this if your task is simple data aggregation (e.g., 'list all people in City X'). For generic data retrieval, an internal database connector might suffice. But because you need OFAC's authority and its deep versioning mechanisms, these 10 tools are necessary. If you only call get_entity_details without checking the list's update time via get_list_last_updated, your result is incomplete.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by OFAC SLS. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually tracking changes to watchlists sucks.
Right now, if a compliance officer needs to prove an entity wasn't on the list last month, they have two options: download huge CSV files from OFAC and manually compare them side-by-side with today’s version. This is slow, error-prone, and requires deep knowledge of spreadsheet formulas just to track simple additions or deletions.
With this MCP server, you ask your agent for the change set. The agent uses `get_delta_version_metadata` and spits out a clean JSON object showing only what changed between Version A and Version B. You get the data structure; you don't get the headache.
The OFAC Sanctions Service MCP Server: Get structured, auditable sanctions data.
Before this server, checking an entity meant jumping between different government portals and relying on manual downloads. If the list updated in the middle of your shift, you might miss it until someone told you. It was a process built for filing cabinets, not digital workflows.
Now, your agent handles the complexity. You call `get_list_last_updated`, confirm the data is fresh, and then use `get_entity_details` to get structured facts—no more guessing games, just verified records.
Common Questions About OFAC Sanctions Service MCP
How do I check if a sanctions list has been updated using get_list_last_updated? +
Call get_list_last_updated and provide the specific list name. The agent returns the precise timestamp of the last modification, letting you know instantly if your data is stale or current.
What's the difference between get_delta_version_metadata and get_full_version_metadata? +
get_delta_version_metadata returns only the changes (the additions/deletions). get_full_version_metadata gives you the complete, structural blueprint of the list exactly as it existed at that specific version.
How can I find out what lists are available to screen? +
Use the list_sanctions_lists tool. It returns a definitive catalog of all sanctions lists maintained by OFAC, so you know exactly which list identifiers to use.
I need to check an entity's profile—which tool should I use? +
Use get_entity_details. This tool pulls detailed profile information for a given ID, including aliases and addresses. It’s the right place to go once you have a suspect ID.
Does this server help with compliance reporting? +
Yes. You can use get_version_entry_count combined with version listing tools (list_list_versions) to automatically generate metrics on list size and scope for reports.
When I run `get_sls_about`, what kind of general API information can I expect? +
The tool provides foundational details about the OFAC Sanctions List Service (SLS) API itself. This info is critical for understanding the service's scope and connectivity requirements before running any specific screening checks.
Using `get_version_entry_count`, how do I compare the total number of entities across two different versions? +
You run this tool twice—once for each version ID you want to check. The output gives a precise count, letting you immediately see which list grew or shrank between those specific historical dates.
If I use `list_version_tags`, what kind of descriptive labels can I pull from a sanctions list version? +
This tool lists all available tags and associated metadata for a given version. You can use these labels to filter or categorize the data, which is useful when compiling reports based on specific criteria.
Is the OFAC SLS API Key required? +
No. The SLS API is publicly accessible. However, providing an API key if you have one ensures higher rate limits and consistent access.
What is the difference between SDN and Non-SDN lists? +
The SDN (Specially Designated Nationals) list contains individuals and entities whose assets are blocked. Non-SDN lists contain entities subject to other sanctions, such as sector-specific or prohibited accounts.
Can I see aliases for a specific person? +
Yes! Use the get_entity_details tool with the specific Entity ID. The agent will return the full profile, including all known aliases, addresses, and identifying information.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
PubChem
Search 116M+ chemical compounds with molecular properties, SMILES notation, formulas, and drug-like properties from the world's largest free chemistry database.
Farmonaut
Access satellite agriculture data via Farmonaut — monitor crop health with NDVI, weather, soil moisture, crop advisory, and deforestation alerts from any AI agent.
Bureau of Labor Statistics Full — The Mega Server
The ultimate BLS Mega-Server: Access all 6 major datasets including CPI (Inflation), CES (Jobs), CPS (Unemployment), JOLTS (Turnover), LAUS (Local metrics), and OEWS (Wages by Profession).
You might also like
GetBlock (Web3 RPC Provider)
Access 50+ blockchain networks (Ethereum, Solana, Bitcoin) via RPC. Query balances, blocks, and transactions directly from your AI agent.
UserStack User-Agent Lookup
Universal User-Agent intelligence — detect devices, browsers, and OS via AI.
Text In Church
Keep your congregation engaged with church-specific texting, email, and communication tools that grow attendance and giving.