Logistics Freight Intelligence MCP Server

Logistics freight intelligence for AI agents — this MCP server delivers real-time route disruption forecasting, trade sanctions screening, freight cost volatility analysis, and border delay prediction through 8 specialized tools. It is built for 3PLs, customs brokers, supply chain analysts, and freight forwarders who need structured risk data integrated directly into their AI workflows.

The server orchestrates 9 authoritative data sources in parallel — NOAA, GDACS, OFAC, OpenSanctions, UN COMTRADE, Exchange Rates, BLS, World Bank, and OECD — and synthesizes each query into a scored, labeled result. Every response includes a numeric risk score (0-100), a categorical verdict, and a list of plain-language signals that explain the rating. No subscriptions, no API keys to manage, no dashboards to configure — connect your MCP client and start querying.

What data can you access?

Why use the Logistics Freight Intelligence MCP Server?

Building supply chain risk into an AI agent today means stitching together six or more APIs, normalizing their schemas, writing scoring logic, and keeping credentials fresh — before writing a single line of business logic. That is typically two to four weeks of engineering work for a dataset that changes daily.

This MCP server eliminates that build time. Connect it to Claude Desktop, Cursor, or any MCP-compatible client and your agent can call structured freight intelligence tools the same way it calls a calculator. The server handles parallel data fetching, normalization, and risk scoring transparently.

• Scheduling — run daily route disruption sweeps or weekly carrier screenings via Apify's built-in scheduler with zero infrastructure
• API access — trigger any tool programmatically from Python, JavaScript, or any HTTP client using the Apify API
• No credential management — all 9 underlying data sources are accessed through Apify's actor infrastructure; no API keys required beyond your Apify token
• Monitoring — receive Slack or email alerts when a supply chain vulnerability score crosses a defined threshold via Apify webhooks
• Integrations — pipe results into Zapier, Make, HubSpot, or any webhook-compatible destination for downstream logistics workflows

Features

• 8 purpose-built MCP tools covering route disruption, trade compliance, carrier risk, freight cost volatility, border delay prediction, sanctions cargo screening, route comparison, and comprehensive vulnerability assessment
• 9 parallel data sources fetched simultaneously per query using Promise.all — NOAA, GDACS, OFAC, OpenSanctions, UN COMTRADE, Exchange Rate Tracker, BLS, World Bank, and OECD
• Herfindahl-Hirschman Index (HHI) trade concentration scoring — calculates market concentration across trade partners; HHI above 2,500 flags highly concentrated supply chains
• 12 logistics-relevant weather threat types screened per NOAA alert: storm, flood, hurricane, tornado, blizzard, ice, wind, fog, snow, freeze, heat, and dust
• Compound hazard detection — concurrent extreme weather and active disaster events trigger a cascading disruption multiplier on top of individual scores
• OFAC match confidence thresholding — only matches scoring 70+ (compliance) or 60+ (border delay) count as sanction hits, reducing false positives
• 8 sanctioned jurisdiction flags in trade route analysis: Iran, North Korea, Syria, Cuba, Crimea, Russia, Myanmar, and DPRK
• Weighted composite scoring — Supply Chain Vulnerability Score aggregates route disruption (25%), trade compliance (30%), freight cost (25%), and border delay (20%)
• 5-level categorical verdicts with plain-language signals at every dimension: CLEAR/MINOR/MODERATE/SEVERE/CRITICAL for disruption; COMPLIANT through BLOCKED for compliance; STABLE through EXTREME for cost volatility
• Carrier risk assessment uses a 60/40 compliance-to-cost weighting model producing ACCEPTABLE, ELEVATED, or HIGH_RISK determinations
• Route comparison engine accepts 2-5 trade routes, scores each across all dimensions, and returns a ranked list with the lowest-risk recommendation
• Spending limit enforcement — every tool call checks the Apify charge limit before fetching data, preventing budget overruns
• Standby mode server — runs as a persistent HTTP server on the Apify platform, enabling sub-second MCP handshakes for client connections

