
FMCSA Carrier Safety
io.github.J0401Published by GitHub account J0401v1.0.1Updated Nov 17, 2026
FMCSA carrier safety by DOT number: inspections, crashes, out-of-service. API, no login.
The publisher's own server: Carrier
Overview
Remote MCP server that looks up FMCSA trucking carrier safety records by DOT number, including inspections, crashes and out-of-service status.
- What you can do
- Look up carrier safety records by DOT number
- Retrieve inspection, crash and out-of-service information for a carrier
- No tool list was published, so exact operations are not documented beyond the description.
- When to use it
- Useful when vetting a motor carrier, checking a trucking company's safety history, or pulling FMCSA compliance details into a conversation without leaving the assistant.
- Requirements
- Remote streamable HTTP endpoint at mcp.apify.com; OAuth authentication is required. No environment variables or headers are declared.
Installation
In SourceWeft
- Open FMCSA Carrier Safety in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/io.github.J0401%2Ffmcsa-carrier-safety/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"fmcsa-carrier-safety": {
"type": "http",
"url": "https://mcp.apify.com/?tools=j0401/fmcsa-carrier-safety"
}
}
}Tools
0Version history
1- v1.0.1LatestNov 17, 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.
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 Carrier Vetting
Published by GitHub account santex85
Vets US motor carriers and brokers using FMCSA open data: lookup, name search, authority and insurance compliance, and heuristic fraud red flags.

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.

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.