CarrierScore MCP Server

CarrierScore provides FMCSA motor-carrier risk scores, monitoring, and carrier-selection evidence reports for AI agents via the Model Context Protocol (MCP). It answers how risky a carrier is and what was knowable on a given date, using longitudinal risk scores (0–100, higher is riskier) and timestamped evidence from daily archives of public FMCSA / US DOT safety data.

🛠️ Key Features

FMCSA motor-carrier risk intelligence for AI agents
Longitudinal risk scores (0–100; higher = riskier)
Monitoring and carrier-selection evidence reports (“Montgomery files”)
Timestamped reporting based on given dates
Tool count: 4

🚀 Use Cases

Freight brokers needing risk assessment
AI booking/dispatch agents using carrier risk and evidence

⚡ Developer Benefits

Deterministic “knowable on a given date” framing for evidence reporting
Structured longitudinal scoring and time-stamped carrier-selection records

⚠️ Limitations

Evidence and scoring are derived from daily archives of public FMCSA / US DOT safety data (including census and inspections), as described in the provided excerpt.

CarrierScore MCP Server

FMCSA motor-carrier risk intelligence for AI agents, over the Model Context Protocol.

CarrierScore answers "how risky is this carrier, and what was knowable about it on a given date?" for freight brokers and AI booking/dispatch agents. It builds longitudinal risk scores (0–100, higher = riskier) and timestamped carrier-selection evidence reports ("Montgomery files") from daily archives of public FMCSA / US DOT safety data: census, inspections, crashes, out-of-service orders, operating authority, and insurance filings.

Website: carrierscore.io · Agent docs: carrierscore.io/llms.txt

Hosted endpoint (recommended)

No install needed — a hosted Streamable HTTP MCP endpoint is live:

code

https://mcp.carrierscore.io/mcp

Keyless requests get a rate-limited free tier (lookups, scores, text evidence reports). Paid tiers add carrier-list monitoring, structured JSON evidence reports, and higher volume — see pricing. Paid tiers authenticate with an X-API-Key header (or CARRIERSCORE_API_KEY when self-hosting).

Tools

Tool	What it does
`carrier_lookup`	Carrier identity by US DOT number: legal name, DBA, operating status, FMCSA safety rating, fleet size, address, registration dates. Use first to confirm a DOT is real and matches the rate confirmation.
`carrier_score`	The CarrierScore risk score (0–100, higher = riskier) with full component breakdown, hard flags (active OOS order, no active insurance, reincarnated-carrier link), and data-sufficiency indicator.
`montgomery_file`	Timestamped carrier-selection evidence report — the documented artifact a broker retains at the moment of booking (post Montgomery v. Caribe Transport II). Text format on the free tier; JSON on paid tiers.
`monitor_carriers`	Batch score summary + flags for up to 100 DOT numbers per call — screen candidates for a load or re-check an active roster.

Connect from a client

Claude Code

bash

claude mcp add --transport http carrierscore https://mcp.carrierscore.io/mcp

Claude Desktop / claude.ai

Settings → Connectors → Add custom connector → URL https://mcp.carrierscore.io/mcp.

Cursor

.cursor/mcp.json:

json

{
  "mcpServers": {
    "carrierscore": {
      "url": "https://mcp.carrierscore.io/mcp"
    }
  }
}

Generic MCP client (Streamable HTTP)

json

{
  "mcpServers": {
    "carrierscore": {
      "type": "streamable-http",
      "url": "https://mcp.carrierscore.io/mcp"
    }
  }
}

Self-hosting

The server in this repo is a thin Streamable HTTP client over the CarrierScore REST API (https://api.carrierscore.io).

bash

npm install
npm run build
CARRIERSCORE_API_URL=https://api.carrierscore.io npm start
# MCP endpoint: POST http://127.0.0.1:8322/mcp

Environment variables:

Variable	Default	Purpose
`CARRIERSCORE_API_URL`	`http://127.0.0.1:8321`	Base URL of the CarrierScore REST API
`CARRIERSCORE_API_KEY`	(unset)	Optional API key for paid tiers; unset = rate-limited free tier
`PORT`	`8322`	Port for the MCP HTTP endpoint (`POST /mcp`)

Disclaimer

CarrierScore scores are computed statistical indicators built from public FMCSA data under a documented, transparent methodology (population percentiles plus hard flags). They are not safety fitness determinations, are not endorsed by FMCSA, and do not substitute for a carrier's official safety rating or your own judgment. Every score and evidence report embeds this disclaimer — retain it when storing or quoting results.

dot_number	string	required	US DOT number of the carrier, digits only (e.g. "1234567")
format	string	optional	"text" = filing-ready report (free tier); "json" = structured fields (requires API key)

io.carrierscore/carrierscore