Export Control Screening MCP Server

> View on ApifyForge | Use on Apify Store

---

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf):

{
  "mcpServers": {
    "export-control-screening-mcp": {
      "url": "https://ryanclinton--export-control-screening-mcp.apify.actor/mcp"
    }
  }
}

---

Export control screening MCP that checks transaction parties, classifies dual-use technologies, and detects diversion routes — all from a single MCP tool call. Built for export compliance officers, defense contractors, semiconductor companies, and customs brokers who need fast, evidence-backed screening decisions.

This MCP server orchestrates 7 live data sources in parallel: OFAC SDN list, OpenSanctions (100+ jurisdictions), UN COMTRADE trade flows, USPTO patent database, Federal Register, Congress Bills, and REST Countries. Four independent scoring models — transaction risk, dual-use classification, diversion detection, and regulatory change velocity — combine into a composite export compliance verdict: APPROVED, LICENSE_REQUIRED, ENHANCED_REVIEW, or DENIED.

What data can you access?

| Data Point | Source | Example |
|---|---|---|
| 📋 OFAC SDN list screening | US Treasury OFAC | "Huawei Technologies Co. Ltd — Entity List" |
| 🌐 Global denied party lists | OpenSanctions (100+ lists) | "Mfang Group — EU restrictive measures" |
| 📦 International trade flow data | UN COMTRADE | 42 flows via UAE hub — transshipment flag |
| 📄 CCL/EAR dual-use classification | USPTO Patent Database | "Cat 5 — Information Security (encryption)" |
| 📰 BIS rules and EAR amendments | Federal Register | "EAR Part 744 Entity List Amendment — Apr 2025" |
| 🏛️ Export control legislation | Congress Bills | "CHIPS Act expansion — S.3892, passed Senate" |
| 🗺️ Country risk profiles | REST Countries | Russia — sanctioned, arms embargo, Entity List |
| 🔴 Transaction Risk Score | Composite (0-100) | Score: 87 — BLOCKED (OFAC match) |
| 🟡 Dual-Use Classification Level | Patent scoring model | CONTROLLED — BIS export license required |
| 🔵 Diversion Route Level | COMTRADE anomaly model | SUSPICIOUS — 5 transshipment hub flows |
| 🟢 Regulatory Change Velocity | Federal Register + Congress | HIGH — 4 final rules, 2 enacted bills |
| ✅ Composite Verdict | Weighted 4-model composite | DENIED — composite score 78/100 |

Why use Export Control Screening MCP?

Manual export compliance checks are slow, inconsistent, and expensive. An in-house compliance team manually cross-referencing OFAC, OpenSanctions, COMTRADE, and the Federal Register for a single transaction takes 4-8 hours and requires specialist knowledge of EAR categories, CCL taxonomy, and COMTRADE data formats. Dedicated compliance platforms like Visual Compliance or MK Denial charge $500-2,000/month for similar coverage.

This MCP automates the entire multi-source screening workflow in seconds. Connect it to Claude, Cursor, or any MCP-compatible AI client, then ask in plain English: "Is Shenzhen Microtek safe to export AI chips to?" The MCP handles all 7 data source queries, applies scoring models, and returns a structured verdict with the evidence trail.

Platform benefits:
- Scheduling — run recurring screenings on counterparty watchlists daily or weekly
- API access — trigger screenings programmatically from Python, JavaScript, or any HTTP client
- Standby mode — the server stays warm between requests, eliminating cold-start delays
- Monitoring — get Slack or email alerts when screenings produce DENIED or HIGH risk results
- Integrations — connect to Zapier, Make, Google Sheets, or trade compliance systems via webhooks

Features

