CarrierTrail
REMOTE · CARRIERTRAIL.COM · 2 COMPONENTS
US carrier lookup from public FMCSA data: USDOT/MC records, authority, insurance, safety.
Available components
Last scanned (3 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 321 tokens (~107/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://carriertrail.com/mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=carriertrail.com | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | bac132866ef8b7fb135af32a0d404f80 |
| SANs: carriertrail.com, go.carriertrail.com, *.go.carriertrail.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of carriertrail.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| carriertrail.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://carriertrail.com/mcp/v1 | Verified | 200 | |
| http (plaintext) | http://carriertrail.com/mcp/v1 | HTTPS enforced | 301 | https://carriertrail.com/mcp/v1 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_carrier Look up a carrier ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Number type when the number has no prefix. Default DOT. |
| number | string | yes | USDOT or docket number, e.g. "2233441", "MC-123456", "USDOT 2233441". |
| sections | array | – | Optional subset. Default all. |
No output schema declared.
No examples provided.
get_recent_changes Recent public changes ~62
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).
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| dot | string | yes | USDOT number. |
No output schema declared.
No examples provided.
search_carriers Search carriers by name ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| name | string | yes | Company name or part of it. Each word needs at least 3 letters. |
| state | string | – | Optional two-letter US state, e.g. TX. |
No output schema declared.
No examples provided.
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.
remote · carriertrail.com
claude mcp add --transport http com-carriertrail-mcp 'https://carriertrail.com/mcp/v1'
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.