SanctionScreen: 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.

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

Screens people, companies and vessels against US OFAC, UK and Canadian sanctions lists, with optional paid tools funded by a USDC wallet.

What you can do
  • Screen people, companies and vessels against US OFAC, UK and Canadian sanctions lists.
  • Run free screening tools without any wallet configured.
  • Use paid tools that charge per call from a dedicated Base wallet holding USDC.
  • Bound spending with a per-call USD limit and a total per-session USD cap.
When to use it
Useful when an assistant needs to check names of individuals, companies or vessels against US, UK or Canadian sanctions lists as part of compliance, onboarding or due-diligence work.
Requirements
Runs locally as an npm package over stdio; no authentication is declared. Paid tools need SANCTIONSCREEN_WALLET_KEY, the private key of a dedicated low-balance Base wallet holding USDC; free tools work without it. Optional caps: SANCTIONSCREEN_MAX_PER_CALL_USD (default 0.10) and SANCTIONSCREEN_MAX_SPEND_USD (default 1.00).
Before you install
The server asks for a wallet private key (SANCTIONSCREEN_WALLET_KEY) and paid tools spend real USDC, so use a dedicated low-balance wallet and keep the per-call and session caps low. Screening results are list lookups, not a compliance determination. Names submitted for screening are sent to the provider's remote service.

Installation

In SourceWeft

  1. Open SanctionScreen: US, UK and Canada sanctions screening in the dashboard and add it to a workspace.
  2. 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

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  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.