fairquery-sanctions-screener
OfficialRelated Servers
Alternatives to fairquery-sanctions-screener
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceScreens names and companies against OFAC, EU, UK, and UN sanctions lists with fuzzy-match scores, supporting bulk lookups for AML/KYC checks. Data is sourced directly from official government lists and cached for fast repeat checks.-
- AlicenseNot gradedqualityAmaintenanceScreen names against consolidated OFAC, EU, UK, and UN sanctions lists and resolve legal entities via GLEIF, with offline fuzzy matching.131 npm1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceScreens names against the US Consolidated Screening List including OFAC SDN and BIS Entity List, keyless.26 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables screening names and batches against global sanctions, PEP, and watchlists for AML compliance, returning scored matches.20 npmMIT

CompliAPIofficial
AlicenseNot gradedqualityCmaintenanceReal-time OFAC and global sanctions screening for AI agents: screen crypto addresses, emails, websites, government IDs, and countries against OFAC SDN and 10+ sanctions/crime/risk lists, plus PEP screening, VPN detection, and IP geolocation. Hosted remote streamable-HTTP server at https://api.compliapi.com/mcp (anonymous tools/list; free API key or x402 pay-per-call).MIT- AlicenseNot gradedqualityCmaintenanceChecks names against US FinCEN financial crime lists for compliance and AML due diligence, with a single read-only tool.MIT
TDQS
Scored across 2 tools
screen_names performs actual sanctions screening while list_sources only returns static metadata about the covered lists. The descriptions explicitly state when to use each and forbid using the other for the wrong task, so an agent can easily tell them apart.
Both tools follow a clean verb_noun pattern in snake_case (screen_names, list_sources). There is no mixing of conventions or vague verbs.
The server has only two tools, and while each earns its place (screen_names does the core work, list_sources supports it), the surface is thin for a screening service that could plausibly offer tools to inspect cache status or retrieve specific entry details. This is borderline per the rubric for 1-2 tools.
The core screening workflow is fully covered with rich parameters (names/queries, filters, minScore, list selection) and a helper for source metadata. Minor gaps exist, such as no tool to manage or inspect the Apify cache or fetch a single list entry outside of screening results, but these are workable.