# io.github.qinisolabs/sanctionwise (npm · sanctionwise)

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

- Trust score: 69/100 (medium)
- Change this week: +23
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `sanctionwise`: 69/100 (this document), [markdown](https://verifymcp.io/servers/qinisolabs-sanctionwise/sanctionwise.md), [page](https://verifymcp.io/servers/qinisolabs-sanctionwise/sanctionwise)

## Channel facts

- Registry: `npm`
- Package: `sanctionwise`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 41 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 260 tokens (~130/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add qinisolabs-sanctionwise -- npx -y sanctionwise
```

### Codex

```bash
codex mcp add qinisolabs-sanctionwise -- npx -y sanctionwise
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "qinisolabs-sanctionwise": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "sanctionwise"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add qinisolabs-sanctionwise --command npx --arg -y --arg sanctionwise
```

### Hermes

```yaml
mcp_servers:
  qinisolabs-sanctionwise:
    command: "npx"
    args: ["-y", "sanctionwise"]
```

### Other

```json
{
  "mcpServers": {
    "qinisolabs-sanctionwise": {
      "command": "npx",
      "args": [
        "-y",
        "sanctionwise"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 69, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-02 (score 66, +45)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] Security disclosure: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] License: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Dependency health: unverified → partial
- [functional] Licence: Apache-2.0

### 2026-08-01 (score 21, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 28, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-29 (score 46, +20)

- [functional regression] Dependency health: partial → unverified
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-28 (score 26, −20)

- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Dependency health: unverified → partial
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (2)

### `screen_name` (~175 tokens)

USE THIS to screen a person, company or vessel name against the UK Sanctions List before onboarding, paying, or transacting with them — never decide from memory whether someone is sanctioned. Returns ranked POSSIBLE matches with the official designation details (regime, type, sanctions imposed, statement-of-reasons snippet). CRITICAL: this is an INDICATIVE name-match only — a match MUST be verified by a human against the official entry and is NOT confirmation; a 'no match' is NOT a clearance (it covers the UK FCDO list only, screens the name string only, and reflects the dataset's report date). Not legal, compliance or KYC/AML advice.

Input parameters:

- `limit` (number): Max matches to return (default 10).
- `name` (string, required): The person/company/vessel name to screen.

### `get_sanctions_entry` (~85 tokens)

USE THIS to fetch the full official UK Sanctions List entry for a Unique ID (e.g. one returned by screen_name) — all names/aliases, regime, designation date, sanctions imposed, nationality/DOB, and the UK statement of reasons.

Input parameters:

- `id` (string, required): The UK Sanctions List Unique ID, e.g. 'RUS0001'.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/qinisolabs-sanctionwise/sanctionwise#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 66
- 2026-08-01: 21
- 2026-07-31: 28
- 2026-07-29: 46
- 2026-07-28: 26
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/sanctionwise
- Socket report: https://socket.dev/npm/package/sanctionwise
- Repository: https://github.com/qinisolabs/sanctionwise
- Changelog RSS feed: https://verifymcp.io/servers/qinisolabs-sanctionwise/sanctionwise/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/qinisolabs-sanctionwise/sanctionwise/changelog.json
- HTML version of this page: https://verifymcp.io/servers/qinisolabs-sanctionwise/sanctionwise