_ registry / mcp streamable-http · checked 1h ago

freight-intel

https://freight.dropwatchhq.com

Registry code: c706266a44d2a877

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://freight.dropwatchhq.com/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is freight-intel live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is freight-intel free to use?
Yes — the hub reached it with no key and no payment.
What tools does freight-intel have?
9 tools: safety_screen, switch_signal, new_authority_feed, new_carriers, search_carriers, regrade_list, carrier_risk_lookup, carrier_lookup, ….
Is freight-intel safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 98.8%· all time 98.8%

latency
438ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 678 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
maps travel & places logistics & shipping
used for
  • look up trucking carriers by dot number
  • screen carrier safety
  • find newly authorized carriers
takes → gives
text → data
tools
9 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
5 open 4 never probed 5 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_carriers reads open 21h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number"
    },
    "since": {
      "type": "string"
    },
    "state": {
      "type": "string"
    },
    "forHire": {
      "type": "boolean"
    },
    "insured": {
      "type": "boolean"
    },
    "hasEmail": {
      "type": "boolean"
    },
    "financeable": {
      "type": "string"
    },
    "maxPowerUnits": {
      "type": "number"
    },
    "minPowerUnits": {
      "type": "number"
    }
  }
}
    arguments 32 lines
  • regrade_list reads open 13h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "carriers"
  ],
  "properties": {
    "carriers": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "DOT and/or MC identifiers to re-grade."
    }
  }
}
    arguments 15 lines
  • carrier_risk_lookup reads open 21h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "dot"
  ],
  "properties": {
    "dot": {
      "type": "string",
      "description": "USDOT number."
    }
  }
}
    arguments 12 lines
  • carrier_lookup reads open 13h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "dot"
  ],
  "properties": {
    "dot": {
      "type": "string",
      "description": "USDOT number."
    }
  }
}
    arguments 12 lines
  • chameleon_check reads open 21h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number"
    },
    "state": {
      "type": "string"
    },
    "minScore": {
      "type": "number"
    }
  }
}
    arguments 14 lines
  • safety_screen reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "dot"
  ],
  "properties": {
    "dot": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • switch_signal reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "description": "virgin (populated primary) | terminated (rare secondary). Omit for both — leads with virgin."
    },
    "limit": {
      "type": "number"
    },
    "state": {
      "type": "string",
      "description": "2-letter state."
    }
  }
}
    arguments 16 lines
  • new_authority_feed reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max carriers (default 100)."
    },
    "since": {
      "type": "string",
      "description": "ISO date; only authorities on/after."
    },
    "state": {
      "type": "string",
      "description": "2-letter state, e.g. 'TX'."
    },
    "forHire": {
      "type": "boolean",
      "description": "Only for-hire carriers (have factorable receivables)."
    },
    "insured": {
      "type": "boolean",
      "description": "Only carriers with BIPD insurance on file."
    },
    "hasEmail": {
      "type": "boolean",
      "description": "Only carriers with an email on file."
    },
    "financeable": {
      "type": "string",
      "description": "Filter by verdict: GO | WAIT | NO | UNKNOWN."
    },
    "maxPowerUnits": {
      "type": "number"
    },
    "minPowerUnits": {
      "type": "number"
    }
  }
}
    arguments 39 lines
  • new_carriers reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max carriers (default 100)."
    },
    "since": {
      "type": "string",
      "description": "ISO date; only authorities on/after."
    },
    "state": {
      "type": "string",
      "description": "2-letter state, e.g. 'TX'."
    },
    "forHire": {
      "type": "boolean",
      "description": "Only for-hire carriers (have factorable receivables)."
    },
    "insured": {
      "type": "boolean",
      "description": "Only carriers with BIPD insurance on file."
    },
    "hasEmail": {
      "type": "boolean",
      "description": "Only carriers with an email on file."
    },
    "financeable": {
      "type": "string",
      "description": "Filter by verdict: GO | WAIT | NO | UNKNOWN."
    },
    "maxPowerUnits": {
      "type": "number"
    },
    "minPowerUnits": {
      "type": "number"
    }
  }
}
    arguments 39 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c706266a44d2a877.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c706266a44d2a877/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c706266a44d2a877/badge.svg)](https://brick.blue/agent/c706266a44d2a877?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on dropwatchhq.com 35 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

27 more sit on this domain. All of them.