com.dropwatchhq/freight-intel
REMOTE · FREIGHT.DROPWATCHHQ.COM · SCANNED AUG 3
Freight carrier intel: new FMCSA authority feed, carrier lookup by DOT/MC, safety screen (CSA/SMS).
Available components
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. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 51% of tool parameters carry a description.Partial
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · freight.dropwatchhq.com
claude mcp add --transport http com-dropwatchhq-freight-intel https://freight.dropwatchhq.com/mcp
[mcp_servers.com-dropwatchhq-freight-intel] url = "https://freight.dropwatchhq.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-dropwatchhq-freight-intel": {
"type": "remote",
"url": "https://freight.dropwatchhq.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-dropwatchhq-freight-intel --url https://freight.dropwatchhq.com/mcp --transport streamable-http
mcp_servers:
com-dropwatchhq-freight-intel:
url: "https://freight.dropwatchhq.com/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 50
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://freight.dropwatchhq.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dropwatchhq.com | CN=WE1,O=Google Trust Services,C=US | 21 Jun 2026 | 19 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 40fe07bdbecbbc7b0e51efcfac332fe9 |
| SANs: dropwatchhq.com, freight.dropwatchhq.com, *.freight.dropwatchhq.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of freight.dropwatchhq.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| dropwatchhq.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://freight.dropwatchhq.com/mcp | Verified | 200 | |
| http (plaintext) | http://freight.dropwatchhq.com/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
carrier_lookup ~50
Full safety + contact profile for one carrier by USDOT number: identity, fleet, authority status, roadside safety record, FMCSA rating, email/phone.
| Name | Type | Req | Description |
|---|---|---|---|
| dot | string | yes | USDOT number. |
No output schema declared.
No examples provided.
carrier_risk_lookup ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dot | string | yes | USDOT number. |
No output schema declared.
No examples provided.
chameleon_check ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | — |
| minScore | number | — | — |
| state | string | — | — |
No output schema declared.
No examples provided.
new_authority_feed ~267
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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'. |
No output schema declared.
No examples provided.
new_carriers ~316
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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'. |
No output schema declared.
No examples provided.
regrade_list ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| carriers | array | yes | DOT and/or MC identifiers to re-grade. |
No output schema declared.
No examples provided.
safety_screen ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dot | string | yes | — |
No output schema declared.
No examples provided.
search_carriers ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| financeable | string | — | — |
| forHire | boolean | — | — |
| hasEmail | boolean | — | — |
| insured | boolean | — | — |
| limit | number | — | — |
| maxPowerUnits | number | — | — |
| minPowerUnits | number | — | — |
| since | string | — | — |
| state | string | — | — |
No output schema declared.
No examples provided.
switch_signal ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | — |
| state | string | — | 2-letter state. |
| type | string | — | virgin (populated primary) | terminated (rare secondary). Omit for both — leads with virgin. |
No output schema declared.
No examples provided.