FMCSA Carrier Verify

dev.sourcewirePublished by sourcewire.devv1.2.4Updated Oct 29, 2026

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

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant vet US trucking carriers by USDOT or MC number, returning authority, insurance and out-of-service status with a…

What you can do
  • Look up US trucking carriers by USDOT or MC number
  • Check operating authority and insurance status
  • Report out-of-service (OOS) information
  • Return an overall PASS, REVIEW, FAIL or INCOMPLETE vetting verdict
When to use it
Useful when you need to screen or verify a US motor carrier before booking freight, onboarding a carrier, or checking whether a trucking company is legally allowed to operate.
Requirements
A remote MCP endpoint at mcp.apify.com; OAuth authentication is required. No local package or environment variables are declared.
Before you install
The server is hosted by a third party and requires OAuth sign-in, so carrier queries are sent to that provider. Verdicts are derived from public FMCSA-style data and should not replace official records or legal compliance checks.

Installation

In SourceWeft

  1. Open FMCSA Carrier Verify in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.sourcewire%2Ffmcsa-carrier-verify/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.2.4LatestOct 29, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.