SanctionScreen
io.sanctionsscreen/sanctionscreen · v1.0.0
Screen counterparties and enrich companies for AI agents — sanctions checks, cited sources.
MCPremoteAPI keyE-commerceLaw & government
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 2 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 88/100
What it does: 2 tools · 2 read, 0 write · E-commerce, Developer tools, Law & government
Test call enrich_company: needs a key: rpc error: invalid_api_key: expected 'Authorization: Bearer cs_live_<32 hex chars>' (934 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://api.sanctionsscreen.io/mcpTools
2 tools listed at last check
screen_counterpartyScreen a counterparty name against the indexed sanctions lists (OFAC SDN, UK FCDO consolidated). What it does: normalizes the query (Unicode NFKD fold, punctuation strip, lowercase, Cyrillic/Greek transliteration; tolerant to token order e.g. "Putin Vladimir" vs "Vladimir Putin"), looks it up in thenrich_companyResolve a company domain or legal name to structured company facts via the free public GLEIF LEI registry. Inputs: {domain? e.g. "apple.com", name? e.g. "Apple Inc.", request_id? (idempotency)}. At least one of domain/name is required. v1 boundaries (returned honestly, never invented): - GLEIF has
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.sanctionsscreen/sanctionscreen)