# mcp-sanctions (pypi · atomno-mcp-sanctions)

Sanctions/watchlist screening (RF, OFAC, EU, UK, UN) with confidence levels for KYC/AML.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `atomno-mcp-sanctions`: 80/100 (this document), [markdown](https://verifymcp.io/servers/atomno-mcp-mcp-sanctions/atomno-mcp-sanctions.md), [page](https://verifymcp.io/servers/atomno-mcp-mcp-sanctions/atomno-mcp-sanctions)

## Channel facts

- Registry: `pypi`
- Package: `atomno-mcp-sanctions`
- 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-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 36 dependencies flagged as unhealthy.
- **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 (MIT).
  - Actively maintained (last published 17 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 548 tokens (~109/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the mcp-sanctions server?

mcp-sanctions runs locally as a PyPI package, launched with uvx atomno-mcp-sanctions. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add atomno-mcp-mcp-sanctions -- uvx atomno-mcp-sanctions
```

### Cursor

```json
{
  "mcpServers": {
    "atomno-mcp-mcp-sanctions": {
      "command": "uvx",
      "args": [
        "atomno-mcp-sanctions"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "atomno-mcp-mcp-sanctions": {
      "command": "uvx",
      "args": [
        "atomno-mcp-sanctions"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add atomno-mcp-mcp-sanctions -- uvx atomno-mcp-sanctions
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "atomno-mcp-mcp-sanctions": {
      "type": "local",
      "command": [
        "uvx",
        "atomno-mcp-sanctions"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add atomno-mcp-mcp-sanctions --command uvx --arg atomno-mcp-sanctions
```

### Hermes

```yaml
mcp_servers:
  atomno-mcp-mcp-sanctions:
    command: "uvx"
    args: ["atomno-mcp-sanctions"]
```

### Netclaw

```json
{
  "McpServers": {
    "atomno-mcp-mcp-sanctions": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "atomno-mcp-sanctions"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add atomno-mcp-mcp-sanctions -t stdio -c uvx -a atomno-mcp-sanctions
```

### Other

```json
{
  "mcpServers": {
    "atomno-mcp-mcp-sanctions": {
      "command": "uvx",
      "args": [
        "atomno-mcp-sanctions"
      ]
    }
  }
}
```

## 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-09-19 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 75, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-03 (score 72, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-02 (score 57)

First indexed and scored.

## MCP tools (5)

### `screen_person` (~103 tokens)

Скрининг физлица по ФИО (+ опционально дата рождения) по публичным перечням. Нейтральная выдача, требуется ручная верификация. Тариф Pro.

Input parameters:

- `birth_date`: Дата рождения YYYY-MM-DD для дизамбигуации однофамильцев.
- `full_name` (string, required): ФИО физлица для скрининга (напр. «Иванов Иван Иванович»).

### `screen_entity` (~101 tokens)

Скрининг организации по наименованию и опционально ИНН/ОГРН по публичным перечням. Тариф Pro.

Input parameters:

- `inn`: ИНН организации (10 или 12 цифр), если известен.
- `name` (string, required): Наименование организации для скрининга.
- `ogrn`: ОГРН/ОГРНИП (13 или 15 цифр), если известен.

### `screen_inn` (~57 tokens)

Быстрый точный скрининг по ИНН по всем поддерживаемым перечням. Тариф Pro.

Input parameters:

- `inn` (string, required): ИНН физлица или юрлица (10 или 12 цифр).

### `screen_foreign_agent` (~89 tokens)

Проверка по реестру иностранных агентов (Минюст РФ): точное и нечёткое совпадение ФИО/ИНН. Нейтральная выдача.

Input parameters:

- `fio` (string, required): ФИО или наименование для проверки по реестру иностранных агентов.
- `inn`: ИНН (10 или 12 цифр), если известен.

### `list_watchlists` (~34 tokens)

Метаданные поддерживаемых публичных перечней: id, источник, версия, дата обновления. Тариф Pro.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/atomno-mcp-mcp-sanctions/atomno-mcp-sanctions#diagnostics

## Score history

- 2026-09-20: 80
- 2026-09-19: 80
- 2026-09-18: 79
- 2026-09-17: 79
- 2026-09-16: 78
- 2026-09-15: 78
- 2026-09-14: 77
- 2026-09-13: 77
- 2026-09-12: 76
- 2026-09-11: 76
- 2026-09-10: 75
- 2026-09-09: 75
- 2026-09-08: 72
- 2026-09-07: 72
- 2026-09-06: 72
- 2026-09-05: 72
- 2026-09-04: 72
- 2026-09-03: 72
- 2026-09-02: 57

## Common questions

### What is the mcp-sanctions server?

mcp-sanctions is listed in the public MCP registry as io.github.atomno-mcp/mcp-sanctions. Sanctions/watchlist screening (RF, OFAC, EU, UK, UN) with confidence levels for KYC/AML. This page covers its PyPI package (atomno-mcp-sanctions).

### Is the mcp-sanctions server safe to use?

mcp-sanctions scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the mcp-sanctions server expose?

mcp-sanctions exposes 5 tools: screen_person, screen_entity, screen_inn, screen_foreign_agent, list_watchlists. Their descriptions and schemas cost roughly 384 tokens of context every time the server is loaded.

### Is the mcp-sanctions server still maintained?

mcp-sanctions is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the mcp-sanctions server under?

mcp-sanctions declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/atomno-mcp-sanctions/
- Socket report: https://socket.dev/pypi/package/atomno-mcp-sanctions
- Repository: https://github.com/atomno-mcp/mcp-sanctions
- Changelog RSS feed: https://verifymcp.io/servers/atomno-mcp-mcp-sanctions/atomno-mcp-sanctions.xml
- Changelog JSON feed: https://verifymcp.io/servers/atomno-mcp-mcp-sanctions/atomno-mcp-sanctions.json
- HTML version of this page: https://verifymcp.io/servers/atomno-mcp-mcp-sanctions/atomno-mcp-sanctions