Sanctionwise

io.github.qinisolabsPublished by GitHub account qinisolabsv0.1.1Updated Oct 24, 2026

Verified UK sanctions screening for AI agents — official FCDO UK Sanctions List, not guesses.

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

Screens names against the official FCDO UK Sanctions List, returning ranked possible matches with designation details or a no-match result.

What you can do
  • Screen a person, company or vessel name against the UK Sanctions List and get ranked possible matches with designation details
  • Look up the full official entry for a Unique ID, including names, aliases, regime and statement of reasons
  • Work offline from a bundled dataset that refreshes itself from a weekly public release and reports the dataset's report date
When to use it
Useful when an assistant needs to check whether a name appears on the UK sanctions list instead of answering from memory, for indicative screening that a human then verifies against the official entry.
Requirements
Runs locally as an npm package started with npx; no account, API key or token is needed. The list data is bundled for offline use, and startup may download the latest public list from a GitHub release.
Before you install
Results are indicative name matches only and must be verified by a human; a no-match is not a clearance. It covers the UK FCDO list only, screens just the name string supplied, and is not real-time or legal, compliance or KYC/AML advice. Names screened are not transmitted, but startup may fetch the public list from GitHub.

Installation

In SourceWeft

  1. Open Sanctionwise in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Qiniso]

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

json
{ "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

bash
npm i sanctionwise
ts
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

ToolWhat it does
screen_nameScreen a person/company/vessel name → ranked POSSIBLE matches with official designation details
get_sanctions_entryFull 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.

Source: README.md at commit 4f15466

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts