
CarrierScore MCP server
Which servers in the official MCP registry are CarrierScore's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-26
- Registry nameio.carrierscore/carrierscoreverified in the MCP registry
The registry name sits under carrierscore.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-26
- Tools8
- Server calls itselfcarrierscore-mcp-server
- Server version0.4.0
- Protocol version2025-06-18
On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 2749 ms.
- Its tools do every use case we checked: Check carrier risk indices before booking a load; Generate timestamped carrier selection evidence reports.
- Checked on 1 of the 7 days it takes to judge reliability.
Once connected
- For "Check carrier risk indices before booking a load", the likely first call is carrier_score.
- For "Generate timestamped carrier selection evidence reports", the likely first call is montgomery_file.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- What an agent can do with it2 of 2 use cases
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer172 ms
- Space in an agent's context≈ 3,984 tokensthe definitions of all its tools (8), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results8 of 8 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- can do · Check carrier risk indices before booking a load
- can do · Generate timestamped carrier selection evidence reports
- not sure · Monitor carrier lists for authority and insurance changes
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
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…
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…
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…
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…
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…
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…
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…
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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"carrierscore": {
"type": "http",
"url": "https://mcp.carrierscore.io/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http carrierscore https://mcp.carrierscore.io/mcpclaude.ai, ChatGPT and other clients: add https://mcp.carrierscore.io/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.