
FMCSA Carrier Vetting
io.github.santex85Published by GitHub account santex85v0.1.0Updated Nov 19, 2026
Vet US motor carriers and brokers from FMCSA open data: authority, insurance, OOS, safety.
The publisher's own server: Carrier
Overview
Vets US motor carriers and brokers using FMCSA open data: lookup, name search, authority and insurance compliance, and heuristic fraud red flags.
- What you can do
- Look up a carrier profile by USDOT or MC/FF/MX number, including status, dockets, address, fleet size and safety rating
- Search carriers by legal or DBA name with state, city, active-only and for-hire-only filters
- Review full authority and insurance compliance: authority types and status, BIPD/cargo/bond on file, grant dates, cancellations, revocation and out-of-service orders, plus 24-month inspection and crash counts
- Run a heuristic fraud/risk screen that returns severity-coded flags, a score and a risk level
- When to use it
- Useful when a freight broker, shipper or 3PL wants to check who a carrier is, whether it holds active authority and insurance, and whether anything looks like fraud before tendering a load.
- Requirements
- Runs as a local Python process (stdio or streamable HTTP); the README describes creating a virtual environment and installing requirements, and the manifest ships an mcpb package. No API key or login is needed; it queries FMCSA open datasets on data.transportation.gov. Optional HOST, PORT and MCP_TRANSPORT environment variables. Network access required.
Installation
In SourceWeft
- Open FMCSA Carrier Vetting in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
FMCSA Carrier Vetting MCP server
An MCP server for freight brokers, shippers and 3PLs that need to vet US motor carriers and brokers before tendering a load. It answers "who is this carrier, are they allowed to haul, are they insured, and does anything look like fraud?" in one call. It uses FMCSA's own open data on data.transportation.gov (Socrata SODA API, no key, no login).
Tools
Example calls
Sample red_flags output for a carrier whose authority was granted the day before:
Red-flag checks
Score: high = 40, medium = 15, low = 5, capped at 100. Risk level is high if any high flag (or score ≥ 60),
medium if score ≥ 15, otherwise low. These are heuristics, not a finding of fraud. Always confirm by
calling the phone number FMCSA lists, not the one in an e-mail.
Data sources
All are FMCSA datasets on data.transportation.gov, read live per call (nothing is downloaded or cached except the per-dataset "last updated" timestamp, kept 1 hour):
Freshness. Every response has a dataFreshness list with each dataset's rowsUpdatedAt. FMCSA refreshes
these daily (all were updated 2026-11-17 when this was built). Data can lag the live SAFER / L&I web pages by
a day or more. Motus is FMCSA's current registration system. The legacy L&I files are still published, but
the legacy authority history has no new actions after about May 2026, so this server reads authority and
insurance from the Motus files and uses the legacy history only for older grant dates.
Terms / licence. The datasets carry no explicit licence field on data.transportation.gov. They are US federal government works published as open data, generally public domain in the US (17 U.S.C. § 105); this was not confirmed against a dataset-specific licence. No key is used. Socrata throttles anonymous clients, so for heavy production traffic register a free Socrata app token (not used here). The optional FMCSA QCMobile API needs a webKey via login.gov and is not used.
Privacy. Only what FMCSA publishes is returned, with no enrichment. The census file also contains company officer names, e-mail addresses and cell phones. This server deliberately leaves those out and returns only the business phone and addresses that the SAFER Company Snapshot shows.
Limits
- 90 s timeout per tool call, 45 s per HTTP request, 2 retries on 429/5xx.
search_carriers: name of 3+ characters, at most 100 results (scans up to 500 matches to sort by fleet size).- History lists are capped (50 status changes, 50 insurance filings, 25 cancellations, 50 orders, 10 shared-contact examples).
- Inspection/crash numbers are raw counts from FMCSA files, not the official SMS BASIC percentiles.
- One SODA query per dataset per call;
red_flagsandcheck_authoritymake about 10 to 13 requests and usually take 5 to 12 s.
Run
Environment variables: HOST (default 0.0.0.0), PORT (default 8080), MCP_TRANSPORT (streamable-http, stdio or sse; default streamable-http). No API key is needed.
mcpize.yaml is included for MCPize (runtime: python, startCommand.type: http).
Use with Claude Desktop or another MCP client
Local (stdio). Clone the repo, create the venv as above, then add this to claude_desktop_config.json
(or your client's MCP config), with the paths changed to where you cloned it:
Remote (streamable HTTP). Run .venv/bin/python src/server.py on a server and point any client that supports
remote MCP servers at http://<host>:8080/mcp. GET /health returns {"status": "healthy"}.
License
MIT, see LICENSE. The data returned by the tools stays under the terms of its sources (see above).
Source: README.md at commit 72d3f91
Tools
0Version history
1- v0.1.0LatestNov 19, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Carrier integrations
Carrier
llc.carrierOfficial publisher
Carrier lets an assistant manage programmable eSIM and mobile connectivity — fleets, plans and orders — through the Carrier API.

FMCSA Trucking Carrier Leads
Published by GitHub account benbarazandeh
Apify-hosted MCP tool that searches the official FMCSA USDOT census for trucking carriers and new leads by state and fleet size.

FMCSA Carrier Safety
Published by GitHub account J0401
Remote MCP server that looks up FMCSA trucking carrier safety records by DOT number, including inspections, crashes and out-of-service status.

US Trucking Changes (FMCSA)
Published by GitHub account datablume
FMCSA carrier changes: authority suspensions, insurance cancellations, new carriers. Runs on Apify.
Dialvett: Bulk Phone Number Validator & Carrier Lookup
dev.workers.cybermax-tools.cybermax
Apify-hosted remote MCP server that lets an assistant validate and format phone numbers in bulk and look up line type, carrier, location and time zone.