FMCSA motor-carrier risk scores, monitoring, and carrier-selection evidence reports for AI agents.
| Endpoint | https://mcp.carrierscore.io/mcp (streamable-http) |
|---|---|
| Registry version | 0.1.0 |
| Now | 8 tools · grade F (49) · pin ts_cabb31fa89caac1ab578ecf09f121f1f · protocol 2025-06-18 |
| First / last listed | 2026-11-01 02:14 UTC / 2026-11-01 02:14 UTC |
| Grade over time | 2026-11-01: F (49), 8 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: carrier_lookup carrier_score montgomery_file monitor_carriers save_carrier_list list_alerts audit_entries verify_evidence
carrier_lookup | Look up an FMCSA-registered motor carrier's identity by US DOT number: legal name, DBA, operating status, FMCSA safety rating, fleet size (power units, drivers), physical address, and registration dates.
Use this first when a booking/dispatch agent needs to confirm WHO a carrier is — that a DOT number is real, active, and matches the company name on a rate confirmation. It does not return risk in params: dot_number* |
carrier_score | Get the CarrierScore risk indices for a carrier by US DOT number: two first-class, separately validated indices (0-100, HIGHER = RISKIER), each with a full component breakdown.
This is the core "is this carrier safe to book?" signal for AI booking agents. Served methodology v0.5 returns TWO indices, both population-relative and built from point-in-time public FMCSA data:
- inspection_risk — ins params: dot_number* |
montgomery_file | Generate a timestamped Montgomery file — a carrier-selection evidence report — for a carrier by US DOT number.
Since Montgomery v. Caribe Transport II (SCOTUS, May 2026), freight brokers are exposed to state-law negligent-selection claims and need documented, timestamped, safety-data-based carrier selection. This report is that artifact: the two risk indices (inspection / compliance risk and cras params: dot_number*, format |
monitor_carriers | Batch risk check for a list of carriers by US DOT number (max 100 per call): score summary and hard flags for each.
Use when an agent is screening multiple candidate carriers for a load, or re-checking a broker's active carrier roster ("did any of my carriers pick up an out-of-service order or drop insurance?"). For a full breakdown of any single carrier that looks risky here, follow up with carr params: dot_numbers* |
save_carrier_list | Save a named list of carriers (by US DOT number) for continuous monitoring. Requires a paid CarrierScore API key (Monitor or Compliance tier) — connect with your key via OAuth (or set CARRIERSCORE_API_KEY on a self-hosted server); the free tier gets a 403 with an upgrade link.
Once saved, CarrierScore diffs every carrier on the list against the previous day's scoring run after each daily run and params: name*, dot_numbers*, webhook_url, email |
list_alerts | Retrieve the alert history for a saved carrier list (see save_carrier_list), newest first. Requires the same paid API key that saved the list.
Each alert records one change detected between consecutive daily scoring runs for one carrier: type (oos_order_activated, authority_lost, insurance_lapsed, status_changed, inspection_risk_jump, crash_risk_jump, score_jump, reincarnation_link), severity (cr params: list_id*, since |
audit_entries | List the immutable audit-archive entries for the caller's API key: every Montgomery evidence report the key generated (text or json), newest first, each with its entry id, generation timestamp, DOT number, scoring date, methodology version and the SHA-256 of the archived report text. Requires a paid CarrierScore API key.
Use it to answer "which carriers did we generate evidence for, and when?" an params: dot_number, since, limit |
verify_evidence | Verify an archived Montgomery evidence report by its audit entry id: CarrierScore re-reads the immutable stored copy, recomputes its SHA-256 and reports whether it matches the hash recorded at generation time (and, optionally, a hash the caller supplies — e.g. the sha256 printed on a broker's filed copy). Requires the same paid API key that generated the report.
Use it when a broker or auditor ne params: entry_id*, sha256 |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.