OpenSanctions MCP. Check any entity against global sanctions lists.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
OpenSanctions screens persons, companies, and maritime vessels against major global compliance databases like OFAC, EU, UN, and UK HMT. It performs mandatory Know Your Customer (KYC) and Anti-Money Laundering (AML) checks by identifying sanctions violations or links to Politically Exposed Persons (PEPs).
You run these complex identity risk assessments directly through your AI client.
What your AI agents can do
Get datasets
Lists all available sanctions datasets, including their descriptions and how many entities they contain.
Get entity
Retrieves full details for a specific entity by ID, pulling names, aliases, addresses, and sanctions status.
Match pep
Screens a name against Politically Exposed Persons (PEP) lists, returning match scores and political positions.
Run targeted checks using match_sanctions and match_pep to determine if a person or company is listed on major sanctions or PEP databases.
Use dedicated tools like search_person, search_company, or search_vessel to quickly narrow down results by entity type and location.
Get a comprehensive profile for one entity using get_entity which pulls aliases, dates of birth, nationalities, and related sources.
Call get_datasets to list all available sanctions datasets, letting you understand the full scope of the compliance data.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
OpenSanctions: 8 Tools for Compliance Data Queries
These tools allow you to perform specific compliance actions: search by type, match against PEP lists, or retrieve full entity records.
019d8467get datasets
Lists all available sanctions datasets, including their descriptions and how many entities they contain.
019d8467get entity
Retrieves full details for a specific entity by ID, pulling names, aliases, addresses, and sanctions status.
019d8467match pep
Screens a name against Politically Exposed Persons (PEP) lists, returning match scores and political positions.
019d8467match sanctions
Uses fuzzy matching to find potential matches against global sanctions lists; adjust sensitivity with the threshold parameter.
019d8467search company
Searches for companies by name, returning their registration numbers, jurisdiction, and current sanctions status.
019d8467search entities
Performs free-text searches across all entity types (Person, Company, Vessel) using fuzzy matching and schema filters.
019d8467search person
Searches for individuals by name, providing aliases, dates of birth, nationalities, and current sanctions status.
019d8467search vessel
Finds ships using names or IMO numbers, returning details on their flag, owners, and sanctions status.
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 OpenSanctions, 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 run complex identity risk assessments directly through your AI client, screening persons, companies, and vessels against major global compliance databases like OFAC, EU, UN, and UK HMT. This server handles mandatory Know Your Customer (KYC) and Anti-Money Laundering (AML) checks by identifying sanctions violations or links to Politically Exposed Persons (PEPs).
To find an entity, you can start broad with search_entities, which performs free-text searches across all types—Person, Company, Vessel—using fuzzy matching and schema filters. Need to narrow it down? You've got dedicated tools for that. Use search_person to look up individuals by name, pulling back their aliases, dates of birth, nationalities, and current sanctions status.
For corporate checks, run search_company, which finds businesses by name, giving you registration numbers, jurisdiction details, and the current sanctions status. If you're tracking maritime assets, use search_vessel to find ships using names or IMO numbers, getting back their flag, owners, and sanctions standing.
When you need deeper verification, you can run targeted checks against major watchlists. To see if a person is linked to political risk, call match_pep; this screens a name specifically against Politically Exposed Persons lists, returning match scores and the individual's political positions. For general sanctions screening, use match_sanctions. This tool uses fuzzy matching to find potential matches across global sanctions lists; you can even fine-tune it by adjusting the sensitivity with the threshold parameter.
To get the full picture on any single hit, run get_entity using a specific ID. This pulls comprehensive details for that entity, including names, aliases, addresses, and their sanctions status. You'll also want to know what data you're working with. Call get_datasets to list every available sanctions dataset, letting you understand the full scope of compliance coverage in the database.
If you need an exact search on a person, search_person provides aliases, DOBs, nationalities, and sanctions status. For companies, search_company returns registration numbers, jurisdiction, and current sanctions status. To locate vessels, search_vessel gives details on the ship's flag, owners, and sanctions status.
How OpenSanctions MCP Works
- 1 Ask your AI client (Claude or Cursor) to screen an entity, specifying if it's a person, company, or vessel.
- 2 The server uses the appropriate tool (
match_sanctions,search_company, etc.) and runs fuzzy matching against its global databases. - 3 You get back structured data containing match scores, specific sanctions lists violated, aliases found, and source datasets.
The bottom line is: you use your AI agent to run complex compliance checks in natural language and get a clean, actionable risk report in return.
Who Is OpenSanctions MCP For?
This server is for anyone whose job involves vetting people or organizations before they can do business. Think Compliance Officers who hate manual spreadsheet cross-referencing, or Financial Analysts who need instant AML/KYC checks on incoming transaction parties.
Uses search_entities and match_sanctions to vet clients and partners against global sanctions lists before onboarding them.
Runs structured checks using get_entity and match_pep on transaction parties to assess political risk and identify potential money laundering links.
Employs dedicated tools like search_vessel to trace the ownership or movement of assets tied to sanctioned regions or individuals.
What Changes When You Connect
- You get instant risk scoring. Instead of manual database lookups,
match_sanctionsreturns a match score (0.0-1.0) showing exactly how close the name is to a known sanction list entry. - It handles multiple entity types. You don't need separate workflows; use
search_entitiesonce and filter results for people, companies, or vessels immediately. - You get complete profiles. Use
get_entitywith a known ID to pull everything—aliases, dates of birth, nationalities, and all linked source datasets in one go. - It keeps you compliant by default. By integrating this server, your agent guarantees that every client check runs against key global lists like OFAC and the EU list.
- You can track physical assets easily. The
search_vesseltool lets you check ships using names or their IMO number, critical for maritime compliance.
Real-World Use Cases
Vetting a new corporate partner
A business development team is onboarding 'GlobalTech Corp'. They ask the agent to run search_company first. If results come back, they immediately use get_entity on the ID to check for aliases and any sanctions flags before signing the contract.
Investigating a suspicious individual
A compliance analyst gets a name: 'Javier Sanchez'. They run search_person. If it's ambiguous, they use match_pep to check for political links. Finally, if the person is linked to a company, they cross-reference that company using search_company.
Tracking suspicious shipping activity
A maritime risk specialist needs to know about a ship called 'The Sea Serpent'. They use search_vessel with the name. The results show an IMO number, which they then pass to get_entity for full ownership and sanctions background.
Discovering available compliance data
A researcher needs to know what datasets exist before running any checks. They simply call the get_datasets tool, which lists all 40+ global regimes and their entity counts for immediate scoping.
The Tradeoffs
Treating every search as unique
Running separate searches: first search_person, then a separate search_company on the same name, leading to fragmented results and missing connections.
→
Start with search_entities. This tool supports free-text searching across all types. If that yields an ID, use get_entity immediately after to pull every piece of associated data into one record.
Ignoring sensitivity settings
Running a generic sanctions check without specifying the threshold parameter in match_sanctions, causing the agent to either miss subtle matches or return too many false positives.
→
Always review the match score. Use the threshold parameter (e.g., 0.75) when calling match_sanctions to tune how sensitive you need the check to be.
Stopping at basic name matches
Finding a company via search_company, but assuming that's all the info is. Missing aliases, ownership links, or date of birth details.
→
Always follow up any initial search with get_entity using the resulting ID. This pulls in the enriched data (aliases, DOB, etc.) needed for a complete profile.
When It Fits, When It Doesn't
Use this server if your workflow requires mandatory KYC/AML checks on an identity—whether that's a person, a corporation, or a vessel. The core need is risk assessment against known global lists (OFAC, EU, UN). Don't use it if you just need to find general public business data; use standard web search tools for that. If you only have vague rumors and no identifying name or ID, the results will be weak. You must first run search_entities to establish a core identifier before running targeted checks like match_sanctions. Never trust an initial search result; always follow up with get_entity to ensure data completeness.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by OpenSanctions. 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 8 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Vetting a single client usually means jumping through five different portals.
Right now, vetting a new partner is manual torture. You start in the corporate registry portal for company names; then you copy that name into a separate compliance database to check sanctions; next, you use another tool just for PEP checks; and finally, if it's a person, you have to get their birthdate from a third source. It’s clicking through five different tabs just to build one picture.
With this MCP server, your agent handles the whole thing. You ask it: 'Is Acme Corp safe?' It runs `search_company`, checks for sanctions using `match_sanctions`, and verifies PEP status with `match_pep`—all in one sequence. You get a single, compiled risk report back.
OpenSanctions MCP Server: Run full compliance profiles.
The biggest time sink is the cross-referencing of identifiers. A name found in `search_entities` might be an alias, and you have to manually check if that alias links to a different entity type or source dataset. This process takes hours of dedicated manual review.
Now, after running any initial search, calling `get_entity` provides the full context immediately. It pulls together all known aliases, DOBs, and sources into one place, letting you move from basic identification straight to deep risk analysis.
Common Questions About OpenSanctions MCP
Do I need an API key? +
No! OpenSanctions is completely free for non-commercial use. No authentication required.
What sanctions lists are included? +
OpenSanctions aggregates data from OFAC (US), EU Consolidated List, UN Security Council, UK HMT, and many other global sanctions regimes.
How accurate is the name matching? +
The API uses fuzzy matching with configurable thresholds (0.0-1.0). Default threshold of 0.85 balances accuracy and recall for most use cases.
Can I screen companies, not just individuals? +
Yes! Use search_company to find sanctioned companies, or use the general search with schema='Company' filter.
What AI clients can use the `search_entities` tool? +
Any MCP-compatible client. You just subscribe to this server and connect your agent. The tool works across Claude, Cursor, or any other compatible platform.
What details does the `get_entity` tool return for a match? +
It returns full entity records by ID. You get names, aliases, dates of birth, nationalities, addresses, and which specific source datasets flagged the entry.
Is OpenSanctions available for commercial screening or are there rate limits when I use `match_sanctions`? +
The service requires no API key for non-commercial use. For high-volume, production workloads, check the Vinkius Marketplace documentation for specific rate limits.
What does running the `get_datasets` tool actually show me? +
It lists every available sanctions dataset. You get the names, descriptions, publisher information, and a count of how many entities are contained within each source.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Kinde (Modern Authentication)
Manage users, organizations, roles, and permissions in Kinde directly from your AI agent.
Aliyun CAPTCHA / 阿里云验证码
Alibaba Cloud's dominant anti-bot service — verify tickets and audit security risk via AI.
StackHawk
Connect your AI to the StackHawk DAST platform. Run automated security scans, triage alerts seamlessly, and find vulnerabilities effortlessly.
You might also like
Quickbase
Build custom business apps with a no-code platform that connects data, automates workflows, and adapts as your needs evolve.
Payload CMS
Manage headless content via Payload CMS — manipulate documents, patch JSON states, retrieve singletons, and structure database endpoints using AI.
Wikidata
Access the world's largest open knowledge graph—query entities via SPARQL, perform vector searches, and manage structured data directly from your AI agent.