FreightUtils MCP Server
NPM · FREIGHTUTILS-MCP · 2 COMPONENTS
Neutral freight reference + validation layer for AI agents: ADR, HS, UN/LOCODE, freight math
Available components
Last scanned (1 hour ago)
Scores higher than 95% of npm servers
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to SoapyRED/freightutils-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 22918 tokens (~881/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 99% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Known CVEs: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 770 → 881 ▼ functional
- Schema quality: 770 → 853 ▼ functional
- Schema quality: 19260 → 21188 ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 2.28.0 → 2.32.0 functional
- Package version: 2.28.0 → 2.31.0 functional
- Package version: 2.28.0 → 2.30.0 functional
- Package version: 2.28.0 → 2.29.0 functional
- 4 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Package version: 2.27.0 → 2.28.0 functional
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 0
- Package version: 2.26.0 → 2.27.0 functional
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: 627 → 727 ▼ functional
- Package version: 2.24.0 → 2.26.0 functional
- Package version: 2.24.0 → 2.25.0 functional
- 29 Oct 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.97 → unverified ▼ security
- Stability: 0.97 → pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 2.23.0 → 2.24.0 functional
- 28 Oct 26 +5
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- CVE-2023-54404 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: pass → 0.97 functional
- Package version: 2.22.5 → 2.23.0 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/freightutils-mcp@2.32.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | SoapyRED/freightutils-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SoapyRED/freightutils-mcp/.github/workflows/publish-registry.yml@refs/tags/v2.32.0 |
| Rekor log index | 3698140578 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b3589b6e8e0986cc93f94e9bef687fe2edac40b8ec7ed69b4e054b1d425f449176f2972ff3e23c496cf571b9d843a5017143c544045a61826b8634eac |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
validate ~505
Validate and parse freight identifiers by their public check-digit algorithms: shipping container numbers (ISO 6346), air waybill (AWB) numbers (IATA modulus-7) and IMO ship identification numbers. Two modes: pass text=<arbitrary string> to find and validate every identifier in it (e.g. a booking-email line), OR pass value=<identifier> + type=<container|awb|imo> to validate one. Behavior: deterministic check-digit arithmetic; per identifier found it reports type, the normalised form, valid (pass/fail), expected vs actual check digit, and details (container: owner prefix + equipment category; AWB: airline prefix + the airline from the AWB-prefix dataset when ONE record holds the prefix — when several do (e.g. 020: Lufthansa and Lufthansa Cargo), airline is null and airline_candidates[] lists every holder with airline_note saying why, never a guessed carrier; IMO: the 7-digit number); text mode with no identifiers found returns an empty found[] with a note. Rate-limited: a limit error carries reset_at, the UTC time the allowance resets. Returns: found[] (each entry with its own _source naming the standard applied) and disclaimer under result, plus confidence, _source and citation (the FreightUtils v1 response envelope). Limitations: STRUCTURAL ONLY — a valid check digit means well-formed, NOT that the container, shipment or vessel exists or is active; not a registry or tracking lookup. Related: container_lookup (container TYPE specs, not numbers), airline_lookup (the AWB-prefix dataset the airline resolution uses).
| Name | Type | Req | Description |
|---|---|---|---|
| consignment | object | – | With type "consignment": the consignment object to validate. The answer says whether it is valid and which checks it carries the inputs for. |
| text | string | – | Arbitrary string to scan for container / AWB / IMO identifiers (parse mode). Provide this OR value+type. Example: "2 cntrs MSKU3068808 / TGHU7654325 on AWB 176-12345675". |
| type | string | – | Identifier type for value: container = ISO 6346, awb = IATA air waybill, imo = IMO ship number; or "consignment" with the consignment argument. |
| value | string | – | A single identifier to validate (typed mode). Requires type — value without type is refused. Example: "MSKU3068808". |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| _source | object | yes | – |
| as_of | string | – | – |
| blocking_errors | array | – | – |
| citation | object | yes | – |
| confidence | object | yes | – |
| edition | – | – | – |
| envelope_version | string | yes | – |
| missing_inputs | array | – | – |
| normalized_input | object | – | – |
| ok | boolean | yes | – |
| result | – | yes | – |
| status | string | – | – |
| validity | object | – | – |
| warnings | array | – | – |
No examples provided.
vehicle_lookup ~515
Look up road-freight vehicle and trailer specifications — 17 types: EU articulated trailers (standard/mega curtainsider, box, reefer, double-deck, flatbed, low-loader), US 53ft/48ft dry vans, rigid trucks (7.5-26 t) and vans (Luton, Transit, Sprinter). Each record carries internal dimensions, payload and gross weights, euro/UK pallet capacity, axle configuration and features. Provide slug (e.g. "standard-curtainsider") for one record; omit it to list all 17; category (articulated | rigid | van) and region (EU | US) filter the list. Behavior: read-only; an unknown slug errors with the valid list and the closest slugs; a single record carries its provenance (sources, audited_at, decision_rationale). A list (no single record asked for) returns summary rows with total, truncated, next_offset and detail_hint; full: true returns full records five per page, with offset / limit to page. Rate-limited: a limit error carries reset_at, the UTC time the allowance resets. Returns: the vehicle record (or the list) under result, plus confidence, _source and citation (the FreightUtils v1 response envelope). Field names as this package serves them (snake_case); the hosted /api/mcp endpoint serves the same fields in camelCase (e.g. total_cbm → totalCbm). Limitations: typical specs, provenance pending independent verification (the envelope's provenance_status says so) — real equipment varies by operator and build; legal payload is set by the vehicle's plated weights. Related: ldm_calculator (whether a pallet load fits), pallet_fitting_calculator, consignment_calculator.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by vehicle category. |
| full | boolean | – | Lists only: true returns full records (provenance, sources, rationale) instead of summary rows, five per page by default. A single-record call always returns the full record. |
| limit | integer | – | Lists only: rows per page (default: every summary row; 5 with full: true). |
| offset | integer | – | Lists only: rows to skip (default 0). The response gives total and next_offset. |
| region | string | – | Filter by region. |
| slug | string | – | Vehicle slug. Examples: "standard-curtainsider", "mega-trailer". Omit to list all 17. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| _source | object | yes | – |
| as_of | string | – | – |
| blocking_errors | array | – | – |
| citation | object | yes | – |
| confidence | object | yes | – |
| edition | – | – | – |
| envelope_version | string | yes | – |
| missing_inputs | array | – | – |
| normalized_input | object | – | – |
| ok | boolean | yes | – |
| result | – | yes | – |
| status | string | – | – |
| validity | object | – | – |
| warnings | array | – | – |
No examples provided.
How do I install the FreightUtils MCP Server server?
FreightUtils MCP Server runs locally as an npm package, launched with npx -y freightutils-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · freightutils-mcp
claude mcp add soapyred-freightutils -- npx -y freightutils-mcp
What is the FreightUtils MCP Server server?
FreightUtils MCP Server is listed in the public MCP registry as io.github.SoapyRED/freightutils. Neutral freight reference + validation layer for AI agents: ADR, HS, UN/LOCODE, freight math. This page covers its npm package (freightutils-mcp).
Is the FreightUtils MCP Server server safe to use?
FreightUtils MCP Server scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FreightUtils MCP Server server expose?
FreightUtils MCP Server exposes 26 tools: cbm_calculator, chargeable_weight_calculator, ldm_calculator, adr_lookup, adr_exemption_calculator, and 21 more. Their descriptions and schemas cost roughly 22,918 tokens of context every time the server is loaded.
Is the FreightUtils MCP Server server still maintained?
FreightUtils MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the FreightUtils MCP Server server under?
FreightUtils MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the FreightUtils MCP Server server?
VerifyMCP ran 16 checks on FreightUtils MCP Server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.