FlitIQ — FMCSA Carrier Intelligence
Look up U.S. motor carriers, check CSA safety scores, verify insurance, and save carriers to your FlitIQ pipeline — all inside Claude. Requires a FlitIQ Pro or Team subscription.
- Category
- Operations
- Primary Subcategory
- Pending
Integration details
Description
FlitIQ is an FMCSA carrier intelligence tool used by brokers, shippers, and 3PLs to vet motor carriers before they book a load. This MCP plugin gives Claude access to the same data the FlitIQ web and iOS apps use: carrier identity, CSA BASIC scores, real insurance carrier names and policy detail (BIPD primary/excess, cargo, trust), recent inspections, recent crashes, and per-docket operating authority. Pro and Team subscribers can also save carriers to their pipeline directly from a Claude conversation. Per-carrier lookups only — no bulk export or list-all-carriers operation.
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- FlitIQ
- Access
- Unknown
- First tracked
- 2026-08-12
- Tool count
- 7
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Get alerts for FlitIQ — FMCSA Carrier Intelligence
Get updates when FlitIQ — FMCSA Carrier Intelligence’s Discoverability Score or category rank changes.
Claude Discoverability Score
FlitIQ — FMCSA Carrier Intelligence isn’t discoverable through Claude’s Connector picker
It runs as a local Claude Desktop Extension, so Claude cannot surface or score it there today.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What the current score measures

Remote Connectors Claude can surface from the Connector picker.
Competitive lineup
7 tools agents can invoke
How do I improve a Verified connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.