OpenSanctions MCP Server for AutoGen 8 tools — connect in under 2 minutes
Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add OpenSanctions as an MCP tool provider through the Vinkius and every agent in the group can access live data and take action.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench
async def main():
# Your Vinkius token — get it at cloud.vinkius.com
async with McpWorkbench(
server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
transport="streamable_http",
) as workbench:
tools = await workbench.list_tools()
agent = AssistantAgent(
name="opensanctions_agent",
tools=tools,
system_message=(
"You help users with OpenSanctions. "
"8 tools available."
),
)
print(f"Agent ready with {len(tools)} tools")
asyncio.run(main())
* 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 OpenSanctions MCP Server
Connect to OpenSanctions and access the world's largest open sanctions and PEP screening database through natural conversation — no API key needed for non-commercial use.
AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use OpenSanctions tools. Connect 8 tools through the Vinkius and assign role-based access — a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.
What you can do
- Entity Search — Search for sanctioned persons, companies and vessels by name
- Sanctions Screening — Screen names against global sanctions lists (OFAC, EU, UN, UK HMT)
- PEP Screening — Screen persons against Politically Exposed Persons databases
- Entity Details — Get full entity info including aliases, dates of birth, nationalities and addresses
- Vessel Search — Search sanctioned vessels by name or IMO number
- Dataset Browser — Browse all available sanctions datasets worldwide
The OpenSanctions MCP Server exposes 8 tools through the Vinkius. Connect it to AutoGen 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 OpenSanctions to AutoGen via MCP
Follow these steps to integrate the OpenSanctions MCP Server with AutoGen.
Install AutoGen
Run pip install "autogen-ext[mcp]"
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token
Integrate into workflow
Use the agent in your AutoGen multi-agent orchestration
Explore tools
The workbench discovers 8 tools from OpenSanctions automatically
Why Use AutoGen with the OpenSanctions MCP Server
AutoGen provides unique advantages when paired with OpenSanctions through the Model Context Protocol.
Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use OpenSanctions tools to solve complex tasks
Role-based architecture lets you assign OpenSanctions tool access to specific agents — a data analyst queries while a reviewer validates
Human-in-the-loop support: agents can pause for human approval before executing sensitive OpenSanctions tool calls
Code execution sandbox: AutoGen agents can write and run code that processes OpenSanctions tool responses in an isolated environment
OpenSanctions + AutoGen Use Cases
Practical scenarios where AutoGen combined with the OpenSanctions MCP Server delivers measurable value.
Collaborative analysis: one agent queries OpenSanctions while another validates results and a third generates the final report
Automated review pipelines: a researcher agent fetches data from OpenSanctions, a critic agent evaluates quality, and a writer produces the output
Interactive planning: agents negotiate task allocation using OpenSanctions data to make informed decisions about resource distribution
Code generation with live data: an AutoGen coder agent writes scripts that process OpenSanctions responses in a sandboxed execution environment
OpenSanctions MCP Tools for AutoGen (8)
These 8 tools become available when you connect OpenSanctions to AutoGen via MCP:
get_datasets
Returns dataset names, descriptions, publisher info and entity counts. Get list of all sanctions datasets available
get_entity
Returns full entity details including names, aliases, dates of birth, nationalities, addresses, sanctions details, related entities and source datasets. Get detailed info for a specific entity by ID
match_pep
Returns match scores, matched entities, political positions and source datasets. Useful for KYC/AML compliance checks. Screen a name against Politically Exposed Persons (PEP) lists
match_sanctions
Uses fuzzy matching to find potential matches. Returns match scores, matched entities and sanction details. Use threshold parameter (0.0-1.0) to adjust sensitivity. Default 0.85. Screen a name against global sanctions lists
search_company
Returns company names, registration numbers, jurisdictions, addresses and sanctions status. Search for companies in the sanctions database
search_entities
Supports free-text search with fuzzy matching. Returns entity names, types (Person, Company, Vessel), countries and dataset sources. Use schema parameter to filter by entity type (Person, Company, Vessel, etc.). Search sanctions and PEP entities by name
search_person
Returns person names, aliases, dates of birth, nationalities, countries and sanctions status. Search for persons in the sanctions database
search_vessel
Returns vessel names, IMO numbers, flags, owners and sanctions status. Search for vessels (ships) in the sanctions database
Example Prompts for OpenSanctions in AutoGen
Ready-to-use prompts you can give your AutoGen agent to start working with OpenSanctions immediately.
"Screen 'Vladimir Putin' against sanctions lists."
"Search for companies sanctioned in Russia."
"What sanctions datasets are available?"
Troubleshooting OpenSanctions MCP Server with AutoGen
Common issues when connecting OpenSanctions to AutoGen through the Vinkius, and how to resolve them.
McpWorkbench not found
pip install "autogen-ext[mcp]"OpenSanctions + AutoGen FAQ
Common questions about integrating OpenSanctions MCP Server with AutoGen.
How does AutoGen connect to MCP servers?
Can different agents have different MCP tool access?
Does AutoGen support human approval for tool calls?
Connect OpenSanctions with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect OpenSanctions to AutoGen
Get your token, paste the configuration, and start using 8 tools in under 2 minutes. No API key management needed.