SanctionsNorth: US, UK and Canada sanctions screening
NPM · SANCTIONSNORTH-MCP
Screen people, companies and vessels against US OFAC, UK and Canadian sanctions lists.
Available components
Last scanned (22 hours ago)
Scores higher than 41% 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 Security99
- 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
- 31 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 12 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 611 tokens (~152/item across 4 items; 4 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 Management43
- Stability observed for 13 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 4 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +4
- Stability: unverified → 0.30 ▲ functional
- 9 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 8 Nov 26 49
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 21 Nov 2026 · Analysed npm/sanctionsnorth-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 111 packages
| Packages resolved | 111 |
|---|---|
| Stale | 31 |
| 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 →
demo_screen Free demo: sanctions check for one name ~85
FREE, no wallet needed. Checks one name against US OFAC, UK and Canadian sanctions lists and returns whether there is a potential match, how many, and the top match only (no aliases, programs or DOB/country checks). Rate-limited to a few calls per day. Use screen_name for full details.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Person, company or vessel name |
No output schema declared.
No examples provided.
list_coverage Which sanctions lists are covered and how fresh ~40
FREE. The lists SanctionsNorth screens against, entry counts, when each was last fetched from the official source, publication dates where available, and licences.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
screen_name Sanctions screening: one name ~259
PAID $0.005 USDC per successful call. Screens a person, company or vessel against US OFAC SDN + non-SDN, the UK Sanctions List and Canada's Consolidated Autonomous Sanctions List (SEMA/JVCFOA). Fuzzy, transliteration-aware matching. Returns result (potential_match / no_match) and matches with score, strength (strong/possible), listed name and the alias that matched, list, programs, DOB, countries, listing date and flags. Invalid input is not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Nationality or address country; mismatches are flagged |
| dob | string | – | Date or year of birth (YYYY or YYYY-MM-DD). People whose listed birth year differs by more than 1 are down-ranked and flagged. |
| limit | integer | – | Max matches returned (default 10) |
| lists | array | – | Only these lists (default all four) |
| minScore | number | – | Match threshold 0.70-1.00 (default 0.85). Lower finds more spelling variants and more false positives. |
| name | string | yes | Name to screen |
| type | string | – | Restrict to people, companies/organisations or vessels (default any) |
No output schema declared.
No examples provided.
screen_names_batch Sanctions screening: up to 25 names ~227
PAID $0.05 USDC per successful call. Screens up to 25 people, companies or vessels in one call against the same US, UK and Canadian lists (e.g. a vendor list or a payment batch). Returns a per-name result and the top matches for each. Cheaper than screen_name for more than 10 names.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Nationality or address country; mismatches are flagged |
| dob | string | – | Date or year of birth (YYYY or YYYY-MM-DD). People whose listed birth year differs by more than 1 are down-ranked and flagged. |
| limit | integer | – | Max matches per name (default 3) |
| lists | array | – | Only these lists (default all four) |
| minScore | number | – | Match threshold 0.70-1.00 (default 0.85). Lower finds more spelling variants and more false positives. |
| names | array | yes | 1-25 names |
| type | string | – | Restrict to people, companies/organisations or vessels (default any) |
No output schema declared.
No examples provided.
How do I install the SanctionsNorth: US, UK and Canada sanctions screening MCP server?
SanctionsNorth: US, UK and Canada sanctions screening runs locally as an npm package, launched with npx -y sanctionsnorth-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · sanctionsnorth-mcp
claude mcp add tendertrail-sanctionsnorth-mcp -- npx -y sanctionsnorth-mcp
What is the SanctionsNorth: US, UK and Canada sanctions screening MCP server?
SanctionsNorth: US, UK and Canada sanctions screening is an MCP server listed in the public MCP registry as io.github.tendertrail/sanctionsnorth-mcp. Screen people, companies and vessels against US OFAC, UK and Canadian sanctions lists. This page covers its npm package (sanctionsnorth-mcp).
Is the SanctionsNorth: US, UK and Canada sanctions screening MCP server safe to use?
SanctionsNorth: US, UK and Canada sanctions screening scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 SanctionsNorth: US, UK and Canada sanctions screening MCP server expose?
SanctionsNorth: US, UK and Canada sanctions screening exposes 4 tools: demo_screen, list_coverage, screen_name, screen_names_batch. Their descriptions and schemas cost roughly 611 tokens of context every time the server is loaded.
Is the SanctionsNorth: US, UK and Canada sanctions screening MCP server still maintained?
SanctionsNorth: US, UK and Canada sanctions screening is still listed as active in the MCP registry. We last reached this channel on 21 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 SanctionsNorth: US, UK and Canada sanctions screening MCP server under?
SanctionsNorth: US, UK and Canada 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.
What did VerifyMCP test on the SanctionsNorth: US, UK and Canada sanctions screening MCP server?
VerifyMCP ran 15 checks on SanctionsNorth: US, UK and Canada sanctions screening, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about SanctionsNorth: US, UK and Canada sanctions screening: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.