PublicAML plugin for Claude Code: AML checks, incoming-payment screening and invoice verification
PublicAML · Announcement · 15 November 2026
PublicAML now has a plugin for Claude Code. It installs with two commands. It connects our free MCP server and teaches Claude four jobs: risk-score any address, screen every incoming payment to your wallets, check on-chain that a counterparty really paid an invoice, and trace stolen funds. It covers Bitcoin, Ethereum, BNB Chain and TRON, plus Solana for address screening. No account and no API key.
Install
/plugin marketplace add saloprj/publicaml-claude-plugin /plugin install publicaml@publicaml
Run these two commands inside Claude Code, then restart it. The skills appear as /publicaml:… commands. Claude also picks them up by itself when you paste an address or ask about a payment.
What the plugin adds
| /publicaml:check-address | Risk score 0–100, risk level, what the wallet is, and sanctions exposure for an address or a transaction. From MEDIUM up, it also shows where the risk came from: the source, the number of hops and the amount. |
| /publicaml:incoming-payments | KYT for your own wallets. It lists new incoming transfers and drops dust and address-poisoning spam. It scores each sender once and suggests an action: accept, hold and ask for source of funds, or escalate. It remembers the last run, so the next one picks up only new transfers. |
| /publicaml:verify-invoice-payment | Did the client pay? It finds the transfer by tx hash, or by amount from the invoice date, and checks the asset, network and amount. Then it AML-screens the payer. Verdicts: paid, paid but hold for review, underpaid or overpaid, wrong network, or not found. |
| /publicaml:trace-funds | Where the money went (exchanges, mixers, bridges) or where it came from. It follows funds through DEX swaps on Ethereum and BNB Chain. |
Things you can ask
- “Check TXyz… for AML risk.”
- “Screen all incoming payments to our wallets this week.”
- “Did ACME pay invoice 1042: 4,800 USDT TRC-20 to TXyz…?”
- “Is this transaction hash the payment for our invoice, and is the payer clean?”
- “Where did the funds from 0xabc… go?”
Your wallets
The payment skills read your wallets from ~/.claude/publicaml-wallets.txt, or from publicaml-wallets.txt in your project. Put one wallet per line, as chain and address. To run the screening every day while Claude Code is open, use /loop 1d /publicaml:incoming-payments.
tron TXyz... # main USDT wallet ethereum 0xabc... # treasury
What it sees
Every tool is read-only and never moves funds. The plugin sends PublicAML only the address or transaction hash, the chain and the tool options. Your wallet list stays on your machine; only the addresses being checked are sent. A score is a risk signal, not a legal verdict. Privacy policy.
Step by step: AML-check incoming crypto payments and verify invoices with Claude →
Using Claude Desktop, Cursor or your own agent? The same tools as an MCP server →
