SAFER FMCSA DOT Crawler avatar
SAFER FMCSA DOT Crawler

Pricing

Pay per event

Go to Store
SAFER FMCSA DOT Crawler

SAFER FMCSA DOT Crawler

Developed by

BowTiedRacoon

BowTiedRacoon

Maintained by Community

Crawl the SAFER DOT.GOV database for publicly registered vehicles. Supports Address, phone, email, DUNS and other registration details. Perfect for Lead Generation!

5.0 (1)

Pricing

Pay per event

6

Total users

111

Monthly users

6

Runs succeeded

>99%

Issues response

4.3 hours

Last modified

a month ago

You can access the SAFER FMCSA DOT Crawler programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/sse?actors=jungle_synthesizer/fmcsa-dot-crawler",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with SAFER FMCSA DOT Crawler

You have a few options for interacting with the MCP server:

  • Use mcp.apify.com via mcp-remote from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).

  • Set up the connection directly in your MCP client UI by providing the URL https://mcp.apify.com/sse?actors=jungle_synthesizer/fmcsa-dot-crawler along with an API token (or use OAuth).

  • Connect to mcp.apify.com via Server-Sent Events (SSE), as shown below:

{
"mcpServers": {
"apify": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=jungle_synthesizer/fmcsa-dot-crawler",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.