Sanctions Screening
NPM · @PIPEWORX/MCP-SANCTIONS-SCREENING · 2 COMPONENTS
Sanctions Screening MCP — screen people, companies, vessels, and aircraft against the US…
Available components
Last scanned (2 hours ago)
Scores higher than 72% of npm 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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-sanctions-screening). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 742 tokens (~247/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +3
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.20 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-sanctions-screening@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-sanctions-screening |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-sanctions-screening/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691894615 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:15bc2ae243e4c5ed7bfb186fadb39feac97226cba63c1e33f0061e294d8e5260ceab7e51ed8e43e84c9167b281a3c9fba734996456894ae8ba6e03911 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
sanctions_entry ~143
Get the full Consolidated Screening List record for one entry by its uid (from sanctions_screen results, e.g. "SDN:12345") or by OFAC entity number. Returns every field: all aliases, addresses, identity documents (passports, tax IDs, IMO numbers, crypto wallet addresses), sanction programs, license requirements, Federal Register notice, vessel details, and remarks.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_number | string | – | OFAC/CSL entity number, e.g. "36318". Used if uid is not given. |
| uid | string | – | Entry uid from sanctions_screen, e.g. "SDN:36318" or "EL:e123". |
No output schema declared.
No examples provided.
sanctions_lists ~81
List the US restricted-party lists this pack screens against, with entry counts and data freshness (last sync time). Use to cite coverage in a compliance report: OFAC SDN/SSI/CMIC, BIS Entity List/DPL/UVL/MEU, State ITAR-Debarred/ISN, and the DHS UFLPA Entity List.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sanctions_screen ~463
Screen a person, company, vessel, or aircraft name against the US restricted-party lists — OFAC SDN sanctions, Sectoral Sanctions (SSI), Chinese Military-Industrial Complex (CMIC), BIS Entity List / Denied Persons / Military End User, State ITAR Debarred, and the DHS UFLPA Entity List for Xinjiang forced-labor import bans (~26k entries, synced daily). Fuzzy name matching with a 0-1 relevance score, matched aliases, programs, addresses, and which list each hit is on. Use for KYB / KYC / AML / export-control checks, and to check whether a supplier is subject to the forced-labor import ban before importing. Returns an empty matches array when the name is clear. Handles CYRILLIC names — Russian, Ukrainian, Serbian: the lists are held in Latin script, so a Cyrillic name is romanised into a small candidate set (both conventions: г as g or h, и as i or y, я as ya or ia) and every form is screened, with matched_form on each hit naming the spelling that produced it. So "Сбербанк" returns the same matches as "Sberbank". A name in a script we do NOT romanise (Greek, Arabic, Hebrew, Han, Japanese, Korean, Devanagari, Thai) still cannot be compared, and is refused with clear:null / screened:false rather than reported clear — pass the Latin transliteration used on the list.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | 2-letter country code to filter matches by address/nationality, e.g. "CN", "RU", "IR". |
| limit | number|string | – | Max matches (1-50, default 10). |
| list | string | – | Restrict to one list code: SDN | SSI | CMIC | NS-MBS | CAP | PLC | EL | DPL | UVL | MEU | DTC | ISN | UFLPA. |
| name | string | yes | Person, company, vessel, or aircraft name to screen, e.g. "Rosneft" or "Huawei Technologies". |
| type | string | – | Restrict by entry type: Entity | Individual | Vessel | Aircraft. |
No output schema declared.
No examples provided.
How do I install the Sanctions Screening MCP server?
Sanctions Screening runs locally as an npm package, launched with npx -y @pipeworx/mcp-sanctions-screening. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-sanctions-screening
claude mcp add pipeworx-io-sanctions-screening -- npx -y @pipeworx/mcp-sanctions-screening
What is the Sanctions Screening MCP server?
Sanctions Screening is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sanctions-screening. Sanctions Screening MCP, screen people, companies, vessels, and aircraft against the US… This page covers its npm package (@pipeworx/mcp-sanctions-screening).
Is the Sanctions Screening MCP server safe to use?
Sanctions Screening scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Sanctions Screening MCP server expose?
Sanctions Screening exposes 3 tools: sanctions_screen, sanctions_entry, sanctions_lists. Their descriptions and schemas cost roughly 687 tokens of context every time the server is loaded.
Is the Sanctions Screening MCP server still maintained?
Sanctions Screening is still listed as active in the MCP registry. We last reached this channel on 5 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 Sanctions Screening MCP server under?
Sanctions Screening declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.