Sanctions Screening vs OFACScreen Sanctions… | AllMCPs
Side-by-Side Model Context Protocol Comparison
Sanctions Screening vs OFACScreen Sanctions Screening
In-depth architectural comparison of the Sanctions Screening and OFACScreen 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
Sanctions Screening
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
OFACScreen Sanctions Screening
Developer Tools · Remote HTTP/SSE
Quality: 42/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Sanctions Screening if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose OFACScreen Sanctions Screening if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
S
Choose Sanctions Screening when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
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.
OFACScreen Sanctions Screening Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
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).
Sanctions Screening is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, OFACScreen Sanctions Screening belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Sanctions Screening when you need capabilities focused on developer tools and OFACScreen Sanctions Screening when you require tools for developer tools.