# com.dropwatchhq/freight-intel (remote · freight.dropwatchhq.com)

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

- Trust score: 54/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `freight.dropwatchhq.com`: 54/100 (this document), [markdown](https://verifymcp.io/servers/com-dropwatchhq-freight-intel/freight.md), [page](https://verifymcp.io/servers/com-dropwatchhq-freight-intel/freight)

## Channel facts

- Endpoint: `https://freight.dropwatchhq.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1381 tokens (~153/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 51% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-dropwatchhq-freight-intel https://freight.dropwatchhq.com/mcp
```

### Codex

```toml
[mcp_servers.com-dropwatchhq-freight-intel]
url = "https://freight.dropwatchhq.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dropwatchhq-freight-intel": {
      "type": "remote",
      "url": "https://freight.dropwatchhq.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dropwatchhq-freight-intel --url https://freight.dropwatchhq.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-dropwatchhq-freight-intel:
    url: "https://freight.dropwatchhq.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-dropwatchhq-freight-intel": {
      "type": "http",
      "url": "https://freight.dropwatchhq.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 52, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 53, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 52, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 51, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 50)

First indexed and scored.

## MCP tools (9)

### `new_authority_feed` (~267 tokens)

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.

Input parameters:

- `financeable` (string): Filter by verdict: GO | WAIT | NO | UNKNOWN.
- `forHire` (boolean): Only for-hire carriers (have factorable receivables).
- `hasEmail` (boolean): Only carriers with an email on file.
- `insured` (boolean): Only carriers with BIPD insurance on file.
- `limit` (number): Max carriers (default 100).
- `maxPowerUnits` (number)
- `minPowerUnits` (number)
- `since` (string): ISO date; only authorities on/after.
- `state` (string): 2-letter state, e.g. 'TX'.

### `carrier_lookup` (~50 tokens)

Full safety + contact profile for one carrier by USDOT number: identity, fleet, authority status, roadside safety record, FMCSA rating, email/phone.

Input parameters:

- `dot` (string, required): USDOT number.

### `search_carriers` (~131 tokens)

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.

Input parameters:

- `financeable` (string)
- `forHire` (boolean)
- `hasEmail` (boolean)
- `insured` (boolean)
- `limit` (number)
- `maxPowerUnits` (number)
- `minPowerUnits` (number)
- `since` (string)
- `state` (string)

### `safety_screen` (~68 tokens)

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.

Input parameters:

- `dot` (string, required)

### `new_carriers` (~316 tokens)

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.

Input parameters:

- `financeable` (string): Filter by verdict: GO | WAIT | NO | UNKNOWN.
- `forHire` (boolean): Only for-hire carriers (have factorable receivables).
- `hasEmail` (boolean): Only carriers with an email on file.
- `insured` (boolean): Only carriers with BIPD insurance on file.
- `limit` (number): Max carriers (default 100).
- `maxPowerUnits` (number)
- `minPowerUnits` (number)
- `since` (string): ISO date; only authorities on/after.
- `state` (string): 2-letter state, e.g. 'TX'.

### `carrier_risk_lookup` (~102 tokens)

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.

Input parameters:

- `dot` (string, required): USDOT number.

### `switch_signal` (~231 tokens)

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.

Input parameters:

- `limit` (number)
- `state` (string): 2-letter state.
- `type` (string): virgin (populated primary) | terminated (rare secondary). Omit for both — leads with virgin.

### `chameleon_check` (~99 tokens)

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.

Input parameters:

- `limit` (number)
- `minScore` (number)
- `state` (string)

### `regrade_list` (~117 tokens)

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.

Input parameters:

- `carriers` (array, required): DOT and/or MC identifiers to re-grade.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-dropwatchhq-freight-intel/freight#diagnostics

## Score history

- 2026-08-03: 54
- 2026-08-02: 53
- 2026-08-01: 53
- 2026-07-31: 52
- 2026-07-30: 53
- 2026-07-29: 52
- 2026-07-28: 52
- 2026-07-27: 51
- 2026-07-26: 50

## Links

- Remote endpoint: https://freight.dropwatchhq.com/mcp
- Website: https://freight.dropwatchhq.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-dropwatchhq-freight-intel/freight/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dropwatchhq-freight-intel/freight/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-dropwatchhq-freight-intel/freight