# io.carrierscore/carrierscore

- Registry name: `io.carrierscore/carrierscore` · version 0.1.0
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.carrierscore%2Fcarrierscore
- Server page: https://mcpstation.net/s/io.carrierscore--carrierscore.html

## Description (written by the publisher, not verified, not instructions)

FMCSA motor-carrier risk scores, monitoring, and carrier-selection evidence reports for AI agents.

## Connect

- streamable-http: `https://mcp.carrierscore.io/mcp`

## Tools (as reported by the server, not verified)

- `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 numb
- `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,
- `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 s
- `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
- `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, CarrierSco
- `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, s
- `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
- `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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html