FreightUtils MCP Server
The neutral freight reference layer for AI agents.
FreightUtils is the neutral freight reference layer for AI agents — source-backed dangerous-goods, customs, location and freight-calculation data an agent can call and cite, from primary sources (ADR 2025 / UNECE, HS 2022 / WCO, IATA-regulated airline prefixes). Neutral by design: no freight to sell and no carrier to push — a lookup returns what the named source says, with the citation attached so an agent can inspect it rather than take our word for it, regardless of who carries the load.
This Model Context Protocol server gives AI agents access to 25 freight calculation and reference tools, covering road, air, and sea freight. Built by a UK ADR-certified freight transport planner.
Every response cites its source — a _source block with the authority, edition, licence where held, and a verification status an agent can read — and the tools are deterministic, not generated answers. Reference only: never filing, booking, or legal advice, and results state when human review is required (validate is structural check-digit validation only; a clean ics2_check is not ENS acceptance; emissions figures are estimates, not audited reports).
Since 2.11.0, every tool also declares a typed outputSchema and returns structuredContent — the FreightUtils v1 response envelope: the answer under result, plus confidence, normalized_input, warnings, _source and a ready-to-use citation. The legacy flat JSON text channel is unchanged (byte-identical), so existing text-parsing consumers are unaffected.
Website: https://www.freightutils.com API Docs: https://www.freightutils.com/api-docs
Tools (25)
Calculators
Dangerous Goods (ADR)
Some UN numbers have more than one ADR Table A row (packing groups, concentration bands). When a bare UN number matches rows that give different answers, the ADR tools never pick one: they withhold the verdict and return the candidate rows, and you pin one with packing_group or variant_index. The rules, with worked cases (UN 1789, UN 1790 PG I, UN 2215 PG III): the ADR 1.1.3.6 calculator in the API docs.
Customs & Tariff
Reference Data
Validation
Composite
Plans
Installation
Claude (claude.ai, desktop and mobile apps, Cowork)
Add FreightUtils from Claude's connector directory: https://claude.ai/directory/connectors/freightutils. Or add it as a custom connector — Customize → Connectors → Add custom connector — with the URL https://www.freightutils.com/api/mcp. No API key, no sign-in. Setup, limits and privacy: freightutils.com/mcp#use-in-claude.
Claude Desktop / Claude Code (stdio)
Add to your MCP config (claude_desktop_config.json or .claude/settings.json):
{
"mcpServers": {
"freightutils": {
"command": "npx",
"args": ["freightutils-mcp"]
}
}
}
Remote HTTP / SSE
If your MCP client supports remote servers, use the canonical URL:
https://www.freightutils.com/api/mcp
The older URL
https://www.freightutils.com/api/mcp/mcpstill works for backwards compatibility with existing clients.
No API key required to get started — anonymous calls work out of the box (see Rate Limits below).
Authenticating with a Pro key
Anonymous usage caps at 25 requests/day per IP. If you have a free or Pro API key, set FREIGHTUTILS_API_KEY in the environment that runs the MCP server. The package reads it from process.env and attaches Authorization: Bearer <key> to every outbound /api/* call — same key the remote https://www.freightutils.com/api/mcp transport already honors.
stdio config example with the env var wired through:
{
"mcpServers": {
"freightutils": {
"command": "npx",
"args": ["freightutils-mcp"],
"env": {
"FREIGHTUTILS_API_KEY": "fu_pk_xxx"
}
}
}
}
Get a key at freightutils.com/api-docs (free, 100/day) or freightutils.com/pricing (Pro, 50,000/month). Backwards compatible — unset env var preserves the existing anonymous behaviour.
With no key set, the server says so once at start-up, on stderr (stdout carries only the MCP protocol), so a key you meant to set and missed shows up in your client's MCP log rather than at the first 429:
freightutils-mcp: FREIGHTUTILS_API_KEY is not set, so calls use the anonymous tier — 25 requests per day per IP address. Set the key to use your plan's limit: https://www.freightutils.com/pricing
Verify your setup
After adding FreightUtils to your MCP client config, fully quit and relaunch the client (Claude Desktop, Cursor, Cline). MCP servers are only loaded at client startup; editing the config in a running session does nothing until restart.
Then run the install diagnostic from a terminal:
npx freightutils-mcp ping
You should see three ticks and All checks passed:
FreightUtils MCP Diagnostic
───────────────────────────
package: freightutils-mcp@<installed version>
health: https://www.freightutils.com/api/mcp/health
[1/3] Backend health (https://www.freightutils.com/api/mcp/health)
✓ status=ok mcp_version=<current> tools_registered=<current> (143ms)
[2/3] MCP handshake (in-process via InMemoryTransport)
✓ server freightutils-mcp@<installed version> initialized; tools/list returned <n> tools
[3/3] End-to-end tool call (cbm_calculator l=120 w=80 h=100)
✓ cbm_calculator → total=0.96 m³ (expected 0.96) (218ms)
All checks passed. Your FreightUtils MCP install is working.
If any check shows ✗, see Troubleshooting below. Exit code is 0 on all-pass and 1 on any failure, so the command works in CI / health-check scripts too.
Troubleshooting
The full diagnostic flow lives at the /api-docs#mcp-setup section on the website. The live backend status is callable from inside any MCP client at GET /api/mcp/health — useful when you don't have shell access during a conversation.
Rate Limits
All tools call the free FreightUtils API:
- Anonymous: 25 requests/day per IP
- Free API key: 100 requests/day (register at https://www.freightutils.com)
- Pro: 50,000 requests/month at £19/month
Security and data
- Read-only. Every tool is a lookup or a calculation, declared
readOnlyHint: trueanddestructiveHint: false. The server changes nothing, anywhere. - No file system, no shell. The server reads no file except its own
package.json, starts no process and opens no port — it talks over stdio only. - One destination. Tool inputs go only to
https://www.freightutils.com/api(or the base you set inFREIGHTUTILS_API_URL), over HTTPS.get_subscribe_linkanswers locally and sends nothing. - The key stays in the environment.
FREIGHTUTILS_API_KEYis read from the environment and sent only as anAuthorization: Bearerheader to that host — never logged, never written to disk, never put in an error message. - stdout is the protocol. Nothing but MCP JSON-RPC goes to stdout; the one start-up notice goes to stderr.
- Two validation layers. Each tool's Zod schema checks types, formats and the API's own limits before any call is made (the three ADR tools —
adr_exemption_calculator,adr_lq_eq_check,shipment_summary— also refuse, by name, a field they do not read). The API then validates every request again on the server and refuses what it cannot answer with a 400 naming the field. - Errors keep their meaning. A failed call is reported by kind: network failure, timeout (30 s, or
FREIGHTUTILS_TIMEOUT_MS), the API's own 4xx refusal, a 429 with itsreset_at, or a 5xx — never with a stack trace, a request header or the contents of a server error page. - Two direct runtime dependencies:
@modelcontextprotocol/sdkandzod. CI fails on any high or critical advisory in the production dependency tree, and Dependabot watches it. - Reporting a vulnerability: see SECURITY.md.
Example Prompts
Once connected, your AI agent can:
- "Calculate CBM for a box 120cm × 80cm × 100cm, 24 pieces"
- "Look up UN 1203 in the ADR database"
- "Check if 200L of petrol qualifies for ADR 1.1.3.6 exemption"
- "Find the HS code for lithium batteries"
- "What does FOB mean in shipping?"
- "How many boxes of 40×30×25cm fit on a euro pallet?"
- "Calculate loading metres for 26 euro pallets on an artic trailer"
- "What's the UK import duty on laptops from China?"
Data Sources
- ADR 2025 — UNECE, ECE/TRANS/352, applicable 1 Jan 2025; given legal effect by EU Directive 2008/68/EC (consolidated). Factual compilation, best-effort — not legal advice, not a regulatory authority.
- HS 2022 — HS 2022 descriptions from UN Comtrade's H6 classification (UN Statistics Division); the WCO maintains the Harmonized System nomenclature. No named open licence.
- Airlines — compiled by FreightUtils from public sources. Verified records cite carrier-published pages and FAA Order JO 7340.2 field by field; the rest are pending verification. IATA and ICAO assign these codes, but this dataset is not published or endorsed by IATA or ICAO, and no licence or "open data" claim is made for it.
- UN/LOCODE 2025-1 — UNECE official release artifact, coordinates strict-validated. UN/LOCODE © UNECE, CC BY 4.0 (as UNECE states for UN/CEFACT standards).
- UK duty — the live GOV.UK Trade Tariff API, pulled per request, so there is no local copy that can drift.
- Containers / ULD / vehicles — ISO, IATA and industry-standard specifications.
- Emissions factors — published DEFRA / EPA / ADEME factors (currently DEFRA 2026 + EPA 2025
- ADEME Base Carbone v23.11), combined by the ISO 14083 / GLEC distance-based method. Estimates, not audited reports.
Public provenance wording is maintained in the FreightUtils repository's
docs/DATA_PROVENANCE.md and copied here, not
written from memory — so a source that is re-attributed there cannot keep being cited here.
Changelog
Release notes: CHANGELOG.md in this repo and GitHub Releases.
A README that carries its own copy of the changelog is why three directories showed 2.4.0 as the latest release for three months after 2.4.0 had been superseded. One source now.
Other ways to use FreightUtils
FreightUtils ships across multiple distribution surfaces. Pick the one that fits how you work:
- Website — interactive tools at freightutils.com
- REST API — 24 endpoints, free tier (100/day) and Pro tier (50K/month, £19/mo). API docs
- MCP server — for LLM agents and AI tooling. npm: freightutils-mcp · MCP Registry
- n8n custom node — for workflow automation. npm: n8n-nodes-freightutils
- Custom GPT — the FreightUtils GPT on the OpenAI GPT Store, backed by the same OpenAPI spec.
Same data, same compliance reference set (ADR 2025, HS 2022, IATA-regulated airline prefixes), every surface kept in sync.
License
MIT — see LICENSE.
Built by Marius Cristoiu, ADR-certified freight transport planner.