CarrierVet MCP server
dev.carriervet/carriervetcarriervet.devstreamable-httpv1.4.1Scanned
Vet US motor carriers by USDOT or MC number: PASS/REVIEW/FAIL verdict, authority, insurance, OOS.
11 tools: 1 can delete or cancel things, 2 change things and 8 only read.
- Reads private data · 2
- Reads text others write · 6
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CarrierVet MCP server can do
The CarrierVet MCP server is published by carriervet.dev, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (1 tool: remove_from_watchlist) and create or change data (2 tools: check_load_eligibility and add_to_watchlist). 8 tools only read.
2 tools read private data (lookup_carrier and get_history); 6 tools bring in text other people can write (lookup_carrier, get_risk, check_load_eligibility and 3 more); 1 tool can send data out of your system (add_to_watchlist). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 1.4.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Deletes or cancels 1Claude Code: deny
remove_from_watchlistStop watching a carrier on this account.No findings
Why it is in this group
- The name "remove_from_watchlist" says "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Stop watching a carrier on this account.
Annotations the server declares
- title: Remove carrier from watchlist
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Changes things 2Claude Code: ask
add_to_watchlistAdd a carrier to this account's watchlist (paid plans).Can send data outNo findings
Why it is in this group
- The name "add_to_watchlist" says "add": a word for a change.
What it can reach
- outboundThe input takes a URL (input.webhook_url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Add a carrier to this account's watchlist (paid plans). Change alerts for the carrier's FMCSA record are delivered to the notification email and/or signed webhook (Pro+) configured for this monitor via alert_email and webhook_url. The carrier must have been looked up at least once.
Annotations the server declares
- title: Add carrier to watchlist
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_load_eligibilityEvaluate your own load rules against a carrier (by USDOT number or MC/FF/MX docket number) and get eligible, needs_review or ineligible, with each rule's result and reason, plus Ca…Reads text others write1 finding
Why it is in this group
- The description's first verb is "evaluate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "check_load_eligibility" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "evaluate": a word for a change.
Description, as the server wrote it Evaluate your own load rules against a carrier (by USDOT number or MC/FF/MX docket number) and get eligible, needs_review or ineligible, with each rule's result and reason, plus CarrierVet's unchanged verdict (PASS, REVIEW or FAIL) and risk score. All rules are optional: follow_verdict (default true: FAIL makes it ineligible, REVIEW needs_review), require_active_authority (default true), no_active_oos (default true), min_bipd_usd, require_cargo, max_risk_score (0-100; above it needs_review), min_authority_age_days (below it needs_review), block_reason_codes (present → ineligible), review_reason_codes (present → needs_review). Escalate needs_review and ineligible to a human; the decision to tender is theirs. Pass exactly one of dot or mc. Costs 1 lookup.
Annotations the server declares
- title: Check load eligibility
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 8Show 8 read-only tools
batch_lookupLook up to 500 USDOT or MC numbers in one call from stored snapshots (Pro and Business plans).Reads text others writeNo findings
Why it is in this group
- The name "batch_lookup" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Batch carrier lookup
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_historyList 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 FMC…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_history" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "email": it reads mail.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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 recorded it, the date CarrierVet saw it, and the before and after values. History starts on the date CarrierVet began recording, so older changes are not included. Recent contact changes are a common double-brokering warning sign. Costs 1 lookup.
Annotations the server declares
- title: Carrier change history
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_receiptFetch 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.No findings
Why it is in this group
- The name "get_receipt" says "get": a word for reading.
Description, as the server wrote it 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. Receipts are saved a few seconds after the lookup. Free; does not cost a lookup.
Annotations the server declares
- title: Get a lookup receipt
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_riskGet a 0-100 risk score for a carrier by USDOT number or MC/FF/MX docket number, with reason codes (e.g.Reads text others writeNo findings
Why it is in this group
- The name "get_risk" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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, severe 75-100. Hard failures (revoked, inactive or missing authority, out-of-service, lapsed or missing insurance, inactive USDOT number, not allowed to operate, Unsatisfactory safety rating) are listed in gates and keep the score at 50 or more, so a carrier that fails one is never low. With mc, the authority status is that docket's own. Also returns an overall verdict (PASS, REVIEW or FAIL) with verdict_reasons, and receipt_id. Informational signal for human review, not a safety rating. Pass exactly one of dot or mc. Costs 1 lookup.
Annotations the server declares
- title: Carrier risk score
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_usageShow this API key's plan, lookups used and remaining this UTC month, monitor count and rate limit.No findings
Why it is in this group
- The name "get_usage" says "get": a word for reading.
Description, as the server wrote it Show this API key's plan, lookups used and remaining this UTC month, monitor count and rate limit. Free; does not cost a lookup.
Annotations the server declares
- title: Quota and plan
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_watchlistList carriers on this account's watchlist (monitors), including each monitor's notification settings and last delivery status.No findings
Why it is in this group
- The name "list_watchlist" says "list": a word for reading.
Description, as the server wrote it List carriers on this account's watchlist (monitors), including each monitor's notification settings and last delivery status.
Annotations the server declares
- title: List watchlist
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
lookup_carrierGet 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 si…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "lookup_carrier" says "lookup": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "file": it reads files.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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, REVIEW or FAIL) with verdict_reasons, based on the PASS/FLAG/FAIL checks for authority, insurance, out-of-service, USDOT operating status and FMCSA safety rating: FAIL if any check is FAIL, REVIEW if any is FLAG, PASS otherwise. Pass exactly one of dot or mc. The response includes receipt_id; get_receipt returns the saved copy of this response later. Costs 1 lookup.
Annotations the server declares
- title: Look up a motor carrier
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
search_carriersFind carriers already stored by CarrierVet whose legal or DBA name contains the given text (max 25).Reads text others writeNo findings
Why it is in this group
- The name "search_carriers" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search carriers by name
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
12 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__carriervet__add_to_watchlist"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:24 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://carriervet.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://carriervet.dev
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://carriervet.dev/mcp: tools/list returned 12 tools to an anonymous client, including remove_from_watchlist (destructive), check_load_eligibility (write), check_contact (write), add_to_watchlist (write)
Posture changes
- Nov 19, 2026
- Tools that change things, listed without credentials: 3 to 4
- Nov 5, 2026
- Tools that change things, listed without credentials: 2 to 3
- RFC 9728 protected resource metadata: none to https://carriervet.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://carriervet.dev
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Findings
Matches of fixed checks, with the text they matched.
The server marks "check_load_eligibility" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "evaluate": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 4.View diff
- Tools that change things, listed without credentials: 3 to 4
Tools2 changed.~2 changedView diff
- Changed:add_to_watchlistChanges thingsdescription
- Changed:list_watchlistOnly readsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3; RFC 9728 protected resource metadata: none -> https://carriervet.dev/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://carr…View diff
- Tools that change things, listed without credentials: 2 to 3
- RFC 9728 protected resource metadata: none to https://carriervet.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://carriervet.dev
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Tools1 added.+1 addedView diff
- Added:check_load_eligibilityChanges things
Install
Pinned to version 1.4.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http carriervet https://carriervet.dev/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http carriervet https://carriervet.dev/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__carriervet__lookup_carrier",
"mcp__carriervet__get_risk",
"mcp__carriervet__get_receipt",
"mcp__carriervet__get_history",
"mcp__carriervet__search_carriers",
"mcp__carriervet__batch_lookup",
"mcp__carriervet__get_usage",
"mcp__carriervet__list_watchlist"
],
"ask": [
"mcp__carriervet__check_load_eligibility",
"mcp__carriervet__add_to_watchlist"
],
"deny": [
"mcp__carriervet__remove_from_watchlist"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as carriervet. Review it before you use it.
Capability tags behind 7 rules
- mcp__carriervet__lookup_carrier private-data, untrusted-input
- mcp__carriervet__get_risk untrusted-input
- mcp__carriervet__check_load_eligibility untrusted-input
- mcp__carriervet__get_history private-data, untrusted-input
- mcp__carriervet__search_carriers untrusted-input
- mcp__carriervet__batch_lookup untrusted-input
- mcp__carriervet__add_to_watchlist outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.carriervet/carriervet/verify?hash=4b944600a955b027d0f8cf58c265f675dab061daaedaa525778d25b69de0f77c" | jq -e '.changed == false'Pinned hash 4b944600a955, from Nov 16, 2026, 10:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.carriervet/carriervet/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.carriervet/carriervet)Source: MCP Registry. Synced Nov 3, 2026, 02:17 UTC.
CarrierVet MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CarrierVet MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the CarrierVet MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: remove_from_watchlist.
Can the CarrierVet MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the CarrierVet MCP server have?
- 11 tools: 1 destructive, 2 write, 8 read. remove_from_watchlist, check_load_eligibility, add_to_watchlist, lookup_carrier, get_risk, get_receipt, get_history, search_carriers and 3 more.
Does the CarrierVet MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CarrierVet MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): add_to_watchlist.
Has the CarrierVet MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.