FMCSA motor-carrier risk scores, monitoring, and carrier-selection evidence reports for AI agents.
Connect Remote server
claude mcp add --transport http carrierscore https://mcp.carrierscore.io/mcp
{
"mcpServers": {
"carrierscore": {
"url": "https://mcp.carrierscore.io/mcp"
}
}
}
{
"servers": {
"carrierscore": {
"type": "http",
"url": "https://mcp.carrierscore.io/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.carrierscore.io/mcp
Tools 8 found in our last check
carrier_lookupLook 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…
carrier_scoreGet 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…
montgomery_fileGenerate 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…
monitor_carriersBatch 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-s…
save_carrier_listSave 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. O…
list_alertsRetrieve 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…
audit_entriesList 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…
verify_evidenceVerify 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…
Details
| Endpoint | https://mcp.carrierscore.io/mcp (Streamable HTTP) |
| First published | 16 Aug 2026 |
| Last updated | 16 Aug 2026 |
| Registry name | io.carrierscore/carrierscore |
More data and analytics servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
