Skip to content

CarrierVet API MCP server

Which MCP servers are CarrierVet API's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to CarrierVet API

Whose server it is
  • Registry namedev.carriervet/carriervetverified in the MCP registry

The registry name sits under carriervet.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools10
  • Server calls itselfcarriervet
  • Server version1.3.0
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 92 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: check carrier operating authority, insurance and out-of-service status; monitor carriers and receive alerts when their records change.
  • Checked on 6 of the 7 days it takes to judge reliability.

Once connected

  • For "check carrier operating authority, insurance and out-of-service status", the likely first call is lookup_carrier.
  • add_to_watchlist, remove_from_watchlist change data without a sign-in: anyone with the address can call them.

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.

Measured dailydaily checks: 6, the first on 2026-10-29
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer157 ms
  • Space in an agent's context≈ 1,818 tokensthe definitions of all its tools (11), which an agent carries on every turn
  • Tool definitionsA · 98 of 100
  • Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 11

What an agent can do with it

  • can do · check carrier operating authority, insurance and out-of-service status
  • can do · monitor carriers and receive alerts when their records change

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

  • Tools that change data, on a server that answers without a sign-in: add_to_watchlist, remove_from_watchlist

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 (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). 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 →

Tools it offers10 tools · read 2026-10-29
  • lookup_carrier

    Get a US motor carrier's FMCSA profile by USDOT number or MC/FF/MX docket number: legal name, operating authority status and age, insurance on file, out-of-service status, fleet size, address and contact. Returns an overall verdict (PASS…

  • get_risk

    Get a 0-100 risk score for a carrier by USDOT number or MC/FF/MX docket number, with reason codes (e.g. insurance_lapsed, authority_under_90_days, shared_phone, multiple_contact_changes). Levels: low 0-24, elevated 25-49, high 50-74…

  • get_receipt

    Fetch the saved copy of an earlier lookup by its receipt_id: the time it was made, the endpoint, the identifier, and the exact response CarrierVet returned, with its SHA-256. Any API key on the account that made the lookup can read it…

  • get_history

    List changes CarrierVet detected in a carrier's FMCSA record (address, phone, email, authority, insurance, out-of-service), newest first, plus fmcsa_history: dated changes from FMCSA's daily files and census, each with the date FMCSA…

  • search_carriers

    Find carriers already stored by CarrierVet whose legal or DBA name contains the given text (max 25). Prefer lookup_carrier when you have a USDOT or MC number. Costs 1 lookup.

  • batch_lookup

    Look up to 500 USDOT or MC numbers in one call from stored snapshots (Pro and Business plans). Each found result includes the same verdict, verdict_reasons and verdict_basis as lookup_carrier. Costs 1 lookup per unique identifier.

  • get_usage

    Show this API key's plan, lookups used and remaining this UTC month, monitor count and rate limit. Free; does not cost a lookup.

  • list_watchlist

    List carriers on this account's watchlist (monitors) with alert email, webhook and last delivery status.

  • add_to_watchlist

    Watch a carrier (paid plans) and get an email and/or signed webhook (Pro+) when its FMCSA record changes. The carrier must have been looked up at least once. Provide alert_email, webhook_url, or both.

  • remove_from_watchlist

    Stop watching a carrier on this account.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "carriervet": {
      "type": "http",
      "url": "https://carriervet.dev/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http carriervet https://carriervet.dev/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://carriervet.dev/mcp as a custom connector in the settings.

OpenAPI spec

22 paths, read 2026-10-29. Open the spec ↗

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.