mcpbeat

Freight Intel MCP Server

com.dropwatchhq/freight-intel
answering

Freight Intel is answering right now. Last checked moments ago. It exposes 9 tools.

Freight carrier intel: new FMCSA authority feed, carrier lookup by DOT/MC, safety screen (CSA/SMS).

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
9
Tools
read from the server
63 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add freight-intel --transport http https://freight.dropwatchhq.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "freight-intel": {
      "url": "https://freight.dropwatchhq.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.freight-intel]
url = "https://freight.dropwatchhq.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "freight-intel": {
      "url": "https://freight.dropwatchhq.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "freight-intel": {
      "url": "https://freight.dropwatchhq.com/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

carrier
carrier_lookup
Full safety + contact profile for one carrier by USDOT number: identity, fleet, authority status, roadside safety record, FMCSA rating, email/phone.
carrier_risk_lookup
Risk-screen one carrier by USDOT number for insurance underwriting / factoring vetting: out-of-service rate vs national average, inspection history, FMCSA rating, authority + insurance status, flags. Honest-null with a 'no roadside inspection history' flag for brand-new carriers. Alias of safety_screen. A transparent triage signal from public FMCSA data, not a guarantee — verify against SAFER for underwriting decisions.
new
new_authority_feed
Return US trucking carriers newly granted FMCSA operating authority, newest first. The broker/factoring lead signal: each carrier just became able to legally haul. Pre-qualified for factoring: each carrier carries financeable (GO/WAIT/NO/UNKNOWN), forHire (has broker/shipper receivables to factor), authorityStatus (Active/Pending), insuranceStatus + insurer (BIPD on file), and owner/principal name — derived from the FMCSA census + L&I authority/insurance datasets. Filter by state, fleet size, since-date, has-email, forHire, financeable verdict, and insured.
new_carriers
Newly-authorized US motor carriers (FMCSA new entrants), newest first — the new-carrier LEADS feed for trucking insurance agents, factoring companies, and ELD/fuel-card/equipment vendors selling to new carriers. Each row: USDOT, legal/DBA name, address, phone, EMAIL (where on file), fleet size, authority type/status, plus factoring pre-qualification (forHire, financeable, authority/insurance status) and the safety layer (out-of-service rate / inspection history where the carrier already has a roadside record; honest-null with a 'no inspection history yet' flag for true new entrants). Alias of new_authority_feed. Filter by state, fleet size, since-date, has-email, forHire, financeable, insured. Leads from public FMCSA census — verify before outreach; respect DNC / CAN-SPAM.
carriers
search_carriers
Search the new-authority carrier set by state, fleet size, since-date, has-email, forHire, financeable verdict (GO/WAIT/NO), and insured. Returns pre-qualified, lead-ready carrier rows. For an arbitrary DOT use carrier_lookup.
chameleon
chameleon_check
Chameleon / reincarnation entity-resolution: new authorities that share a phone or physical address with a recently-DEACTIVATED carrier (a likely reincarnation of an outfit that lost authority). Filing-agent / registration-service clusters are down-weighted. Returns a 0-100 score + match basis. A review signal, not proof of fraud.
regrade
regrade_list
Re-grade a list of carriers (USDOT numbers and/or MC/docket numbers) against the live FMCSA/L&I record plus our switch-signal and chameleon layers. Each carrier returns a triage verdict and flags: already-factored, authority-revoked, insurance-lapsed, chameleon, virgin (no factor yet), or switch-lead (just terminated its factor). The 'wow' demo for factoring companies vetting their own lead list.
safety
safety_screen
Risk verdict for a carrier by USDOT number for insurance underwriting / shipper vetting: out-of-service rate vs national average, inspection history, FMCSA rating, authority status, flags. A transparent triage signal from public FMCSA data, not a guarantee.
switch
switch_signal
The real-time factor-SWITCH lead feed — the edge RigDig's static annual UCC buckets cannot show. PRIMARY = VIRGIN: a fresh authority with NO factor UCC-1 lien on record yet — the populated everyday flow, first factor to call wins (no factor yet — live). SECONDARY = TERMINATED: a UCC-3 termination just hit the carrier's factor lien (carrier now factor-free — highest-value lead). UCC-3 terminations are genuinely RARE — surfaced when they occur; an empty terminated list is honest, not a dead feed. Omit type to get the default (leads with `primary`=virgin, carries `secondary`=terminated). UCC coverage is partial and marked HONESTLY per state (uccCoverage); a carrier in a non-covered state is never labelled 'virgin'. Filter by type and state.

Endpoints

URLTransportStateLatencyChecked
https://freight.dropwatchhq.com/mcp streamable-http answering 66 ms 0 min ago

Freight Intel — questions

Answers built from our own checks of this server.

What can Freight Intel do?
It exposes 9 tools, read directly from the server on our last check. Among them: carrier_lookup, carrier_risk_lookup, chameleon_check, new_authority_feed, new_carriers, regrade_list and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Freight Intel mostly used for?
Its tools cluster around carrier and new. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Freight Intel 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 63 ms. The bar chart above shows every period we have measured.
How do I connect Freight Intel?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Freight Intel need an API key?
No. Freight Intel completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Freight Intel?
It answers our handshake in 63 ms on average, which is faster than 95% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.