Use cases for logistics freight intelligence

Trade route optimization for supply chain teams

Supply chain analysts comparing shipping corridors need objective, multi-dimensional risk data to justify route decisions to leadership. The compare_trade_routes tool accepts up to 5 routes — such as US-Shanghai, US-Rotterdam, and US-Mumbai — and returns a ranked comparison across disruption, compliance, cost volatility, and border delay. The recommendation field surfaces the lowest-composite-risk route automatically.

Sanctions compliance for customs brokers and freight forwarders

Customs brokers screening hundreds of shipments per week face serious liability if a consignee or shipper appears on the OFAC SDN list or international watchlists. The sanctions_cargo_check tool screens entities and optionally their destination country against both OFAC and OpenSanctions simultaneously, returning a match count, compliance level, and the specific signals that triggered the result.

Freight cost forecasting and hedging

CFOs and logistics finance teams need forward-looking freight cost signals before locking in rates or currency hedges. The freight_cost_volatility tool combines currency coefficient-of-variation analysis, BLS fuel and transportation PPI data, and OECD trade volume indicators to produce a volatility score and regime label — from STABLE through EXTREME — with specific signals explaining which driver is dominant.

Border delay planning for just-in-time operations

Manufacturers running lean inventory models cannot absorb unexpected customs delays. The border_delay_predictor tool forecasts delay risk at a specific crossing or port by combining real-time NOAA and GDACS alerts with sanctions-screening backlog indicators, giving procurement teams time to pre-clear documentation or route around affected crossings.

Carrier due diligence for procurement teams

Procurement teams onboarding new logistics partners need evidence that a carrier is not sanctions-exposed and operates in economically stable corridors. The carrier_risk_assessment tool produces a composite carrier risk score from sanctions screening (OFAC + OpenSanctions + COMTRADE) and economic stability (BLS transportation PPI), delivering a defensible ACCEPTABLE, ELEVATED, or HIGH_RISK determination.

Supply chain resilience reporting

Risk management teams preparing quarterly resilience reports for leadership, insurers, or regulators need a single, defensible vulnerability number with supporting evidence. The supply_chain_vulnerability tool runs all 9 data sources against a trade entity or corridor and returns the full composite breakdown, dimensional scores, all signals, and specific recommendations — ready to paste into a board deck or audit report.

How to use the Logistics Freight Intelligence MCP Server

1. Connect your MCP client — Add the server URL https://logistics-freight-intelligence-mcp.apify.actor/mcp to your MCP client configuration. For Claude Desktop, add it under mcpServers in claude_desktop_config.json. Include your Apify API token as a Bearer header.
2. Choose a tool — Ask your AI assistant a natural language question such as "What is the route disruption risk for the Gulf Coast freight corridor?" or "Screen Meridian Cargo Solutions against OFAC and OpenSanctions." The assistant will select the appropriate tool automatically.
3. Review the structured response — Each tool returns a numeric score, a categorical label, and a list of specific signals explaining the rating. The supply_chain_vulnerability tool also returns actionable recommendations.
4. Automate recurring checks — Use Apify's scheduler to run vulnerability assessments on a daily or weekly cadence. Set webhooks to notify your team when scores cross a risk threshold.

MCP tools

Tool parameter details

Input examples

Screen a trade entity for sanctions and compliance:

{
  "tool": "trade_compliance_screen",
  "arguments": {
    "entity": "Meridian Cargo Solutions GmbH",
    "commodity": "electronics"
  }
}

Compare three trade routes:

{
  "tool": "compare_trade_routes",
  "arguments": {
    "routes": ["US-Shanghai", "US-Rotterdam", "US-Mumbai"]
  }
}

Full supply chain vulnerability assessment:

