sanctions
Server Details
Screen a name against OFAC's SDN and Consolidated Sanctions lists before a transaction.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools are functionally distinct: get_sanctionrail_info provides product/pricing details, while screen_name performs the actual sanctions lookup. However, the info tool's description also mentions fuzzy-match screening and 'check a counterparty,' which could briefly mislead an agent into thinking it performs screening. With only two tools, the risk is modest but real.
Both names use lowercase verb_noun style and are readable, but they are not strongly parallel: get_sanctionrail_info is a get_<product>_info meta-tool, while screen_name is a direct verb+object action. The naming is predictable enough with only two tools, though a clearer pattern would have made the relationship between them more obvious.
Two tools is on the low side of the typical range, but it is defensible for a narrowly scoped sanctions-screening server: one operational tool plus one informational setup tool. It does not feel bloated, and the small count is appropriate for the apparent single-purpose domain.
The server covers the primary workflow—screening a counterparty name before a transaction, onboarding, or payment approval—end to end in a single call. It lacks conveniences such as batch screening or a separate entity-detail lookup, but agents can achieve the core task with repeated screen_name calls. These are minor gaps rather than dead ends.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Screen a name against the U.S. Treasury OFAC SDN list. Information, not a compliance determination.
Screen a name or entity against OFAC SDN, the EU Consolidated list and the UK list.
Checks whether a name is on OFAC (US) sanctions lists, including SDN and Non-SDN, for compliance and
Screen company names against OFAC, UN, EU and UK sanctions and US export control lists.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceScreens names against the US Consolidated Screening List including OFAC SDN and BIS Entity List, keyless.105 npmMIT
- AlicenseAqualityBmaintenanceScreens person, company, vessel and aircraft names against the U.S. Treasury OFAC SDN sanctions list and explains every potential match: name-part scores, aliases, and date-of-birth or country conflicts. Runs locally with no API key; names never leave your machine.251Apache 2.0
- FlicenseNot gradedqualityDmaintenanceScreens 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.-
- AlicenseAqualityAmaintenanceEnables agents to fuzzy-screen person and company names against the OFAC SDN/Consolidated, EU, UK and UN sanctions lists downloaded fresh from official sources, returning potential-match statuses, 0–100 scores and listing details via a billed screening tool, plus a free local tool that lists covered sources, score scale and disclaimer.3MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.