What is the key difference between OFACScreen Sanctions Screening and Sanctions Screening?

OFACScreen Sanctions Screening belongs to the Developer Tools category with local stdio execution, while Sanctions Screening belongs to the Developer Tools category with local stdio execution.

How do I install OFACScreen Sanctions Screening or Sanctions Screening in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Which MCP server has more tools and community activity?

OFACScreen Sanctions Screening lists 0 tools with 0 views and 0 GitHub stars. Sanctions Screening lists 3 tools with 0 views and 0 GitHub stars.

Can I use both OFACScreen Sanctions Screening and Sanctions Screening together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

OFACScreen Sanctions Screening vs Sanctions Screening

Q: Are OFACScreen Sanctions Screening and Sanctions Screening free or paid?

OFACScreen Sanctions Screening operates under a Free / Open Source model (No auth required). Sanctions Screening operates under a Free / Open Source model (No auth required).

In-depth architectural comparison of the OFACScreen Sanctions Screening and Sanctions Screening 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.

At a Glance & Executive Verdict

OFACScreen Sanctions Screening

Developer Tools · Local stdio

Quality: 37/100 (Fair) | Auth: No auth required

Sanctions Screening

Developer Tools · Local stdio

Quality: 45/100 (Fair) | Auth: No auth required

Verdict Summary: Choose OFACScreen Sanctions Screening if you need specialized Developer Tools tools running via a local process. Choose Sanctions Screening if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose OFACScreen 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).

Explore OFACScreen Sanctions Screening Details

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

Feature & Specification Comparison

Specification	O OFACScreen Sanctions Screening Developer Tools	S Sanctions Screening Developer Tools
Summary	Screen names against OFAC SDN and 7 more global sanctions lists. Free, no account required.	Screen names against the US Consolidated Screening List: OFAC SDN, BIS Entity List +10 more lists
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

OFACScreen Sanctions Screening Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Sanctions Screening Tools (3)

sanctions_screen

Screen a person, company, vessel, or aircraft name against the US Consolidated Screening List — OFAC SDN sanctions, Sectoral Sanctions (SSI), Chinese Military-Industrial Complex (CMIC), BIS Entity List / Denied Persons / Military End User, State ITAR Debarred, and 5 more US restricted-party lists (…

sanctions_entry

Get the full Consolidated Screening List record for one entry by its uid (from sanctions_screen results, e.g. "SDN:12345") or by OFAC entity number. Returns every field: all aliases, addresses, identity documents (passports, tax IDs, IMO numbers, crypto wallet addresses), sanction programs, license…

sanctions_lists

List the 12 US restricted-party lists covered by the Consolidated Screening List with entry counts and data freshness (last sync time). Use to cite coverage in a compliance report: OFAC SDN/SSI/CMIC, BIS Entity List/DPL/UVL/MEU, State ITAR-Debarred/ISN, and more.

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).

OFACScreen Sanctions Screening Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ofacscreen-sanctions-screening": {
      "command": "npx",
      "args": [
        "-y",
        "ofacscreen-sanctions-screening"
      ]
    }
  }
}

Sanctions Screening Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "sanctions-screening-3": {
      "command": "npx",
      "args": [
        "-y",
        "sanctions-screening-3"
      ]
    }
  }
}

Frequently Asked Questions

OFACScreen Sanctions Screening is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Sanctions Screening belongs to Developer Tools using local stdio subprocess. Select OFACScreen Sanctions Screening when you need capabilities focused on developer tools and Sanctions Screening when you require tools for developer tools.

More alternatives to OFACScreen Sanctions Screening More alternatives to Sanctions Screening Developer Tools category hub