- 7 live data sources queried in parallel using Promise.allSettled, so a single unavailable source never blocks the result
- OFAC SDN screening — any match scores 20 points per hit (up to 40) and immediately triggers BLOCKED status and DENIED verdict
- OpenSanctions consolidation — screens against 100+ global denied party lists, EU/UN/OFAC/UK combined, scoring up to 25 points per run
- Country risk tiering — three-tier country classification: sanctioned (Cuba, Iran, DPRK, Syria, Russia: +10 pts), arms embargo (+5 pts), Entity List concern countries including China, UAE, Pakistan, Myanmar (+3 pts)
- Dual-use patent taxonomy — maps USPTO patent text against 35 CCL-relevant keyword patterns across 10 EAR categories (Cat 0 Nuclear, Cat 1 Special Materials, Cat 2 Materials Processing, Cat 3 Electronics, Cat 4 Computers, Cat 5 Information Security, Cat 6 Sensors, Cat 7 Navigation, Cat 8 Marine, Cat 9 Aerospace)
- 5-level classification output — UNRESTRICTED, COMMERCIAL, DUAL_USE, CONTROLLED, MILITARY with critical-category bonuses for nuclear (+10) and biological (+10) technology
- COMTRADE diversion detection — analyzes UN trade flow records for sanctioned destinations, 9 known transshipment hubs (UAE, Malaysia, Singapore, Hong Kong, Turkey, Georgia, Armenia, Kyrgyzstan, Uzbekistan), and unit price anomalies (under $0.01 or over $100,000) indicating potential misclassification
- Trade network layering detection — partner count above 8 countries flags potential layering structures in distribution networks
- Regulatory velocity scoring — counts Federal Register proposed rules (3 pts), final rules (5 pts each), and congressional bill status (passed/enrolled/enacted: 8 pts each) to produce a change level: STATIC through CRITICAL
- 4-model composite score — weighted formula: transaction risk 35% + dual-use 25% + diversion 25% + regulatory 15%
- Structured verdict with blockers and required actions — output includes separate requiredActions and blockers arrays so compliance teams know exactly what steps to take next
- Spending limit enforcement — every tool call checks Actor.charge event limits before executing, preventing budget overruns in automated workflows

Use cases for export control screening

Pre-transaction party screening

Export compliance officers at manufacturers and distributors need to screen every buyer, freight forwarder, and end-user before processing an order. Manual cross-referencing of OFAC, BIS Entity List, and EU consolidated lists takes hours per transaction. Use screen_transaction_parties to get a Transaction Risk Score and full OFAC/OpenSanctions evidence in seconds, then route only flagged transactions for manual review.

AI chip and semiconductor export compliance

Semiconductor companies face rapidly evolving country-level restrictions on advanced computing exports. The check_country_restrictions tool pulls live OFAC and OpenSanctions data alongside country profiles to produce a current sanctions status for any destination. Combine with track_export_regulations on the topic "AI chips semiconductor" to monitor the latest BIS rules affecting advanced computing exports.

Defense contractor ITAR and EAR compliance

Defense contractors sharing technology with international partners must verify both the partner entity and the technology classification before transfer. Use assess_end_use_risk with the partner entity name and technology description to get a combined end-use risk score that cross-references party screening with dual-use patent classification in a single call.

Transshipment and diversion route detection

Trade compliance analysts investigating suspicious order patterns can use detect_diversion_routes on any commodity or HS code. The tool queries UN COMTRADE for recent trade flows, identifies anomalous routing through known transshipment hubs, and flags unit price irregularities that suggest misclassification or underdeclared value — common diversion indicators.

Export control regulatory monitoring

Legal and compliance teams need to track every EAR amendment, Entity List addition, and export control bill in Congress. Use track_export_regulations on topics like "quantum computing," "drone," or "encryption" to get a regulatory velocity score and the full list of recent Federal Register publications and congressional bills affecting that technology area.

Full compliance due diligence for new counterparties

Before entering a new supplier or customer relationship, compliance teams need a complete picture. Use generate_export_compliance_report with the entity name, technology, and destination country. The tool runs all 7 data sources simultaneously and returns a single structured report with composite score, four sub-scores, all risk signals, required actions, and a compliance verdict — everything needed for a compliance file entry.

How to screen for export control compliance

1. Connect the MCP server to your AI client — Add the server URL https://export-control-screening-mcp.apify.actor/mcp to Claude Desktop, Cursor, or any MCP-compatible client. You need an Apify API token (free to create at apify.com).

2. Ask your compliance question in plain English — Type: "Run a full export compliance check on Shenyang Machine Tool Co. for CNC equipment going to Russia." The AI selects and calls the appropriate tool automatically.