{
  "tool": "supply_chain_vulnerability",
  "arguments": {
    "entity": "Taiwan Strait electronics corridor"
  }
}

Output example

The following is a representative response from supply_chain_vulnerability for a high-risk trade entity:

{
  "entity": "Taiwan Strait electronics corridor",
  "compositeScore": 63,
  "verdict": "HIGH_RISK",
  "routeDisruption": {
    "score": 48,
    "weatherAlerts": 7,
    "disasterCount": 2,
    "disruptionLevel": "MODERATE",
    "signals": [
      "7 weather alerts — widespread logistics impact",
      "2 high-severity disasters — supply chain infrastructure at risk"
    ]
  },
  "tradeCompliance": {
    "score": 72,
    "sanctionHits": 1,
    "tradePartnerHHI": 2810,
    "complianceLevel": "HIGH_RISK",
    "signals": [
      "1 sanctions/watchlist matches — trade compliance review required",
      "Trade HHI 2810 — highly concentrated supply chain"
    ]
  },
  "freightCost": {
    "score": 55,
    "currencyVolatility": 25,
    "commodityPressure": 16,
    "economicStress": 10,
    "volatilityLevel": "MODERATE",
    "signals": [
      "Currency CV 6.4% — high freight cost uncertainty",
      "PPI 8.2% — producer cost inflation impacts freight rates"
    ]
  },
  "borderDelay": {
    "score": 44,
    "weatherDisruptions": 4,
    "complianceRisk": 1,
    "delayLevel": "MODERATE",
    "signals": [
      "4 severe weather/disaster events — port/border closure risk",
      "1 watchlist flags — customs enhanced screening delays likely"
    ]
  },
  "allSignals": [
    "7 weather alerts — widespread logistics impact",
    "2 high-severity disasters — supply chain infrastructure at risk",
    "1 sanctions/watchlist matches — trade compliance review required",
    "Trade HHI 2810 — highly concentrated supply chain",
    "Currency CV 6.4% — high freight cost uncertainty",
    "PPI 8.2% — producer cost inflation impacts freight rates",
    "4 severe weather/disaster events — port/border closure risk",
    "1 watchlist flags — customs enhanced screening delays likely"
  ],
  "recommendations": [
    "Highly concentrated supply chain — diversify sourcing to reduce dependency"
  ]
}

Output fields

Vulnerability score reference

How much does it cost to run logistics freight intelligence queries?

This MCP server uses pay-per-event pricing — each tool call costs $0.045. Compute costs are included. You are only charged when a tool is successfully invoked; connection and idle time are free.

You can set a maximum spending limit per run to control costs. The server stops charging when your budget is reached. Apify's free plan includes $5 of monthly credits — enough for approximately 111 tool calls per month at no charge.

Compare this to enterprise TMS platforms such as Oracle Transportation Management or SAP TM at $2,000-5,000/month, or standalone sanctions screening services like World-Check at $500-1,500/month. With this MCP, most logistics teams spend $5-20/month with no subscription commitment.

How to connect this MCP server

Claude Desktop

Add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "logistics-freight-intelligence": {
      "url": "https://logistics-freight-intelligence-mcp.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_APIFY_TOKEN"
      }
    }
  }
}

Cursor / Windsurf / Cline

Point your MCP client configuration to:

https://logistics-freight-intelligence-mcp.apify.actor/mcp

Include your Apify API token as a Bearer authorization header. The server speaks the standard MCP Streamable HTTP transport protocol and is compatible with any spec-compliant client.

Python

import httpx

MCP_URL = "https://logistics-freight-intelligence-mcp.apify.actor/mcp"
APIFY_TOKEN = "YOUR_APIFY_TOKEN"

headers = {
    "Content-Type": "application/json",
    "Authorization": f"Bearer {APIFY_TOKEN}",
}

