Sanctions Io
NPM · @PIPEWORX/MCP-SANCTIONS-IO · 2 COMPONENTS
sanctions.io MCP — wraps the sanctions.io Screening API (api.sanctions.io)
Available components
Last scanned (3 hours ago)
Scores higher than 68% 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-io). 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 Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 621 tokens (~310/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 0
- Stability: 0.17 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 1 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 77
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-io@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-io |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-sanctions-io/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691894101 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0de00d2d4d5efb988272bcb9a1c8c3ca88afa6d49fb34dd764ee9b94704a5bf8e2b2a548ad966b98548694e46b6faf7729e05938f4853dfe349158f3a |
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_bulk ~265
Batch-screen up to 10,000 records against sanctions/PEP/watchlists in one request. Pass a `records` array of objects (each with a name, plus optional entity_type/external_identifier/date_of_birth/identifier/country). Top-level min_score/data_source/entity_type act as defaults applied to any record that omits them. Example: sanctions_bulk({ records: [{ name: "Vladimir Putin", external_identifier: "cust-1" }, { name: "Acme Corp", external_identifier: "cust-2" }], min_score: 0.9, _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | sanctions.io API token |
| data_source | string | – | Default comma-separated watchlist source(s) applied to records that omit their own (optional) |
| entity_type | string | – | Default entity_type applied to records that omit their own (optional) |
| min_score | number | – | Default minimum match score applied to records that omit their own. Default 0.88. |
| records | array | yes | Records to screen (up to 10,000). Each item: { name (required), entity_type?, external_identifier?, data_source?, min_score?, country?, date_of_birth?, identifier? } |
No output schema declared.
No examples provided.
sanctions_search ~301
Screen a single name against global sanctions, PEP, and watchlists (OFAC, EU, UN, FATF, criminal, adverse media) for AML compliance. Returns scored entity matches with list metadata. Example: sanctions_search({ name: "Vladimir Putin", entity_type: "individual", min_score: 0.9, _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | sanctions.io API token (get one at https://api.sanctions.io/users/signup/) |
| country | string | – | Filter matches by country (ISO name or code), optional |
| data_source | string | – | Comma-separated watchlist source(s) to screen against, e.g. "OFAC-COMPREHENSIVE", "PEP", "FATF". Omit to search all subscribed lists. |
| date_of_birth | string | – | Filter individual matches by date of birth, YYYY-MM-DD (optional) |
| entity_type | string | – | Restrict to a type: "individual" or "entity" (optional) |
| identifier | string | – | Filter by a known identifier (passport, tax ID, registration number, etc.), optional |
| min_score | number | – | Minimum match confidence score, 0.0-1.0. Default 0.88. |
| name | string | yes | Name to screen (person or organization), e.g. "Vladimir Putin", "Acme Corp" |
No output schema declared.
No examples provided.
How do I install the Sanctions Io MCP server?
Sanctions Io runs locally as an npm package, launched with npx -y @pipeworx/mcp-sanctions-io. 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-io
claude mcp add pipeworx-io-sanctions-io -- npx -y @pipeworx/mcp-sanctions-io
What is the Sanctions Io MCP server?
Sanctions Io is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sanctions-io. sanctions.io MCP, wraps the sanctions.io Screening API (api.sanctions.io). This page covers its npm package (@pipeworx/mcp-sanctions-io).
Is the Sanctions Io MCP server safe to use?
Sanctions Io scores 81 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 Io MCP server expose?
Sanctions Io exposes 2 tools: sanctions_search, sanctions_bulk. Their descriptions and schemas cost roughly 566 tokens of context every time the server is loaded.
Is the Sanctions Io MCP server still maintained?
Sanctions Io 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 Io MCP server under?
Sanctions Io declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.