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.

OFAC Sanctions Service MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: OFAC Sanctions Service
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to OFAC Sanctions Service through Vinkius, pass the Edge URL in the `mcps` parameter and every OFAC Sanctions Service tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="OFAC Sanctions Service Specialist",
    goal="Help users interact with OFAC Sanctions Service effectively",
    backstory=(
        "You are an expert at leveraging OFAC Sanctions Service tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in OFAC Sanctions Service "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About OFAC Sanctions Service MCP Server

Connect to the OFAC Sanctions List Service (SLS) API through your AI agent and explore authoritative data on sanctioned individuals, groups, and entities using natural conversation.

When paired with CrewAI, OFAC Sanctions Service becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call OFAC Sanctions Service tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

List Discovery — Retrieve identifiers for all available sanctions lists, including the Specially Designated Nationals (SDN) and Consolidated Non-SDN lists.
Update Monitoring — Check the timestamp of the last update for any sanctions list to ensure you are using the most current data.
Version Tracking — List historical and current versions of sanctions lists and retrieve specific version metadata.
Entity Inspection — Access detailed profile information for specific sanctioned entities, including names, aliases, and addresses.
Deltas & Full Versions — Retrieve metadata for full list versions or just the changes (deltas) between specific versions.
Entry Metrics — Get the total count of entities within a specific list version for audit purposes.
Tag Management — List all descriptive tags and labels associated with list versions.

The OFAC Sanctions Service MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect OFAC Sanctions Service to CrewAI via MCP

Follow these steps to integrate the OFAC Sanctions Service MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from OFAC Sanctions Service

Why Use CrewAI with the OFAC Sanctions Service MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with OFAC Sanctions Service through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

OFAC Sanctions Service + CrewAI Use Cases

Practical scenarios where CrewAI combined with the OFAC Sanctions Service MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries OFAC Sanctions Service for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries OFAC Sanctions Service, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain OFAC Sanctions Service tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries OFAC Sanctions Service against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

OFAC Sanctions Service MCP Tools for CrewAI (10)

These 10 tools become available when you connect OFAC Sanctions Service to CrewAI via MCP:

get_delta_version_metadata

Get delta version metadata

get_entity_details

Get specific entity metadata

get_full_version_metadata

Get full version metadata

get_list_last_updated

Check for list updates

get_sls_about

Get SLS API info

get_version_entry_count

Get total entries in a version

list_list_versions

List versions of a sanctions list

list_sanctions_lists

g. SDN, NONSDN). List available sanctions lists

list_version_entities

List entities in a version

list_version_tags

List tags for a version

Example Prompts for OFAC Sanctions Service in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with OFAC Sanctions Service immediately.

"When was the SDN sanctions list last updated?"

"Get the details for entity ID '12345' in the latest SDN version."

"List all historical versions available for the SDN list."

Troubleshooting OFAC Sanctions Service MCP Server with CrewAI

Common issues when connecting OFAC Sanctions Service to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

OFAC Sanctions Service + CrewAI FAQ

Common questions about integrating OFAC Sanctions Service MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.