# Screen a trade entity for sanctions and compliance
payload = {
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params": {
        "name": "trade_compliance_screen",
        "arguments": {
            "entity": "Meridian Cargo Solutions GmbH",
            "commodity": "electronics"
        }
    },
    "id": 1
}

response = httpx.post(MCP_URL, json=payload, headers=headers)
result = response.json()

content = result["result"]["content"][0]["text"]
import json
data = json.loads(content)

print(f"Compliance level: {data['complianceLevel']}")
print(f"Sanction hits: {data['sanctionHits']}")
print(f"Trade HHI: {data['tradePartnerHHI']}")
for signal in data["signals"]:
    print(f"  - {signal}")

JavaScript

const MCP_URL = "https://logistics-freight-intelligence-mcp.apify.actor/mcp";
const APIFY_TOKEN = "YOUR_APIFY_TOKEN";

async function assessSupplyChainVulnerability(entity) {
  const response = await fetch(MCP_URL, {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
      "Authorization": `Bearer ${APIFY_TOKEN}`,
    },
    body: JSON.stringify({
      jsonrpc: "2.0",
      method: "tools/call",
      params: {
        name: "supply_chain_vulnerability",
        arguments: { entity },
      },
      id: 1,
    }),
  });

  const result = await response.json();
  const data = JSON.parse(result.result.content[0].text);

  console.log(`Entity: ${data.entity}`);
  console.log(`Composite score: ${data.compositeScore} — ${data.verdict}`);
  console.log(`Route disruption: ${data.routeDisruption.disruptionLevel}`);
  console.log(`Trade compliance: ${data.tradeCompliance.complianceLevel}`);
  console.log(`Freight cost: ${data.freightCost.volatilityLevel}`);
  console.log(`Border delay: ${data.borderDelay.delayLevel}`);
  for (const rec of data.recommendations) {
    console.log(`Recommendation: ${rec}`);
  }
}

assessSupplyChainVulnerability("Taiwan Strait electronics corridor");

cURL

# Screen a carrier for sanctions and economic risk
curl -X POST "https://logistics-freight-intelligence-mcp.apify.actor/mcp" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -d '{
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params": {
      "name": "carrier_risk_assessment",
      "arguments": {
        "carrier": "Pinnacle Freight Services Ltd"
      }
    },
    "id": 1
  }'

# Compare trade routes
curl -X POST "https://logistics-freight-intelligence-mcp.apify.actor/mcp" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -d '{
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params": {
      "name": "compare_trade_routes",
      "arguments": {
        "routes": ["US-Shanghai", "US-Rotterdam", "US-Mumbai"]
      }
    },
    "id": 2
  }'

How the Logistics Freight Intelligence MCP works

Data collection phase

When a tool call is received, the server immediately fans out to the relevant data sources using Promise.all — all actor calls execute in parallel with a 120-second timeout and 512 MB memory allocation each. For supply_chain_vulnerability, all 9 actors run simultaneously: NOAA and GDACS for weather and disaster data, OFAC and OpenSanctions for sanctions screening, UN COMTRADE for bilateral trade flow analysis, Exchange Rate Tracker for currency data, and BLS, World Bank, and OECD for economic indicators. Focused tools like route_disruption_forecast call only the 2 actors relevant to that dimension.

Risk scoring phase

Each dimension runs a dedicated scoring model with explicit weightings and capped sub-scores to prevent any single signal from dominating.

Route Disruption scores up to 40 points from NOAA (10 points per extreme alert, 4 per severe, capped at 40), up to 30 from GDACS (10 per red/orange disaster, 3 per event, capped at 30), and up to 30 from compound hazard detection — concurrent extreme weather and active disasters trigger a 15-point cascading multiplier.

Trade Compliance applies OFAC confidence thresholding at 70+ and OpenSanctions dataset-membership testing (up to 35 points), calculates trade partner HHI from COMTRADE bilateral flows with thresholds at 1,000, 1,500, and 2,500 (up to 30 points), checks all trade partners against 8 sanctioned jurisdictions (up to 20 points), and adds a 15-point composite penalty for coincident sanctions hits and risky routes.

