FMCSA Carrier Vetting

● Active

io.github.santex85/fmcsa-carrier-mcp

Vet US motor carriers and brokers from FMCSA open data: authority, insurance, OOS, safety.

Category
Data & Analytics
Version
0.1.0
Registry
active
Published
11/18/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 21, 2026

Looks healthy: FMCSA Carrier Vetting is maintained, open source.

Maintained
Active
Last commit 4 days ago (Nov 18, 2026), 0 open issues.
Official registry
Active
Published as io.github.santex85/fmcsa-carrier-mcp in the official MCP registry, version 0.1.0.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
On your machine
A local mcpb package started by your client; it can reach whatever your user account can.
Credentials
None declared
The registry entry declares no required environment variables.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 18, 2026
Stars
0
Forks
0
Last push
Nov 18, 2026
License
MIT

Pythoncarrier-vettingfmcsafreightlogisticsmcpmcp-servermodel-context-protocolpythontruckingusdot

From the 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 | NEWAUTHORITY, NEWUSDOT | high :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).

Read the full README on GitHub →

The most-starred Data & Analytics servers in the index, with their live-check result.

ServerStarsLast pushLive check
PostHog41,013Nov 2026Needs sign-in
PostHog MCP Server40,870Nov 2026Needs sign-in
Agent-Native Analytics7,735Nov 2026Needs sign-in
TradingMCP5,320Nov 2026Needs sign-in
Jitsu5,138Nov 2026Needs sign-in

FMCSA Carrier Vetting: questions people ask

Is FMCSA Carrier Vetting a remote or a local MCP server?
According to its entry in the official MCP registry, FMCSA Carrier Vetting ships as a local package (mcpb) that your client starts on your machine.
Is FMCSA Carrier Vetting safe to use?
Looks healthy: FMCSA Carrier Vetting is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: On your machine; credentials: None declared. Serverdex check of Nov 21, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is FMCSA Carrier Vetting still maintained?
Active: the repository's last commit 4 days ago. Last push Nov 18, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 18, 2026.
How do I add FMCSA Carrier Vetting to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. Website Contacts & Socials (role emails, WhatsApp, LINE, Telegram)Contact channels from a website: role emails, WhatsApp, LINE, Telegram, socials. No personal data.
  2. US & UK Import Tariffs and Duty RatesUS HTS and UK Trade Tariff: HS code search, duty rates by origin and rough landed-cost estimates.
  3. US Product Recalls (FDA, NHTSA, CPSC)US product recalls from FDA (food, drugs, devices), NHTSA (vehicles) and CPSC (consumer products).
  4. OSS Audit (package due diligence)Open-source package due diligence: licences, release health, Scorecard, dependents, OSV vulns.
Browse all Data & Analytics →

Add the badge to your site

Show visitors that FMCSA Carrier Vetting is listed here — it’s also the link we check for a free listing.

FMCSA Carrier Vetting — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-santex85-fmcsa-carrier-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="FMCSA Carrier Vetting — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![FMCSA Carrier Vetting — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-santex85-fmcsa-carrier-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).