SupplyMaven API Pro
OfficialRelated Servers
Alternatives to SupplyMaven API Pro
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceOcean and multimodal freight intelligence suite providing cross-validated rates, total landed cost, transit reliability, customs, risk, emissions, and unified ship decisions through 47 tools.477 npmMIT

Datalastic MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables real-time vessel tracking, port data, maritime weather, and maritime intelligence through 25 tools, allowing AI clients to query live vessel positions, registry, port info, area searches, weather, and more.MIT- FlicenseNot gradedqualityCmaintenanceProvides AI agents with geopolitical risk intelligence, calibrated forecasts, sanctions and trade-control data, and live maritime chokepoint traffic across 60 countries, with source-linked answers.-
- AlicenseNot gradedqualityDmaintenanceOcean container shipping intelligence for AI agents — D\&D tariffs, freight rates, vessel schedules, port congestion, inland haulage across 6 major carriers. 24 MCP tools.MIT
- FlicenseAqualityBmaintenanceMCP server that exposes tools for monitoring supply chain disruptions, including vessel positions, port weather, congestion, and news. Includes an AI agent that synthesizes these sources to assess route risks.5-
- AlicenseNot gradedqualityCmaintenanceAgent-ready economic, market & geo-health intelligence — 163 MCP tools, 155 driver-backed indices.MIT
TDQS
Scored across 34 tools
While most tools have distinct purposes, there is some overlap between tools like `commodity_price_monitor` and `get_commodity_volatility_alerts`, and between `get_disaster_events` and `get_natural_disaster_alerts`. However, descriptions clarify their different focuses, so ambiguity is minimal.
Naming conventions are mixed: many tools follow a `get_` prefix pattern, but several others use noun-first names like `commodity_price_monitor` or `port_congestion_monitor`. This inconsistency could cause minor confusion, but the names are still descriptive enough.
With 34 tools, the server is comprehensive but slightly heavy. Each tool justifies its existence by covering a specific data point or analysis, but the set could be streamlined without losing functionality. Still, the scope of supply chain monitoring warrants this many tools.
The toolset is remarkably complete for a supply chain risk monitoring API. It covers commodities, ports, borders, chokepoints, rail, air cargo, freight rates, economic indicators, manufacturing, disasters, policy, predictive signals, and synthesized briefs. No obvious gaps are apparent for the stated domain.