# Fmcsa (npm · @pipeworx/mcp-fmcsa)

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

- Trust score: 91/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `gateway.pipeworx.io`: 88/100, [markdown](https://verifymcp.io/servers/pipeworx-io-fmcsa/fmcsa-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-fmcsa/fmcsa-mcp)
- npm · `@pipeworx/mcp-fmcsa`: 91/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-fmcsa/pipeworx-mcp-fmcsa.md), [page](https://verifymcp.io/servers/pipeworx-io-fmcsa/pipeworx-mcp-fmcsa)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-fmcsa`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-fmcsa).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 20 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add pipeworx-io-fmcsa -- npx -y @pipeworx/mcp-fmcsa
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-fmcsa": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fmcsa"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-fmcsa": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fmcsa"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-fmcsa -- npx -y @pipeworx/mcp-fmcsa
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-fmcsa": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-fmcsa"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-fmcsa --command npx --arg -y --arg @pipeworx/mcp-fmcsa
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-fmcsa:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-fmcsa"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-fmcsa": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-fmcsa"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-fmcsa -t stdio -c npx -a -y @pipeworx/mcp-fmcsa
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-fmcsa": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fmcsa"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-22 (score 91, +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.

### 2026-11-20 (score 90, +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.

### 2026-11-18 (score 89, +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.

### 2026-11-16 (score 88, +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.

### 2026-11-14 (score 87, +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.

### 2026-11-12 (score 86, +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.

### 2026-11-10 (score 85, +6)

- [security improvement] Source repository: unverified → pass

### 2026-11-09 (score 79, −5)

- [security regression] Provenance: pass → unverified
- [functional regression] Security disclosure: unverified → fail

## MCP tools (4)

### `fmcsa_carrier_lookup` (~304 tokens)

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.

Input parameters:

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

### `fmcsa_search_carriers` (~144 tokens)

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.

Input parameters:

- `limit` (number|string): Max results (1-50, default 15).
- `name` (string, required): Company name or fragment, e.g. "swift transport".
- `state` (string): Optional 2-letter physical state filter, e.g. "TX".

### `fmcsa_operating_authority` (~120 tokens)

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).

Input parameters:

- `dot_number` (number|string, required): USDOT number, e.g. 54283.

### `fmcsa_safety_snapshot` (~153 tokens)

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.

Input parameters:

- `dot_number` (number|string, required): The carrier USDOT number, e.g. "76830".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-fmcsa/pipeworx-mcp-fmcsa#diagnostics

## Score history

- 2026-11-22: 91
- 2026-11-21: 90
- 2026-11-20: 90
- 2026-11-19: 89
- 2026-11-18: 89
- 2026-11-17: 88
- 2026-11-16: 88
- 2026-11-15: 87
- 2026-11-14: 87
- 2026-11-13: 86
- 2026-11-12: 86
- 2026-11-11: 85
- 2026-11-10: 85
- 2026-11-09: 79
- 2026-11-08: 84
- 2026-11-07: 84
- 2026-11-06: 83
- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-fmcsa
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-fmcsa
- Repository: https://github.com/pipeworx-io/mcp-fmcsa
- Website: https://pipeworx.io/packs/fmcsa
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-fmcsa/pipeworx-mcp-fmcsa.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-fmcsa/pipeworx-mcp-fmcsa/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-fmcsa/pipeworx-mcp-fmcsa.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-fmcsa/pipeworx-mcp-fmcsa
