OFAC (Sanções EUA) vs Compliance & Sanções

In-depth architectural comparison of the OFAC (Sanções EUA) and Compliance & Sanções MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose OFAC (Sanções EUA) when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore OFAC (Sanções EUA) Details

Choose Compliance & Sanções when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Compliance & Sanções Details

Feature & Specification Comparison

Specification	OFAC (Sanções EUA) Developer Tools	Compliance & Sanções Developer Tools
Summary	Checks whether a name is on OFAC (US) sanctions lists, including SDN and Non-SDN, for compliance and	Due diligence & KYC: PEP, national and international sanctions (OFAC, UN, EU, UK, FBI, INTERPOL, FIN
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "ofac-san-es-eua": {
      "command": "npx",
      "args": [
        "-y",
        "ofac-san-es-eua"
      ]
    }
  }
}

{
  "mcpServers": {
    "compliance-san-es": {
      "command": "npx",
      "args": [
        "-y",
        "compliance-san-es"
      ]
    }
  }
}

Related MCP Server Comparisons