Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Fmcsa

NPM · @PIPEWORX/MCP-FMCSA · 2 COMPONENTS

FMCSA MCP — US motor-carrier (trucking/bus) registry & safety.

+4 this week 91 Trust /100

Last scanned (11 hours ago)

Scores higher than 88% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-fmcsa). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 20 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 775 tokens (~193/item across 4 items; 4 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 Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

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 →

Changelog

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.

  • 22 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +6
    • Source repository: unverified → pass ▲ security
  • 9 Nov 26 −5
    • Provenance: pass → unverified ▼ security
    • Security disclosure: unverified → fail ▼ functional
Diagnostics

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 22 Nov 2026 · Analysed npm/@pipeworx/mcp-fmcsa@0.2.1

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 pipeworx-io/mcp-fmcsa
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-fmcsa/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637317171
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d57f6ad09658a1802df37266debdc0ade514a20d9a03b190f0b547def019398f023b05a1d567b2328804ac2c717ef31e31dd7b37dd2a8bab9b06a787c

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~721 tokens

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 →

Tool Tokens
fmcsa_carrier_lookup ~304

Look up a US motor carrier (trucking/bus company) in the FMCSA census by USDOT number, MC/docket number, or company name. Keyless. Returns legal & DBA name, physical address, active/inactive status, interstate/intrastate operation, hazmat flag, fleet size (power units, trucks), driver counts, and cargo types carried. Pass `dot_number` (or `mc_number`, or `name`) directly, or the generic `by` + `value` pair. For carrier authority (broker status) use fmcsa_operating_authority; for safety scores use fmcsa_safety_snapshot.

NameTypeReqDescription
bystring–Alternative calling shape: "dot" = USDOT number, "mc" = MC/docket number, "name" = company name; value goes in `value`.
dot_numbernumber|string–USDOT number to look up, e.g. 54283. The simplest way to call this tool.
mc_numbernumber|string–MC/docket number to look up, e.g. "136818" or "MC136818".
namestring–Carrier company name to look up, e.g. "swift transportation".
valuestring–The lookup value when using `by`: a USDOT number (e.g. "54283"), MC/docket number (e.g. "136818"), or carrier name.

No output schema declared.

No examples provided.

fmcsa_operating_authority ~120

Get a carrier's FMCSA operating authority by USDOT number: the MC docket number and the status of its common-carrier, contract-carrier, and broker authority (Active / Inactive / Pending / Revoked). Keyless. Answers "is this carrier authorized to operate / broker freight" — the legal authority to haul, complementing the census (fmcsa_carrier_lookup) and safety (fmcsa_safety_snapshot).

NameTypeReqDescription
dot_numbernumber|stringyesUSDOT number, e.g. 54283.

No output schema declared.

No examples provided.

fmcsa_safety_snapshot ~153

Get the FMCSA safety profile for a US motor carrier by USDOT number: safety rating (Satisfactory/Conditional/Unsatisfactory) with rating and review dates, USDOT operating status, driver/vehicle/hazmat inspection counts and out-of-service (OOS) rates vs national averages, and 24-month crash counts (fatal/injury/tow). Keyless via the FMCSA SAFER Company Snapshot. Pass an FMCSA QCMobile webKey via _apiKey to also get SMS BASIC categories (Unsafe Driving, HOS, Vehicle Maintenance, ...) with violation counts and percentiles.

NameTypeReqDescription
dot_numbernumber|stringyesThe carrier USDOT number, e.g. "76830".

No output schema declared.

No examples provided.

fmcsa_search_carriers ~144

Search US motor carriers by company name (partial, case-insensitive) in the FMCSA census, ranked by fleet size. Keyless. Returns USDOT number, legal/DBA name, city/state, power units, drivers, and status. Optionally filter by 2-letter state. Use fmcsa_carrier_lookup for full detail on a returned USDOT number.

NameTypeReqDescription
limitnumber|string–Max results (1-50, default 15).
namestringyesCompany name or fragment, e.g. "swift transport".
statestring–Optional 2-letter physical state filter, e.g. "TX".

No output schema declared.

No examples provided.

Install

How do I install the Fmcsa MCP server?

Fmcsa runs locally as an npm package, launched with npx -y @pipeworx/mcp-fmcsa. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-fmcsa

# add to Claude Code
claude mcp add pipeworx-io-fmcsa -- npx -y @pipeworx/mcp-fmcsa
Common questions

What is the Fmcsa MCP server?

Fmcsa is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fmcsa. FMCSA MCP, US motor-carrier (trucking/bus) registry & safety. This page covers its npm package (@pipeworx/mcp-fmcsa).

Is the Fmcsa MCP server safe to use?

Fmcsa scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 Fmcsa MCP server expose?

Fmcsa exposes 4 tools: fmcsa_carrier_lookup, fmcsa_search_carriers, fmcsa_operating_authority, fmcsa_safety_snapshot. Their descriptions and schemas cost roughly 721 tokens of context every time the server is loaded.

Is the Fmcsa MCP server still maintained?

Fmcsa is still listed as active in the MCP registry. We last reached this channel on 22 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 Fmcsa MCP server under?

Fmcsa 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 Fmcsa MCP server?

VerifyMCP ran 16 checks on Fmcsa, 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.