mcp-sanctions
PYPI · ATOMNO-MCP-SANCTIONS
Sanctions/watchlist screening (RF, OFAC, EU, UK, UN) with confidence levels for KYC/AML.
Available components
Last scanned (1 day ago)
Scores higher than 85% of PyPI servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 35 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 62 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 548 tokens (~109/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −3
- Stability: pass → 0.83 functional
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 +4
- Stability: 0.77 → pass security
- 16 Oct 26 −4
- Stability: pass → 0.77 functional
- 15 Oct 26 +1
- Stability: 0.97 → pass security
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 90. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/atomno-mcp-sanctions@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 35 packages
| Packages resolved | 35 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_watchlists ~34
Метаданные поддерживаемых публичных перечней: id, источник, версия, дата обновления. Тариф Pro.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
screen_entity ~101
Скрининг организации по наименованию и опционально ИНН/ОГРН по публичным перечням. Тариф Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| inn | – | – | ИНН организации (10 или 12 цифр), если известен. |
| name | string | yes | Наименование организации для скрининга. |
| ogrn | – | – | ОГРН/ОГРНИП (13 или 15 цифр), если известен. |
Structured output declared, but exposes no named fields.
No examples provided.
screen_foreign_agent ~89
Проверка по реестру иностранных агентов (Минюст РФ): точное и нечёткое совпадение ФИО/ИНН. Нейтральная выдача.
| Name | Type | Req | Description |
|---|---|---|---|
| fio | string | yes | ФИО или наименование для проверки по реестру иностранных агентов. |
| inn | – | – | ИНН (10 или 12 цифр), если известен. |
Structured output declared, but exposes no named fields.
No examples provided.
screen_inn ~57
Быстрый точный скрининг по ИНН по всем поддерживаемым перечням. Тариф Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| inn | string | yes | ИНН физлица или юрлица (10 или 12 цифр). |
Structured output declared, but exposes no named fields.
No examples provided.
screen_person ~103
Скрининг физлица по ФИО (+ опционально дата рождения) по публичным перечням. Нейтральная выдача, требуется ручная верификация. Тариф Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_date | – | – | Дата рождения YYYY-MM-DD для дизамбигуации однофамильцев. |
| full_name | string | yes | ФИО физлица для скрининга (напр. «Иванов Иван Иванович»). |
Structured output declared, but exposes no named fields.
No examples provided.
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.
pypi · atomno-mcp-sanctions
claude mcp add atomno-mcp-mcp-sanctions -- uvx atomno-mcp-sanctions
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 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 4 November 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.