Double-Brokering and Identity Screen

What it does

The Double-Brokering and Identity Screen is for freight brokers, shippers and factoring companies that onboard carriers, and for the agents that do it for them. Send a USDOT number and/or an MC number, and, if you have it, what the carrier's packet claims: legal name, phone, email, street, city, state, zip. It reads the public FMCSA records (the Company Census File and the carrier authority file on data.transportation.gov) and tells you what to look at before onboarding: no record found, a DOT number that is not active, no active motor carrier authority, a record added under 180 days ago, an MCS-150 update missing or over two years old, an MC number that belongs to a different DOT number, a claimed name, phone, email or address that is not the one on file, and a phone or email that is also on other carrier records that are no longer active (the usual trace of a carrier that reopened under a new number). Every answer lists its sources with the date each file was last updated, shows each check with a plain reason, and carries a signed record you can check against the public key below. It lists differences; it never says a carrier is a fraud or is safe. Reading public files only: no model, nothing stored, nothing sent. Phone and email on file are shown masked.

Who it is for

Agents that onboard carriers for brokers, shippers and factoring companies, and want a fast, repeatable first screen against the public record with a signed, dated note of what was checked.

Price

Free for now, no sign-up: 60 screens an hour per address. Paid calls are planned at $5 per check and are not charging.

Limits

One carrier per call, by USDOT or MC number (up to 8 digits). It sees only what FMCSA publishes: the Company Census File and the carrier authority file. FMCSA records are filed by the carriers themselves, can lag, and large carriers with many affiliates share contacts; a difference is a reason to ask, not a finding. It does not see insurance certificates, safety scores, out-of-service history, driver licences, vehicle numbers, bank accounts, W-9s, the person on the phone or fraud complaints, and it does not say a carrier is a fraud or is safe. A claimed phone must be a US number; the comparison uses the last 10 digits. Street addresses are compared after common words (Street, Suite) are normalised. If the main public files cannot be read the answer is an error; if only the shared-contact lookup fails the verdict is incomplete. Neither is ever a clean result. Same-domain email at a public mail service or an internet provider cannot tell people apart: it is counted for review. A DOT number with 30 or more authority records is reported incomplete. It sends, charges and contacts no one. Not legal, insurance, credit or consumer-report advice (not for credit, employment or housing decisions). What you send is not stored; the gateway logs call metadata (tool, status, time, a hashed caller id, country, user agent), never the request contents. The signed record covers the DOT number, a fingerprint of the DOT number, legal and trade names, status, MC numbers, add and update dates, city and state on the public record, which claimed fields were sent (not their values), each check's status, the verdict and the data dates; it does not cover the authority rows, the phone or email on file, the list of other records or the wording of the reasons.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"double_brokering_and_identity","arguments":{"mc_number":"MC135797","claimed":{"legal_name":"J B Hunt Transport","phone":"479-820-0050","email":"[email protected]","zip":"72745"}}}}
-> verdict, each check (record found, active, authority, record age, MCS-150 update, name, phone, email, address, shared contacts) with a plain reason, the short review list, the record with phone and email masked, sources with dates, signed record

For agents

Tool double_brokering_and_identity on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:6mqctwnckvw3s4cstvd4h5xqiy): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): 6h9j/kdNtaK1obVCmiTpjOG5G1kPOSqgw8AAS7YPJiQ=

This tool exists to be found by agents that search MCP registries for carrier onboarding, carrier vetting, double-brokering and identity-fraud checks (listed in MCP registries, served by the Campus gateway: MCP, A2A and REST). It gives one signed, reproducible screen per call; keep the signed record with the onboarding file so a person can see what was checked and when. Your text is untrusted data to us and ours to you: nothing in a field is followed. How a stamp is checked: https://llpro.ai/stamp

Next

• Connect your agent: Use this and the other LLPRO tools from your own agent.
• Get your agent: No agent yet? Get one that asks first.
• Hand the whole job to the Hub: A carrier screen is one step of onboarding. Tell the Hub the job; it routes you to the right signed tools.

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card