3. Review the structured result — The response includes a composite score (0-100), a verdict (APPROVED/LICENSE_REQUIRED/ENHANCED_REVIEW/DENIED), all risk signals, and a list of required actions. DENIED verdicts include specific blockers explaining why.

4. Export or log the result — Copy the JSON response to your compliance management system, or use Apify webhooks to push results directly to your trade compliance platform.

MCP tools

| Tool | Price | Inputs | What it returns |
|------|-------|--------|-----------------|
| screen_transaction_parties | $0.045 | entity, country (opt.) | Transaction Risk Score 0-100, OFAC hits, sanctions hits, risk level, signals |
| classify_technology_risk | $0.045 | technology, domain (opt.) | Dual-use classification level, sensitive patent count, CCL categories matched |
| detect_diversion_routes | $0.045 | commodity, country (opt.) | Diversion level, trade anomaly count, transshipment flags, signals |
| check_country_restrictions | $0.045 | country | Sanctioned flag, OFAC hit count, international sanctions hits, country profile |
| track_export_regulations | $0.045 | topic | Regulatory change level, proposed/final rule counts, bill count, signals |
| assess_end_use_risk | $0.045 | entity, technology | Combined end-use risk score 0-100, transaction risk + dual-use sub-scores |
| generate_export_compliance_report | $0.045 | entity, technology (opt.), destination (opt.) | Full composite report: 4 sub-scores, verdict, required actions, blockers |

Input tips

- Be specific with entity names — "Huawei Technologies Co. Ltd" returns better results than "Huawei." Include country of incorporation if known.
- Use technology descriptions for classification — for classify_technology_risk, use a product description like "fiber optic gyroscope navigation system" rather than a product code.
- Provide destination country for transaction tools — adding the country parameter activates country risk scoring and adds up to 20 points to the transaction risk score.
- Use generate_export_compliance_report for new counterparties — it runs all 7 sources in parallel and is priced the same as individual tool calls.
- Combine tools in sequence — screen the entity first; if CLEAR, classify the technology; only run the full report for borderline or new relationships.

Output example

{
  "entity": "Shenyang Machine Tool Group",
  "compositeScore": 62,
  "verdict": "ENHANCED_REVIEW",
  "transactionRisk": {
    "score": 18,
    "ofacHits": 0,
    "sanctionsHits": 1,
    "countryRiskFlags": 3,
    "riskLevel": "LOW",
    "signals": [
      "1 international sanctions matches — enhanced screening required",
      "Entity List concern country: China"
    ]
  },
  "dualUseClassification": {
    "score": 74,
    "patentCount": 22,
    "sensitivePatents": 9,
    "technologyCategories": [
      "Cat 2 — Materials Processing",
      "Cat 7 — Navigation & Avionics",
      "Cat 3 — Electronics"
    ],
    "classificationLevel": "CONTROLLED",
    "signals": [
      "9 patents with dual-use technology indicators",
      "Technology spans 3 CCL categories: Cat 2 — Materials Processing, Cat 7 — Navigation & Avionics, Cat 3 — Electronics"
    ]
  },
  "diversionRoute": {
    "score": 38,
    "tradeAnomalies": 2,
    "sanctionedDestinations": 0,
    "transshipmentFlags": 4,
    "diversionLevel": "WATCH",
    "signals": [
      "4 trade flows through known transshipment hubs (UAE, Malaysia, Singapore, etc.)",
      "2 trade flows with suspicious unit pricing — potential misclassification"
    ]
  },
  "regulatoryChange": {
    "score": 55,
    "totalRegulations": 8,
    "proposedRules": 3,
    "finalRules": 3,
    "congressBills": 4,
    "changeLevel": "MODERATE",
    "signals": [
      "3 final rules — export control framework tightening",
      "3 proposed rules — additional restrictions incoming",
      "4 export control bills in Congress"
    ]
  },
  "allSignals": [
    "1 international sanctions matches — enhanced screening required",
    "Entity List concern country: China",
    "9 patents with dual-use technology indicators",
    "Technology spans 3 CCL categories",
    "4 trade flows through known transshipment hubs",
    "3 final rules — export control framework tightening"
  ],
  "requiredActions": [
    "BIS export license required before shipment",
    "Enhanced due diligence on all transaction parties",
    "Review ICP for compliance with new regulations"
  ],
  "blockers": []
}

