# CarrierTrail (remote · carriertrail.com)

US carrier lookup from public FMCSA data: USDOT/MC records, authority, insurance, safety.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `carriertrail.com`: 36/100, [markdown](https://verifymcp.io/servers/com-carriertrail-mcp/mcp-account.md), [page](https://verifymcp.io/servers/com-carriertrail-mcp/mcp-account)
- remote · `carriertrail.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-carriertrail-mcp/mcp-v1.md), [page](https://verifymcp.io/servers/com-carriertrail-mcp/mcp-v1)

## Channel facts

- Endpoint: `https://carriertrail.com/mcp/v1`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 321 tokens (~107/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the CarrierTrail MCP server?

CarrierTrail is a hosted endpoint at https://carriertrail.com/mcp/v1, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-carriertrail-mcp 'https://carriertrail.com/mcp/v1'
```

### Cursor

```json
{
  "mcpServers": {
    "com-carriertrail-mcp": {
      "url": "https://carriertrail.com/mcp/v1"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-carriertrail-mcp": {
      "type": "http",
      "url": "https://carriertrail.com/mcp/v1"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-carriertrail-mcp]
url = "https://carriertrail.com/mcp/v1"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-carriertrail-mcp": {
      "type": "remote",
      "url": "https://carriertrail.com/mcp/v1",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-carriertrail-mcp --url 'https://carriertrail.com/mcp/v1' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-carriertrail-mcp:
    url: "https://carriertrail.com/mcp/v1"
```

### Netclaw

```json
{
  "McpServers": {
    "com-carriertrail-mcp": {
      "Transport": "http",
      "Url": "https://carriertrail.com/mcp/v1"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-carriertrail-mcp -t streamable-http -u 'https://carriertrail.com/mcp/v1'
```

### Other

```json
{
  "mcpServers": {
    "com-carriertrail-mcp": {
      "type": "http",
      "url": "https://carriertrail.com/mcp/v1"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 68)

First indexed and scored.

## MCP tools (3)

### `search_carriers` (~89 tokens)

Search carriers by name

Find US motor carriers, brokers and freight forwarders by company name in FMCSA census data. Returns up to 10 matches with USDOT number, location and status.

Input parameters:

- `limit` (integer)
- `name` (string, required): Company name or part of it. Each word needs at least 3 letters.
- `state` (string): Optional two-letter US state, e.g. TX.

### `get_carrier` (~112 tokens)

Look up a carrier

Company record for one carrier by USDOT, MC, FF or MX number: census registration, operating authority, current insurance filings and 24-month roadside safety summary, with a CarrierTrail link.

Input parameters:

- `kind` (string): Number type when the number has no prefix. Default DOT.
- `number` (string, required): USDOT or docket number, e.g. "2233441", "MC-123456", "USDOT 2233441".
- `sections` (array): Optional subset. Default all.

### `get_recent_changes` (~62 tokens)

Recent public changes

Changes to one carrier's public FMCSA census fields seen in the last 90 days (name, status, fleet size, MCS-150 date, dockets and more).

Input parameters:

- `days` (integer)
- `dot` (string, required): USDOT number.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-carriertrail-mcp/mcp-v1#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 69
- 2026-10-30: 69
- 2026-10-29: 68

## Common questions

### What is the CarrierTrail MCP server?

CarrierTrail is an MCP server listed in the public MCP registry as com.carriertrail/mcp. US carrier lookup from public FMCSA data: USDOT/MC records, authority, insurance, safety. This page covers its hosted endpoint (https://carriertrail.com/mcp/v1).

### Is the CarrierTrail MCP server safe to use?

CarrierTrail scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the CarrierTrail MCP server expose?

CarrierTrail exposes 3 tools: search_carriers, get_carrier, get_recent_changes. Their descriptions and schemas cost roughly 263 tokens of context every time the server is loaded.

### Does the CarrierTrail MCP server require authentication?

No. We connected to CarrierTrail without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CarrierTrail MCP server still maintained?

CarrierTrail is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://carriertrail.com/mcp/v1
- Website: https://carriertrail.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-carriertrail-mcp/mcp-v1.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-carriertrail-mcp/mcp-v1.json
- HTML version of this page: https://verifymcp.io/servers/com-carriertrail-mcp/mcp-v1