FMCSA Carrier Verify MCP Server

by sourcewire Your server? Claim it

answering

FMCSA Carrier Verify is answering right now. Last checked 1 min ago.

Vet US trucking carriers by USDOT/MC: authority, insurance, OOS, PASS/REVIEW/FAIL/INCOMPLETE.

Uptime history 62 hours of history

62 hours agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

335 ms

Response time

average over 24h

API key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check FMCSA Carrier Verify every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add fmcsa-carrier-verify --transport http 'https://mcp.apify.com/?tools=sourcewire/fmcsa-carrier-verify'

Settings → Connectors → Add custom connector, then paste this address

https://mcp.apify.com/?tools=sourcewire/fmcsa-carrier-verify

~/.codex/config.toml

[mcp_servers.fmcsa-carrier-verify]
url = "https://mcp.apify.com/?tools=sourcewire/fmcsa-carrier-verify"

.cursor/mcp.json

{
  "mcpServers": {
    "fmcsa-carrier-verify": {
      "url": "https://mcp.apify.com/?tools=sourcewire/fmcsa-carrier-verify"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "fmcsa-carrier-verify": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=sourcewire/fmcsa-carrier-verify"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.apify.com/?tools=sourcewire/fmcsa-carrier-verify	streamable-http	needs key	316 ms	1 min ago

Alternatives to FMCSA Carrier Verify

same job, measured the same way

CarrierTrail

by carriertrail

US carrier lookup from public FMCSA data: USDOT/MC records, authority, insurance, safety.

3 tools answering

Carrier Ledger

by workers-neoaethel-carrier-ledger

Check U.S. trucking carriers and freight brokers in FMCSA records: authority, insurance, notices.

3 tools answering

Haulroll

by workers-cybermax-tools-cybermax

FMCSA carrier vetting API + MCP: authority, insurance, OOS. Keys $19/mo; 50 free calls/day.

3 tools answering

FMCSA Carrier Intelligence

by kmcto

US carrier vetting on FMCSA data: authority, insurance, safety, identity links. Pay per call (x402)

16 tools answering

US Business Verify

by sourcewire

Verify US businesses: TX/NY/CO/CT/OR registry status + OFAC sanctions. PASS/REVIEW/FAIL/INCOMPLETE.

answering

CarrierScrub

by carrierscrub

Check a US motor carrier's FMCSA authority, insurance and safety record: a dated GO/CAUTION/STOP.

answering

Fmcsa

by pipeworx-io

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

437 installs/wk 48 tools answering

CarrierVet

by carriervet

PASS/REVIEW/FAIL verdicts, risk, history, alerts, receipts. Verified against official FMCSA records.

11 tools answering

FMCSA Carrier Verify — questions

Answers built from our own checks of this server.

Why is there no tool list for FMCSA Carrier Verify?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is FMCSA Carrier Verify working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 335 ms. The bar chart above shows every period we have measured.

How do I connect FMCSA Carrier Verify?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.

Does FMCSA Carrier Verify need an API key?

Yes. Every time we knock, FMCSA Carrier Verify answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is FMCSA Carrier Verify?

It answers our handshake in 335 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.