Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add freightutils-mcp -- npx -y freightutils-mcp@2.34.2รันในเทอร์มินัล
{ "mcpServers": { "freightutils-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิด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
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.
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.
Add to your MCP config (claude_desktop_config.json or .claude/settings.json):
{
"mcpServers": {
"freightutils": {
"command": "npx",
"args": ["freightutils-mcp"]
}
}
}
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).
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
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.
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.
All tools call the free FreightUtils API:
readOnlyHint: true and destructiveHint: false. The server changes nothing, anywhere.package.json, starts no process and opens no port — it talks over stdio only.https://www.freightutils.com/api (or the base you set in FREIGHTUTILS_API_URL), over HTTPS. get_subscribe_link answers locally and sends nothing.FREIGHTUTILS_API_KEY is read from the environment and sent only as an Authorization: Bearer header to that host — never logged, never written to disk, never put in an error message.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.FREIGHTUTILS_TIMEOUT_MS), the API's own 4xx refusal, a 429 with its reset_at, or a 5xx — never with a stack trace, a request header or the contents of a server error page.@modelcontextprotocol/sdk and zod. CI fails on any high or critical advisory in the production dependency tree, and Dependabot watches it.Once connected, your AI agent can:
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.
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.
FreightUtils ships across multiple distribution surfaces. Pick the one that fits how you work:
Same data, same compliance reference set (ADR 2025, HS 2022, IATA-regulated airline prefixes), every surface kept in sync.
MIT — see LICENSE.
Built by Marius Cristoiu, ADR-certified freight transport planner.
Neutral freight reference + validation layer for AI agents — ADR dangerous goods, HS codes, airlines, airports, UN/LOCODE, Incoterms, identifier validation and freight math. Every tool has a typed out
{ "mcpServers": { "freightutils-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}ภาพรวม
Neutral freight reference + validation layer for AI agents — ADR dangerous goods, HS codes, airlines, airports, UN/LOCODE, Incoterms, identifier validation and freight math. Every tool has a typed output schema and returns a source-cited envelope.
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Freightutils ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-14 Neutral freight reference + validation layer for AI agents — ADR dangerous goods, HS codes, airlines, airports, UN/LOCODE, Incoterms, identifier validation and freight math. Every tool has a typed output schema and returns a source-cited envelope.