Freight Cost Volatility computes the coefficient of variation across exchange rate samples — CV above 5% triggers a 25-point currency signal (up to 30 points), BLS PPI and fuel series above threshold values add up to 25 points, and OECD/World Bank trade indicators add up to 25 points, with a 20-point composite bonus for coincident currency and economic stress.

Border Delay combines weather severity and disaster alert levels at the crossing location (up to 35 points), compliance screening risk from watchlist flags (up to 35 points), and a 30-point combined delay multiplier for concurrent weather and compliance exposure.

Composite assembly

The four dimension scores are combined with fixed weights: trade compliance (30%), route disruption (25%), freight cost (25%), and border delay (20%). The resulting composite score maps to five verdict levels: LOW_RISK (0-19), MANAGEABLE (20-39), ELEVATED (40-59), HIGH_RISK (60-79), and CRITICAL (80-100). Recommendations are appended only when specific critical thresholds are crossed — CRITICAL disruption level, BLOCKED compliance level, EXTREME cost volatility, or SEVERE border delays — keeping the output actionable rather than verbose.

Tips for best results

1. Use supply_chain_vulnerability for initial assessment, then drill down. Run a full composite assessment first to identify which dimensions are elevated, then call the focused tools (route_disruption_forecast, trade_compliance_screen, etc.) with more specific parameters to get deeper signal data on problem areas.

2. Provide specific region names for weather tools. "Gulf Coast" and "US-Mexico border Laredo crossing" return more targeted NOAA alerts than "USA". For maritime routes, use port names or sea regions such as "South China Sea" or "Strait of Hormuz".

3. Include HS commodity codes in trade compliance queries. Passing commodity: "8471" (computers) alongside an entity name pulls COMTRADE bilateral flows for that specific commodity class, improving HHI accuracy for commodity-specific supply chains.

4. Combine with route comparison before locking in rates. Run compare_trade_routes with your shortlisted corridors before committing to a freight contract. The output ranks routes by composite risk and identifies which dimension is the differentiating factor.

5. Schedule daily disruption forecasts for critical corridors. Use Apify's scheduler to run route_disruption_forecast on your key corridors every morning. Set a webhook to fire a Slack notification when the disruption level reaches SEVERE or CRITICAL.

6. Screen carriers quarterly, not just at onboarding. Sanctions exposure changes. A carrier that was COMPLIANT six months ago may have appeared on a watchlist since. carrier_risk_assessment costs $0.045 — screening your top 20 carriers monthly costs $0.90.

7. Use sanctions_cargo_check with the destination parameter. Screening the destination country separately catches route-based sanctions exposure that entity-only screening misses — for example, a legitimate shipper routing cargo through a sanctioned intermediary port.

Combine with other MCP servers and Apify actors

Limitations

• No real-time container or vessel tracking. This server provides risk intelligence for routes and entities, not live container positions or AIS vessel data. For real-time tracking, use dedicated platforms such as project44 or FourKites.
• NOAA weather coverage is strongest for US and coastal regions. International inland freight corridors (e.g., Central Asia road routes) may return fewer weather alerts than equivalent US corridors.
• OFAC and OpenSanctions match confidence is approximate. The scoring models use name-matching algorithms from the underlying actors. Ambiguous entity names with common words may produce false positives; always confirm matches through official OFAC resources before halting shipments.
• UN COMTRADE data has a reporting lag. Most COMTRADE bilateral trade data is reported with a 3-6 month delay. The HHI analysis reflects recent-but-not-current trade flows; it is a structural risk indicator, not a real-time flow sensor.
• Exchange rate volatility is calculated from available samples. The coefficient-of-variation calculation requires at least 2 rate samples; queries returning a single rate will show a conservative low volatility score rather than an error.
• The server requires an active Apify account and token. There is no anonymous access. Apify's free plan provides $5/month in credits, which covers approximately 111 tool calls.
• Results are advisory, not legal compliance certification. The trade_compliance_screen and sanctions_cargo_check outputs are risk-scoring tools to prioritize review. They do not constitute a legal compliance determination. Consult qualified trade counsel before halting shipments based solely on these scores.
• compare_trade_routes accepts a maximum of 5 routes per call. For larger route sets, make multiple calls and compare composite scores manually.

