Sanctions MCP server
{
"mcpServers": {
"ares": {
"type": "http",
"url": "https://realestate.cz-agents.dev/mcp"
}
}
}{
"mcpServers": {
"ares": {
"type": "http",
"url": "https://realestate.cz-agents.dev/mcp"
}
}
}{
"mcpServers": {
"ares": {
"type": "http",
"url": "https://realestate.cz-agents.dev/mcp"
}
}
}{
"servers": {
"ares": {
"type": "http",
"url": "https://realestate.cz-agents.dev/mcp"
}
}
}{
"mcpServers": {
"ares": {
"type": "http",
"url": "https://realestate.cz-agents.dev/mcp"
}
}
}What it does
This server screens Czech companies and individuals against EU and OFAC sanctions lists for KYC/AML compliance. It exposes sanctions database queries and risk assessment tools, primarily for compliance teams, financial institutions, and businesses conducting due diligence on trading partners.
- Screen a company or individual name against EU FSF and OFAC SDN sanctions lists during customer onboarding.
- Check whether a Czech business partner appears on any active sanctions watchlists before entering a contract.
- Integrate sanctions screening into an automated KYC/AML workflow for transaction monitoring.
Tools this server exposes
| Tool | Does |
|---|---|
| screen_sanctions | Searches a name or company identifier against EU and OFAC sanctions lists. |
| check_sanctions_status | Returns sanctions match results with risk level for a given entity. |
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.