Crypto AML & Wallet Screener MCP — OFAC, EU, UN & AMLBot

The only MCP-native Apify Actor that combines real-time sanctions list screening (OFAC SDN, EU Consolidated, UN) with active on-chain risk scoring (via AMLBot API) in a single execution. Screen Bitcoin, Ethereum, Solana, BNB Chain, and Tron addresses instantly.

This compliance bridge is designed to automate cryptocurrency wallet due diligence. It downloads, parses, and memory-caches the official global sanctions databases once per run, then queries the AMLBot REST API with intelligent pacing (5 reqs/sec) and exponential backoff. Results are flattened as columns for easy Table View and Excel/CSV export on the Apify Console.

---

🎯 Target Audience & 💡 Primary Use Cases

Casos de Uso / Valor Comercial (Commercial Value)

• Onboarding Risk Check: Screen new users' wallet addresses during registration or sign-up to block sanctioned individuals.
• Transaction Validation: Validate destination and origin wallet addresses before executing smart contract transfers or payments.
• Periodic Auditing: Re-check existing corporate asset portfolios and database records against daily updated lists.
• DeFi & Web3 Compliance: Automate MiCA/FinCEN compliance requirements without paying for expensive enterprise suites.

Público Objetivo (Target Audience)

• Compliance & Legal Teams: Audit and export transaction history with legal evidence of sanctions checks.
• Exchanges & VASPs: High-performance REST API to automate wallet verification pipelines.
• Startups & DeFi Builders: Simple integration via JSON webhooks or native Model Context Protocol (MCP).
• AI Agents & LLMs: Fetch risk profiles instantly from the chat using MCP tools without backend middleware.

---

🚀 Características Clave (Key Technical Capabilities)

• Official Sanctions Parsing: Automatically fetches and processes XML data directly from:
  • OFAC SDN list (U.S. Department of the Treasury)
  • EU Consolidated Sanctions List (European Commission FSF)
  • UN Consolidated list (United Nations Security Council)
• On-Chain Risk Enrichment: Integrates with AMLBot API to fetch the 0–100 transaction history risk percentage.
• Multi-Chain Support: Auto-detects formats and validates addresses for Bitcoin (BTC), Ethereum (ETH), Solana (SOL), BNB Chain (BSC), and Tron (TRX).
• Anti-Crash & Fallback Design: Missing sanctions tokens or AMLBot timeouts will not crash your run; the Actor logs a warning, sets an errorCode (e.g., API_TIMEOUT, UNSUPPORTED_CHAIN), and saves the partial results.
• Intelligent Rate-Limiting: Built-in 200ms pacing and exponential retry (up to 3 attempts) on AMLBot API responses (429/503) to respect provider boundaries.
• MCP-Ready Integration: Ready to expose as a tool in Claude Desktop, Cursor, or VS Code using mcp.apify.com.

---

⚙️ Input Parameters

The Actor accepts the following input parameters in its configuration form (INPUT_SCHEMA):

Field / Campo	Type	Default	Description
walletAddresses	Array[String]	Required	List of cryptocurrency wallet addresses to screen.
chains	Array[String]	["BTC","ETH","SOL","BSC","TRX"]	Supported blockchains. Allowed values: BTC, ETH, SOL, BSC, TRX.
sanctionsLists	Array[String]	["ofac","eu","un","uk"]	Sanctions lists to check against.
riskScoring	Boolean	true	Activates AMLBot on-chain risk check. Requires AMLBOT_API_KEY env var.
webhookUrl	String	null	Optional URL to send a POST request with the final summary.

---

📊 Output Schema

To maximize usability, the output dataset is completely flattened so that it maps cleanly as columns in the Apify spreadsheet / Table view.

Flat Table View Columns (Root JSON level)

• wallet (String): The wallet address analyzed.
• chain (String): Detected blockchain network (e.g. BTC, ETH, SOL, BSC, TRX).
• sanctioned (Boolean): true if the address matched a blacklist, false otherwise.
• matchedList (String): The list name where the match occurred (ofac, eu, un, or none).
• matchedEntity (String): Name of the sanctioned individual/entity (or null).
• riskScore (Number): 0–100 numerical on-chain risk score from AMLBot (or null).
• riskLevel (String): Normalized risk level: LOW, MEDIUM, HIGH, CRITICAL, or UNKNOWN.
• checkedAt (String): ISO 8601 timestamp of the check.
• errorCode (String): Error descriptor if a service failed (e.g., UNSUPPORTED_CHAIN, API_TIMEOUT, INVALID_ADDRESS, or null).

---

🧠 Risk Level Methodology

The Actor categorizes the numerical risk score returned by the AMLBot API into four clear levels:

• LOW (0–25): Safe wallet address. No suspicious connections detected.
• MEDIUM (26–60): Warning. Minor exposure to mixers, peer-to-peer exchanges, or secondary risk sources.
• HIGH (61–85): High risk. Direct exposure to gambling, darknet markets, or stolen funds.
• CRITICAL (86–100): Severe threat. Directly linked to sanctioned entities, hackers, or illicit services.

---

🔌 Automatización e Integraciones

• Webhooks & No-Code: Configure the webhookUrl input parameter to trigger automated email/Slack alerts or update Zapier, Make, or n8n workflows when sanctioned: true or riskLevel: "CRITICAL" is detected.
• Schedules: Run the Actor daily or weekly using Apify Console schedules to monitor active customer wallets.
• Cloud Databases: Sync Apify datasets directly to BigQuery, Snowflake, Amazon S3, or PostgreSQL for compliance record audits.

---

📋 Example Output (JSON)

{
  "wallet": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
  "chain": "ETH",
  "sanctioned": false,
  "matchedList": "none",
  "matchedEntity": null,
  "riskScore": 12,
  "riskLevel": "LOW",
  "checkedAt": "2026-06-11T10:04:15.864Z",
  "errorCode": null
}

---

💳 Pricing & Monetization

This Actor is optimized for Pay-Per-Event (PPE) pricing on the Apify Store, providing predictable billing:

• run_start event: $0.05 USD per execution.
• wallet_screened event: $0.10 USD per wallet address checked.

---

🙋 Frequently Asked Questions

How do I configure my AMLBot API Key?

You must set up your AMLBot API Key as an environment variable in the Actor settings on Apify Console. Create a variable named AMLBOT_API_KEY and paste your token. If the variable is missing, the Actor will automatically skip the AMLBot checks and only perform sanctions list matches.

Why does the check return UNSUPPORTED_CHAIN?

This error is returned if the wallet address format does not match any known blockchain regex, or if the detected chain is not in the allowed chains list configured in the input parameters.

Are the sanctions lists downloaded in real-time?

Yes. Every time the Actor runs, it fetches the latest official XML documents directly from the US Treasury (OFAC), the European Commission (EU), and the United Nations (UN). The lists are parsed and cached in memory once per execution to guarantee maximum efficiency and accurate up-to-date checks.