_ registry / mcp streamable-http · checked 1h ago

carriertrail

https://carriertrail.com

Registry code: 95771799372fbcd9

api record

Look up US motor carriers, brokers and freight forwarders in public FMCSA data: search_carriers by name, get_carrier by USDOT/MC number, get_recent_changes for census changes. Every answer includes a CarrierTrail link. Free use is limited per day.

endpoint
https://carriertrail.com/mcp/v1
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is carriertrail live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is carriertrail free to use?
Yes — the hub reached it with no key and no payment.
What tools does carriertrail have?
3 tools: get_carrier, get_recent_changes, search_carriers.
Is carriertrail safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,143ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_carrier unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "number"
      ],
      "properties": {
        "kind": {
          "enum": [
            "DOT",
            "MC",
            "FF",
            "MX"
          ],
          "type": "string",
          "description": "Number type when the number has no prefix. Default DOT."
        },
        "number": {
          "type": "string",
          "maxLength": 30,
          "description": "USDOT or docket number, e.g. \"2233441\", \"MC-123456\", \"USDOT 2233441\"."
        },
        "sections": {
          "type": "array",
          "items": {
            "enum": [
              "company",
              "authority",
              "insurance",
              "safety"
            ],
            "type": "string"
          },
          "description": "Optional subset. Default all."
        }
      },
      "additionalProperties": false
    }
    arguments 37 lines
  • get_recent_changes unknown 1h ago

    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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "dot"
      ],
      "properties": {
        "dot": {
          "type": "string",
          "maxLength": 12,
          "description": "USDOT number."
        },
        "days": {
          "type": "integer",
          "default": 90,
          "maximum": 90,
          "minimum": 1
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • search_carriers unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 80,
          "minLength": 3,
          "description": "Company name or part of it. Each word needs at least 3 letters."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 10,
          "minimum": 1
        },
        "state": {
          "type": "string",
          "pattern": "^[A-Za-z]{2}$",
          "description": "Optional two-letter US state, e.g. TX."
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 95771799372fbcd9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/95771799372fbcd9/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/95771799372fbcd9/badge.svg)](https://brick.blue/agent/95771799372fbcd9?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.