Sanctions Screening vs Sanctions Screening MCP Server

In-depth architectural comparison of the Sanctions Screening and Sanctions Screening MCP Server 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?

S

Choose Sanctions Screening 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).
• Primary tools included: sanctions_screen, sanctions_entry, sanctions_lists.

Explore Sanctions Screening Details

Choose Sanctions Screening MCP Server 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 Sanctions Screening MCP Server Details

Feature & Specification Comparison

Specification	S Sanctions Screening Developer Tools	Sanctions Screening MCP Server Developer Tools
Summary	Screen names against the US Consolidated Screening List: OFAC SDN, BIS Entity List +10 more lists	Screen names against OFAC, EU, UK, UN sanctions lists; resolve entities via GLEIF. Screening aid.
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": {
    "sanctions-screening-3": {
      "command": "npx",
      "args": [
        "-y",
        "sanctions-screening-3"
      ]
    }
  }
}

{
  "mcpServers": {
    "sanctions-screening-mcp-server": {
      "command": "bunx",
      "args": [
        "@cyanheads/sanctions-screening-mcp-server@latest"
      ]
    }
  }
}

Related MCP Server Comparisons