Integrations

• Apify API — call any MCP tool programmatically from Python, JavaScript, or cURL; pipe results into internal dashboards or TMS systems
• Webhooks — trigger Slack, email, or PagerDuty alerts when a supply chain vulnerability score crosses a defined threshold
• Zapier — connect route disruption forecasts to automated freight booking workflows or procurement notifications
• Make — build no-code supply chain monitoring pipelines that check sanctions and weather before triggering purchase orders
• LangChain / LlamaIndex — wrap MCP tool calls as LangChain tools or LlamaIndex query engines for logistics-aware RAG applications
• Claude Desktop — ask natural language questions about route risk, carrier compliance, and cost volatility directly in the Claude interface

Troubleshooting

• Tool returns empty signals despite expected risk — The underlying actors query public APIs that may return no matching records for uncommon entity names or very specific region strings. Try broader search terms: use "Mexico border" instead of a specific crossing name, or the country name instead of a city. If the issue persists, enable run sharing in your Apify account settings so the actor developer can inspect the underlying actor call outputs.

• compare_trade_routes response is slow — This tool runs parallel actor calls for each route sequentially (due to the for-loop in the route comparison logic), which means comparing 5 routes involves up to 30 individual actor calls. Allow 60-90 seconds for a 5-route comparison. For faster results, limit comparisons to 3 routes.

• Sanctions cargo check flags an entity you believe is clean — OpenSanctions consolidates 40+ watchlists, some of which include broad geographic or sectoral designations. Check the signals array for which specific list triggered the match. If the match is a false positive from a common name, use the commodity parameter to narrow the COMTRADE context and re-run.

• freight_cost_volatility returns STABLE despite obvious market stress — The currency volatility calculation requires exchange rate samples with measurable variation. If the Exchange Rate Tracker returns a single rate record for the queried corridor, the coefficient of variation defaults to a low score. Try a more specific currency pair in the corridor parameter, such as "USD/EUR" instead of "US-EU".

• MCP client cannot connect — Verify the server URL is https://logistics-freight-intelligence-mcp.apify.actor/mcp and that your Authorization header is formatted as Bearer YOUR_TOKEN (not token YOUR_TOKEN). The server requires POST requests; GET requests return a 405 error by design.

Responsible use

• All data sources accessed by this server are publicly available from official government and intergovernmental agencies.
• Sanctions screening results are advisory risk scores, not legal determinations. Consult qualified export control and trade sanctions counsel before taking compliance action.
• Do not use this server to circumvent or identify gaps in sanctions enforcement. Comply with OFAC, EU, UN, and all applicable sanctions regimes.
• Respect the terms of service of underlying data providers: NOAA, GDACS, UN COMTRADE, BLS, World Bank, and OECD.
• For guidance on web scraping and data use legality, see Apify's guide.

FAQ

How is the Logistics Freight Intelligence MCP different from a TMS or freight platform? Traditional TMS platforms like Oracle TM or SAP TM manage bookings, execution, and visibility. This MCP provides risk intelligence inputs — sanctions screening, route disruption scoring, cost volatility forecasting — designed to be consumed by AI agents and custom applications, not as a standalone interface. It costs cents per query instead of thousands per month.

How many logistics intelligence queries can I run per month on the free plan? Apify's free plan includes $5 of monthly credits. At $0.045 per tool call, that covers approximately 111 tool calls per month with no payment required. You can set a per-run spending limit to prevent accidental overruns.

