sanctionwise
Verified UK sanctions screening for AI agents.
Ask an LLM whether someone is sanctioned and it answers from stale, fuzzy memory. Designations change constantly — that's data, not recall. sanctionwise screens a name against the official FCDO UK Sanctions List and returns possible matches with their real designation details, or a clean "no match". "Qiniso" means "truth" in Zulu.
Read this. sanctionwise is an indicative name-match screen, not a determination. A match is a POSSIBLE match a human must verify against the official entry — not confirmation. A "no match" is NOT a clearance (UK FCDO list only, name-string only, as of the dataset's report date). It is not legal, compliance or KYC/AML advice and not a substitute for a regulated screening process.
Why it exists
Whether a specific person, company or vessel is currently designated under UK sanctions is exact, fast-changing reference data spread across ~6,200 entries and dozens of regimes — exactly what a language model cannot recall. Asked anyway, it guesses, with serious consequences either way (a missed match, or a false accusation). sanctionwise returns the official FCDO designation by lookup, or an honest "no match", with the disclaimer attached every time.
Tools
screen_name
Screen a person/company/vessel name → ranked possible matches with the official regime, sanctions imposed and statement-of-reasons snippet. Accent- and case-insensitive; screens aliases too.
get_sanctions_entry
The full official entry for a Unique ID — all names/aliases, regime, designation date, nationality/DOB, statement of reasons.
Add it to Claude
Easiest — one click, no config file. Download the Desktop Extension and open it; Claude Desktop installs it in one click:
Download for Claude Desktop (.mcpb)
Or add it as a connector
Settings → Connectors → Add custom connector, and paste the URL. Hosted on the edge, no login, no key:
https://sanctionwise.qinisolabs.workers.dev/mcp
Or run it locally
Prefer to run it yourself over stdio? The official data is bundled (works offline) and the tool auto-refreshes from a weekly GitHub Release — no token, no manual step. Add this under mcpServers and restart:
{
"mcpServers": {
"sanctionwise": { "command": "npx", "args": ["-y", "sanctionwise"] }
}
}
Using asdf or nvm? The desktop app may not see npx on its PATH — replace "npx" with the full path from which npx.
What it is not
sanctionwise screens against the official FCDO UK Sanctions List only. It is not a compliance determination, not multi-list (no EU/US-OFAC/UN), not real-time (reflects the dataset's report date), and not legal/compliance/KYC-AML advice or a regulated screening service. A match needs human verification; a non-match is not a clearance.