npm sanctionwisestdioApache-2.0updated 2mo ago
Verified UK sanctions screening for AI agents โ official FCDO UK Sanctions List, not guesses.
What can you do with sanctionwise?
sanctionwise
Verified UK sanctions screening for AI agents โ official FCDO UK Sanctions List, not guesses.
Verified, trustworthy data tools for AI agents. "Qiniso" means "truth" in Zulu.
Website ยท npm ยท MCP Registry
Ask an LLM "is this person on the UK sanctions list?" and it will answer from stale, fuzzy memory. Designations change constantly and are specific โ that's data, not something to 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".
โ ๏ธ Read this โ what this is and is NOT
- Indicative name-match only. A match is a POSSIBLE match that a human must verify against the official entry (names are widely shared and transliterated). It is not confirmation that the party you mean is the sanctioned party.
- A "no match" is NOT a clearance. It covers the UK (FCDO) list only, screens the name string you pass (not DOBs or aliases you didn't supply), and reflects the dataset's report date, not real-time.
- Not advice. Not legal, compliance, KYC/AML or sanctions advice, and not a substitute for a regulated sanctions-screening process. Every response includes this disclaimer.
Install
{ "mcpServers": { "sanctionwise": { "command": "npx", "args": ["-y", "sanctionwise"] } } }
The official UK Sanctions List data is bundled in the package (works offline, out of the box). The tool also auto-refreshes from a weekly-updated GitHub Release on startup โ cached locally, no key, no token, no manual step โ so it stays current on its own. Every response reports the dataset's report date.
Use it as a library
npm i sanctionwise
import { screenName, getSanctionsEntry } from "sanctionwise";
screenName("Vladimir Putin");
// { matchCount: 3, results: [{ id: "RUS0251", type: "Individual",
// primaryName: "Vladimir Vladimirovich PUTIN", matchType: "exact",
// regimes: ["The Russia (Sanctions) (EU Exit) Regulations 2019"], sanctions: "Asset freeze|โฆ" }],
// disclaimer: "INDICATIVE NAME-MATCH SCREEN ONLY. โฆ" }
screenName("Acme Quilting Supplies Ltd").matchCount; // 0 โ no match (NOT a clearance)
getSanctionsEntry("RUS0251"); // full official entry for a Unique ID
Matching folds accents and is case/punctuation-insensitive, and screens primary names and aliases.
Tools โ 2
| Tool | What it does |
|---|---|
| screen_name | Screen a person/company/vessel name โ ranked POSSIBLE matches with official designation details |
| get_sanctions_entry | Full official entry for a Unique ID (names, aliases, regime, statement of reasons, โฆ) |
Data & auto-refresh
The data is the official FCDO UK Sanctions List (designated persons, entities and ships under the Sanctions and Anti-Money Laundering Act 2018), published under the Open Government Licence v3.0. scripts/build-data.mjs parses the official CSV into one record per target (all names/aliases grouped); the bundled build currently carries 6,200+ designated targets. A weekly GitHub Action (.github/workflows/refresh-data.yml) re-downloads the list and publishes it as a GitHub Release asset; the installed tool fetches that asset on startup (cached, offline-safe), so it self-updates with no npm token and no manual step. The bundled copy is the offline / first-run fallback.
What it is not
- Not a compliance determination. Indicative screening to surface possible matches for human review โ nothing more.
- Not multi-list. UK (FCDO) list only โ not the EU, US (OFAC), UN consolidated, or any other list.
- Not real-time. Reflects the dataset's report date; check the live list for the current position.
- Not advice, and not a regulated screening service.
Privacy
This tool runs locally on your machine and is built not to collect, store, or transmit your data โ no analytics, no telemetry, no account. Screening runs locally; on startup it may download the latest public UK Sanctions List from a GitHub Release, but the names you screen are never transmitted. Full policy: https://qinisolabs.github.io/privacy.html.
License
Apache-2.0 (code). Sanctions data ยฉ Crown copyright, FCDO, Open Government Licence v3.0; see NOTICE.
Install
Add sanctionwise to your client. Pick the one you use.
claude mcp add sanctionwise -- npx -y sanctionwisecodex mcp add sanctionwise -- npx -y sanctionwiseamp mcp add sanctionwise -- npx -y sanctionwise{
"mcpServers": {
"sanctionwise": {
"command": "npx",
"args": [
"-y",
"sanctionwise"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"sanctionwise": {
"command": "npx",
"args": [
"-y",
"sanctionwise"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"sanctionwise","command":"npx","args":["-y","sanctionwise"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"sanctionwise": {
"command": "npx",
"args": [
"-y",
"sanctionwise"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"sanctionwise": {
"command": "npx",
"args": [
"-y",
"sanctionwise"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"sanctionwise": {
"command": "npx",
"args": [
"-y",
"sanctionwise"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"sanctionwise": {
"type": "local",
"command": "npx",
"args": [
"-y",
"sanctionwise"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"sanctionwise": {
"command": {
"path": "npx",
"args": [
"-y",
"sanctionwise"
]
}
}
}
}Add to your Zed `settings.json`.
npx -y sanctionwiseRun `goose configure`, choose **Add Extension โ Command-line Extension**, and paste this command.
Score
39 / 100
Incomplete
- Documentation25/25
- Maintenance16/25
- Trust16/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 71 days ago
- Has a release history
- Repository is not archived
- Licensed Apache-2.0
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint โ no local install
Version history
| Versions | Published |
|---|---|
| 0.1.1Latest | Jun 19, 2026 |
| 0.1.0 | Jun 19, 2026 |