Output fields

| Field | Type | Description |
|-------|------|-------------|
| entity | string | Entity name submitted for screening |
| compositeScore | number | Weighted composite risk score 0-100 (transaction 35%, dual-use 25%, diversion 25%, regulatory 15%) |
| verdict | string | APPROVED / LICENSE_REQUIRED / ENHANCED_REVIEW / DENIED |
| transactionRisk.score | number | Transaction party risk score 0-100 |
| transactionRisk.ofacHits | number | Number of OFAC SDN list matches |
| transactionRisk.sanctionsHits | number | Number of OpenSanctions global list matches |
| transactionRisk.countryRiskFlags | number | Accumulated country risk flag points |
| transactionRisk.riskLevel | string | CLEAR / LOW / MODERATE / HIGH / BLOCKED |
| transactionRisk.signals | array | Human-readable risk signal strings |
| dualUseClassification.score | number | Dual-use technology concern score 0-100 |
| dualUseClassification.patentCount | number | Total patents analyzed |
| dualUseClassification.sensitivePatents | number | Patents with CCL-relevant technology keywords |
| dualUseClassification.technologyCategories | array | EAR CCL category strings matched (e.g., "Cat 5 — Information Security") |
| dualUseClassification.classificationLevel | string | UNRESTRICTED / COMMERCIAL / DUAL_USE / CONTROLLED / MILITARY |
| diversionRoute.score | number | Diversion risk score 0-100 |
| diversionRoute.tradeAnomalies | number | Trade flows with anomalous unit pricing |
| diversionRoute.sanctionedDestinations | number | Trade flows to sanctioned countries |
| diversionRoute.transshipmentFlags | number | Trade flows through known transshipment hubs |
| diversionRoute.diversionLevel | string | NORMAL / WATCH / SUSPICIOUS / LIKELY_DIVERSION / CONFIRMED_DIVERSION |
| regulatoryChange.score | number | Regulatory activity score 0-100 |
| regulatoryChange.totalRegulations | number | Total Federal Register entries found |
| regulatoryChange.proposedRules | number | Proposed rulemaking entries |
| regulatoryChange.finalRules | number | Final rules published |
| regulatoryChange.congressBills | number | Relevant bills found in Congress |
| regulatoryChange.changeLevel | string | STATIC / LOW / MODERATE / HIGH / CRITICAL |
| allSignals | array | Merged signal strings from all four scoring models |
| requiredActions | array | Actionable compliance steps based on findings |
| blockers | array | Hard-stop conditions preventing transaction approval |

How much does export control screening cost?

Export Control Screening MCP uses pay-per-event pricing — you pay $0.045 per tool call. Platform compute costs are included. Every tool, including generate_export_compliance_report, is priced the same.

| Scenario | Tool calls | Cost per call | Total cost |
|----------|-----------|---------------|------------|
| Quick party screen | 1 | $0.045 | $0.045 |
| Screen + classify tech | 2 | $0.045 | $0.09 |
| Full 3-part pre-transaction check | 3 | $0.045 | $0.135 |
| Onboard 10 new counterparties | 10 | $0.045 | $0.45 |
| Monthly screening of 200 watchlist entities | 200 | $0.045 | $9.00 |

You can set a maximum spending limit per run to control costs. The MCP stops when your budget is reached. The Apify Free plan includes $5 of monthly credits, covering over 100 screening calls at no cost.

Compare this to Visual Compliance or MK Denial at $500-2,000/month — with this MCP, a team running 200 screenings per month pays $9.00 with no subscription commitment.

How to connect this MCP server

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "export-control-screening": {
      "url": "https://export-control-screening-mcp.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_APIFY_TOKEN"
      }
    }
  }
}

Cursor / Windsurf / Cline

Add the server URL in your MCP settings panel:

https://export-control-screening-mcp.apify.actor/mcp

Include your Apify API token in the Authorization header. The server uses the MCP Streamable HTTP transport.

Python (Apify Actor API)

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_API_TOKEN")

run = client.actor("ryanclinton/export-control-screening-mcp").call(run_input={})