Trade-Based Money Laundering Detection

Name: Trade-Based Money Laundering Detection
Author: apifyforge

@apifyforge

Trade-Based Money Laundering Detection について

Trade-based money laundering (TBML) detection for compliance teams, AML investigators, and financial intelligence units — delivered as an MCP server that plugs directly into Claude, Cursor, or any MCP-compatible AI agent.

基本情報

カテゴリ

AI とエージェント

ライセンス

MIT

公開者

apifyforge

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "trade-based-money-laundering-mcp": {
      "url": "https://ryanclinton--trade-based-money-laundering-mcp.apify.actor/mcp"
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Trade-Based Money Laundering Detection?

A Model Context Protocol (MCP) server that automates trade-based money laundering (TBML) detection for compliance teams, AML investigators, and financial intelligence units. It orchestrates 14 data sources and runs five peer-reviewed forensic algorithms to identify over-invoicing, carousel fraud, phantom entities, FX layering, and sanctions-adjacent ownership chains, outputting structured evidence ready for FinCEN SAR filing.

How to use Trade-Based Money Laundering Detection?

Add the server URL to your MCP‑compatible client (Claude Desktop, Cursor, Windsurf) by inserting the following configuration, then invoke any of the eight exposed tools via natural‑language prompts to your AI agent. No code is required from the analyst.

{
  "mcpServers": {
    "trade-based-money-laundering-mcp": {
      "url": "https://ryanclinton--trade-based-money-laundering-mcp.apify.actor/mcp"
    }
  }
}

Key features of Trade-Based Money Laundering Detection

Benford‑Grubbs‑Fisher hybrid invoice anomaly detection
Tarjan SCC + Johnson cycle enumeration for carousel fraud
Logistic regression phantom entity screening
Kolmogorov‑Smirnov FX arbitrage deviation detection
Absorbing Markov chain jurisdictional cascade risk scoring
14 parallel data sources (UN COMTRADE, OFAC, OpenCorporates, etc.)
Composite TBML Risk Score (0–100) with five weighted dimensions
FinCEN SAR Form 111 evidence package aligned with 31 CFR 1020.320

Use cases of Trade-Based Money Laundering Detection

Bank AML compliance and transaction monitoring
Export control and sanctions screening
Financial intelligence unit investigations
Trade finance due diligence

FAQ from Trade-Based Money Laundering Detection

What data sources does the server use?

It queries 14 parallel sources: UN COMTRADE, OpenCorporates, GLEIF LEI, UK Companies House, Canada Corporations, Australia ABN, OFAC SDN, OpenSanctions, Exchange Rate Tracker, Exchange Rate History, WHOIS Domain Lookup, OECD Statistics, IMF Economic Data, and IP Geolocation Lookup.

How much does each tool call cost?

Per‑call fees range from $0.040 to $0.050 depending on the tool: investigate_trade_pair ($0.040), detect_invoice_anomalies ($0.045), map_circular_trade_network ($0.045), verify_counterparty_legitimacy ($0.040), analyze_fx_manipulation ($0.040), screen_ownership_chain ($0.045), compute_tbml_risk_score ($0.045), generate_sar_evidence_package ($0.050).

What regulatory standards does the SAR evidence package comply with?

The generate_sar_evidence_package tool produces evidence categorized by Trade Pricing, Sanctions Exposure, Corporate Opacity, Circular Trade, and FX Manipulation, with severity ratings and specific regulatory references (OFAC EO 13224, CDD Rule 31 CFR 1010.230, FATF TBML Guidance 2020) and a FinCEN filing narrative template.

Are there spending controls to prevent runaway costs?

Yes, each tool call checks eventChargeLimitReached before executing, and you can set a maximum budget per session to control costs during exploratory investigations.

What runtime or dependencies are required?

The server runs on Apify and is accessed via an HTTPS URL. It works with any MCP‑compatible client (Claude Desktop, Cursor, Windsurf) and requires no local installation or dependencies from the analyst.