Log inSubmit server
Fmcsa logo

Fmcsa

Keyless FMCSA lookups for carrier identity, operating authority, safety records, and carrier search.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Fmcsa

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "fmcsa": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fmcsa"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The Fmcsa MCP server connects AI agents to US FMCSA carrier, authority, and safety data. It provides keyless lookups by USDOT number, MC number, or carrier name, plus optional SMS BASIC percentiles with an FMCSA webKey. Use it to verify carriers, review operating authority, compare safety indicators, or search for carriers by state and fleet size. It runs through a Pipeworx MCP endpoint or as a local stdio package.

Use cases

  • Verify a carrier by USDOT or MC number
  • Search for carriers by name and state
  • Check broker or freight operating authority
  • Compare carrier safety rates with national averages
  • Review recent carrier crash counts

Key features

  • USDOT, MC number, and carrier-name lookup
  • Partial carrier search with state filtering
  • Operating authority and broker status checks
  • Safety ratings and out-of-service comparisons
  • 24-month crash counts
  • Optional SMS BASIC percentiles

Tools4

What Fmcsa lets your agent do. Expand a tool for its parameters.

Self-reported~144 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @pipeworx/mcp-fmcsa (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads451Package downloads in the last 30 days.
Last commit27d agoMost recent push to the default branch.
Tools exposed4Callable tools this server registers over MCP.

How Fmcsa works

What Fmcsa MCP server does

The Fmcsa MCP server exposes US motor-carrier registry and safety information through MCP tools. It can identify a carrier from a USDOT number, MC number, or name; search for carriers using a partial name; report operating authority; and return a safety snapshot.

Results can include legal and DBA names, addresses, operating status, fleet and driver counts, cargo types, authority classifications, safety ratings, out-of-service rates, national comparisons, and crash counts covering the previous 24 months. Search results are ranked by fleet size and can be narrowed by state.

How it works

The Fmcsa MCP server reads from FMCSA Motor Carrier Census and Operating Authority datasets, the SAFER Company Snapshot, and, when requested, the FMCSA QCMobile API. The census, authority, and SAFER sources work without credentials. SMS BASIC category percentiles require a free QCMobile webKey supplied as the _apiKey argument to the safety tool.

The hosted MCP endpoint is available at https://gateway.pipeworx.io/fmcsa/mcp. A connection to that endpoint includes the four FMCSA tools and shared Pipeworx meta-tools. The gateway's ask_pipeworx tool can route a natural-language question to tools across the broader Pipeworx catalog. A local installation exposes only the FMCSA pack tools and does not include those gateway meta-tools.

The tools can also be called over HTTP. For example, a POST request to /v1/tools/fmcsa_carrier_lookup can submit a dot_number and return the matching carrier record.

Setup and configuration

To use the Fmcsa MCP server with a hosted MCP-capable client, add the Pipeworx endpoint as an MCP server. The package can instead be launched locally with npx -y @pipeworx/mcp-fmcsa, using stdin and stdout for MCP messages. This local mode does not require a Pipeworx account or gateway round trip.

No environment variables are required by the documented setup. The standard FMCSA tools are keyless. To add SMS BASIC percentiles, obtain a QCMobile webKey through FMCSA's API access process, which requires a login.gov account, and pass it to fmcsa_safety_snapshot as _apiKey.

Tools and capabilities

The Fmcsa MCP server provides these focused operations:

  • fmcsa_carrier_lookup: retrieves carrier identity and census details using a USDOT number, MC number, or name.
  • fmcsa_search_carriers: finds partial name matches, ranks them by fleet size, and optionally filters by state.
  • fmcsa_operating_authority: reports MC docket information and common, contract, and broker authority status.
  • fmcsa_safety_snapshot: returns safety ratings, driver, vehicle, and hazmat out-of-service rates compared with national averages, 24-month crash counts, and optional SMS BASIC percentiles.

Limitations and notes

The Fmcsa MCP server depends on upstream FMCSA records. If a carrier's biennial MCS-150 update has expired, the result may show record_inactive. FMCSA does not publish a safety snapshot for inactive USDOT numbers, although the carrier lookup can still return the last filed census record. This condition represents missing upstream safety data rather than a service outage.

The hosted pack endpoint lists shared Pipeworx tools in addition to the FMCSA tools, so its tool count is larger than the four operations documented here. The local stdio package lists only the pack's own tools. The project is licensed under MIT.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Fmcsa

Fmcsa is an MCP server that connects AI agents to FMCSA motor-carrier registry, operating-authority, SAFER, and optional QCMobile data. Its main tools look up carriers, search by name, check common, contract, or broker authority, and return safety ratings, out-of-service rates, crash counts, and optional SMS BASIC percentiles.

Install it locally with `npx -y @pipeworx/mcp-fmcsa` and configure the command in an MCP client. You can also connect to `https://gateway.pipeworx.io/fmcsa/mcp` as a hosted MCP endpoint. The local package uses stdin and stdout and does not require a Pipeworx account.

No, the standard tools are keyless. `fmcsa_safety_snapshot` can optionally accept an FMCSA QCMobile webKey through `_apiKey` to add SMS BASIC percentiles. Obtaining that webKey requires FMCSA API access registration and a login.gov account.

A safety snapshot may be unavailable when the carrier's biennial MCS-150 update has lapsed and FMCSA marks the USDOT record as `record_inactive`. The carrier lookup can still return the last filed census record, so this indicates an upstream FMCSA data gap rather than an outage.

Related MCP servers

All in Travel & Transportation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFmcsa AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/fmcsa?style=directory)](https://allmcps.com/mcp/fmcsa)
HTML Embed
<a href="https://allmcps.com/mcp/fmcsa"><img src="https://allmcps.com/api/badge/fmcsa?style=directory" alt="Fmcsa on AllMCPs" /></a>