Does the logistics freight intelligence scoring use real-time data? NOAA weather alerts and GDACS disaster events are fetched live at query time, reflecting current active alerts. Exchange rates are also live. BLS, OECD, and World Bank data updates on their respective publication schedules — typically monthly to quarterly — so economic indicators reflect recent but not real-time conditions. UN COMTRADE bilateral trade data has a 3-6 month reporting lag.

Can I use this MCP for OFAC compliance auditing? The sanctions_cargo_check and trade_compliance_screen tools are risk-scoring tools that help prioritize review. They cross-reference OFAC and OpenSanctions data but do not constitute a formal OFAC compliance program. Use the outputs to flag entities for human review, not as a standalone audit record.

How does the trade concentration HHI work? The Herfindahl-Hirschman Index is calculated from UN COMTRADE bilateral trade flows for the queried entity. Each trade partner's share of total trade value is squared and summed. An HHI above 2,500 indicates a highly concentrated supply chain (a single partner dominates). Above 1,500 flags moderate concentration. Below 1,000 indicates a diversified trade base.

Can the logistics freight intelligence MCP predict specific shipment delays in days? No. The border delay predictor returns a risk level and contributing signals, not a specific delay duration in hours or days. It indicates the probability and severity of delay at a crossing based on current weather, disaster, and compliance conditions — a SEVERE rating means significant delays are likely, not a specific ETA impact.

Is it legal to use publicly available sanctions and trade data for screening? Yes. OFAC publishes the SDN list specifically for compliance use. OpenSanctions aggregates publicly available government watchlists. UN COMTRADE provides open trade statistics. All data sources in this server are designed for public access and commercial use within their terms of service.

What happens if a tool call hits the spending limit? Each tool checks the Apify per-run charge limit before executing. If the limit is reached, the tool returns a JSON error message — {"error": true, "message": "Spending limit reached for [tool_name]"} — rather than failing silently. No data fetching occurs after the limit is reached.

Can I run logistics freight intelligence queries on a schedule? Yes. Use Apify's built-in scheduler to run the actor (which starts the MCP server) on any cron schedule. Combine with webhooks to receive alerts when scores cross thresholds. Daily route disruption sweeps and weekly carrier compliance checks are common patterns.

How does the carrier risk assessment differ from a full sanctions check? carrier_risk_assessment is a composite 60/40 model combining compliance risk (OFAC + OpenSanctions + COMTRADE) and economic stability risk (BLS transportation PPI). It is designed for carrier onboarding decisions. sanctions_cargo_check is narrower — it screens a specific entity and optional destination purely against OFAC and OpenSanctions, optimized for per-shipment screening workflows.

Which AI assistants and coding tools support this MCP server? The server uses the standard MCP Streamable HTTP transport. It is compatible with Claude Desktop, Cursor, Windsurf, Cline, Continue, and any other MCP-compliant client. It also works with programmatic MCP integrations via Python or JavaScript using standard HTTP POST requests.

How does the compound hazard detection work in route disruption scoring? When both NOAA extreme weather alerts and GDACS red/orange disaster events are active simultaneously for the queried region, the scoring model adds a 15-point cascading multiplier on top of the individual weather and disaster scores. This reflects the empirical observation that concurrent severe weather and active disasters create non-linear freight disruption — airports close, road crews are diverted, and port operations halt together rather than independently.

Help us improve

If you encounter unexpected results or empty responses, you can help resolve issues faster by enabling run sharing:

1. Go to Account Settings > Privacy
2. Enable Share runs with public Actor creators

This lets the actor developer inspect the underlying actor call outputs when something goes wrong. Your data is only visible to the actor developer, not publicly.

Support

Found a bug or have a feature request? Open an issue in the Issues tab on this actor's page. For custom integrations, additional data sources, or enterprise logistics workflows, reach out through the Apify platform.