FreightUtils MCP Server
Related Servers
Alternatives to FreightUtils MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to query and manage logistics shipment data, supporting operations like tracking, quoting, and performance analysis via nine tools backed by a demo dataset or a REST API.9253 npmMIT
- 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
- AlicenseAqualityBmaintenanceEnables optimal freight-mode selection (air, sea-LCL, full container) by solving 3D bin-packing, cost optimization, and delivery-risk analysis behind two tools: solve for deterministic planning and explain for hallucination-proof natural-language narration of results.2MIT
- FlicenseNot gradedqualityDmaintenanceProvides container shipping intelligence for AI agents, enabling demurrage & detention calculations, local charges, inland haulage rates, and CFS tariffs across multiple shipping lines, with pay-per-request USDC payments via x402.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform international trade operations such as calculating landed costs, classifying goods, explaining trade terms, estimating shipping, and converting currencies for Kazakhstan/EAEU/Central Asia trade routes.28 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to pack trucks and shipping containers by generating validated 3D load plans with metrics like LDM, linear feet, and pallet positions through the Hansatic packing API.38 npmMIT
TDQS
Scored across 25 tools
Most tools target clearly different reference domains (HS codes, Incoterms, airlines, airports, UN/LOCODE), and the descriptions are strong. However, the calculator family has heavy overlap—consignment_calculator, shipment_summary, cbm_calculator, ldm_calculator, and chargeable_weight_calculator all cover similar CBM/LDM/chargeable-weight ground—and validate/resolve_reference both touch identifier parsing. An agent needs to read the descriptions very carefully to avoid selecting the wrong tool.
Most names follow a clear domain_operation pattern: *_lookup and *_calculator are used predictably for the majority of tools. However, validate, resolve_reference, nearest_airport, shipment_summary, and get_subscribe_link break the pattern, and adr_lq_eq_check uses an awkward long-form. The convention is readable and mostly consistent, with only a few clear outliers.
25 tools sits right at the heavy end of the appropriate range, and many are individually justifiable for a broad freight-utilities server. The count feels a bit inflated by a family of overlapping calculators plus a composite shipment_summary, and get_subscribe_link is a meta-utility rather than a freight domain tool. Consolidating the calculator family or trimming niche helpers would produce a tighter tool set.
The server covers a wide range of freight logistics use cases: HS codes, duties, Incoterms, reference lookups, pallet/container/aircraft capacity, packaging dimensions, ADR dangerous-goods checks, identifier validation, and emissions. It is missing any rate/quote/tracking tools and geocoding/routing capability, but these seem outside the stated utility scope. The minor gaps are mostly optional add-ons, and an agent can complete standard freight logistics calculations without dead ends.