
SanctionsNorth: US, UK and Canada sanctions screening
io.github.tendertrailPublished by GitHub account tendertrailv0.1.0Updated Nov 8, 2026
Screen people, companies and vessels against US OFAC, UK and Canadian sanctions lists.
Overview
Screens people, companies and vessels against US OFAC, UK and Canadian sanctions lists from an assistant, with optional paid tools.
- What you can do
- Screen individuals, companies and vessels against US OFAC, UK and Canadian sanctions lists
- Run free screening queries without any wallet or payment setup
- Use paid screening tools that are charged per call in USDC from a Base wallet
- Keep paid usage within per-call and per-session USD caps set by environment variables
- When to use it
- Useful when you need quick sanctions or watchlist checks on a person, company or vessel during compliance, onboarding, due diligence or research work, and want the assistant to run the lookup directly.
- Requirements
- Runs as a local npm package over stdio on a desktop machine. Free tools need no credentials. Paid tools need SANCTIONSNORTH_WALLET_KEY, the private key of a dedicated low-balance Base wallet holding USDC, plus optional caps SANCTIONSNORTH_MAX_PER_CALL_USD (default 0.10) and SANCTIONSNORTH_MAX_SPEND_USD (default 1.00). Network access to the provider endpoint is required.
Installation
In SourceWeft
- Open SanctionsNorth: US, UK and Canada sanctions screening in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Tools
0Version history
1- v0.1.0LatestNov 8, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.