mcpbeat Sign in

FMCSA Carrier Intelligence MCP Server

answering

FMCSA Carrier Intelligence is answering right now. Last checked 12 min ago. It exposes 11 tools.

US motor carrier safety, authority and identity-linkage checks from FMCSA data. Pay per call (x402).

Uptime history 10 days of history
10 days agonow
100.0%
Uptime 24h
91 of 91 checks
11
Tools
read from the server
214 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 4 October 2026. No other catalogue keeps this.

11 Oct 2 tool descriptions were rewritten get_safety_history, search_carriers
4 Oct 2 tool descriptions were rewritten get_safety_history, lookup_carrier

Nothing serious here today

Today is the operative word: we check FMCSA Carrier Intelligence every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add fmcsa-carrier-intelligence --transport http https://fmcsa-mcp-843680657471.us-central1.run.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "fmcsa-carrier-intelligence": {
      "url": "https://fmcsa-mcp-843680657471.us-central1.run.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.fmcsa-carrier-intelligence]
url = "https://fmcsa-mcp-843680657471.us-central1.run.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "fmcsa-carrier-intelligence": {
      "url": "https://fmcsa-mcp-843680657471.us-central1.run.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "fmcsa-carrier-intelligence": {
      "url": "https://fmcsa-mcp-843680657471.us-central1.run.app/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

address
check_address_consistency
How many distinct business addresses and phones this carrier reports across FMCSA's independent records of it (census registration, licensing and insurance filings, and its own self-reported crash records). Mailing addresses are excluded — differing from the physical address there is normal. Paid. Cheaper than either identity tool; one row, no graph.
applicant
check_applicant_against_roster
Screens one applicant carrier against a roster of carriers you already do business with (or are vetting) — the batch generalization of confirm_identity_link, for the real-world case of catching a carrier that was previously cut from your network (revoked, suspended, or otherwise let go) trying to re-enter under a new USDOT number. usdot_number is the applicant; roster_usdot_numbers is your own list, supplied by you. Returns linked (true if the applicant shares an identity cluster with ANY roster member) and matched_roster_usdot_numbers (which ones, always a subset of what you supplied — never a carrier you didn't already name). roster_not_found lists any roster entries that simply don't resolve to a known carrier (still your own input, not a new disclosure). usdot_number's own cluster_id is always included, same as check_carrier_identity's convention — it's the applicant's own data, not something withheld pending a match. usdot_number must not also appear in roster_usdot_numbers, and roster_usdot_numbers must be a non-empty list of at most settings.roster_screen_max_size distinct entries (currently 100) — either violation is a free invalid_arguments; split a larger roster into multiple calls rather than expecting it to be truncated for you. An unresolved usdot_number (the applicant itself) is a free not_found, same as confirm_identity_link/check_carrier_identity. Paid, metered: price = price_check_applicant_against_roster_base + price_check_applicant_against_roster_per_entry * (the deduped roster size) — see get_catalog for current rates. A "not linked to anything on your roster" result is a complete, valuable answer and bills the same as a match, same reasoning as check_carrier_identity's cluster_size == 1.
carrier
check_carrier_identity
Full identity-linkage detail for a carrier: why it's flagged and how confident that is. Priced meaningfully above the free screen_carrier_identity — call that first if you only need the flag and a count. Never names or points at another carrier (redesigned 2026-09-18 — see schemas.IdentityAssessment's docstring): no linked USDOT number, legal name, or shared-identifier hash. A linked carrier's own identity was never this caller's to receive, and an unsalted hash of a low-entropy value like a phone number or address doesn't meaningfully withhold it from a determined party anyway (confirmed by reading Truckin's own hashing code). Every field here is either the subject carrier's own data or a derivative signal — a score, a match-term-type label (which *kind* of identifier matched, never the value), a count, a boolean. SSN and EIN matches carry weight 2.0 each in FMCSA's ARCHI methodology and are not present in public data; D&B is nominally weight 2.0 too but is only genuinely available for ~4% of carriers, and officer data (needed for the name x officer term) is missing for another ~15%. So score_provenance.match_score_ceiling is computed per carrier, not a flat 4.5 — most responses cap out at 2.5 or lower. It also states plainly that recall against FMCSA's own declared-predecessor label set is not measurable. flagged applies FMCSA's own ARCHI flag rule (match_score >= 1.5 AND a linked motive >= 1); it is not a fraud determination and must not be presented as one. Note flagged and match_score >= 1.5 are NOT the same condition — clustering requires 2+ independent identifier-type families to agree, so materially more carriers clear the score threshold than are ever flagged. Paid. A carrier with no linked carriers is a complete answer and bills; an unknown USDOT number is a free not_found.
carriers
search_carriers
Filtered carrier search. Paid — you pay only when a call returns records; a zero-row result is free, same as an exact-key miss. safety_tier filters on safety_tier_derived: 1 = inspected with zero BASIC alerts, up to 6 = all five BASICs alerted. Carriers with no tier (never inspected, or not in SMS) never match a tier filter. Defaults to Active carriers only — pass include_inactive=true to also see Inactive/Pending. Capped at 100 rows per response regardless of the requested limit; never a full-table dump. Carries no contact information (legal_name, dba_name, addresses, phone, email — removed 2026-09-19, see schemas.CarrierProfile) — a filterable, multi-result endpoint returning personal contact details for whoever matched a filter was the sharpest version of that risk in this product; use lookup_carrier's claimed_name/claimed_street/etc. if you need to confirm a specific carrier's claimed identity.
catalog
get_catalog
Free, unauthenticated dataset catalog. Describes every table this service sells, its fields, current pricing, and freshness. Read this before paying for anything.
confirm
confirm_identity_link
Confirms or denies that two carriers YOU ALREADY SUSPECT are linked in fact share an identity cluster — the lower-risk alternative to check_carrier_identity's removed linked_carriers field (see schemas.IdentityAssessment's docstring for why that was removed 2026-09-18). This never discloses a carrier's identity to a caller who didn't already have it: both usdot_number_a and usdot_number_b are supplied by you. It only ever answers "do these two specific carriers share a cluster?", never "who is linked to this carrier?" — call check_carrier_identity for that, which stops at a score and a count for exactly this reason. cluster_id is returned only when linked is true, and isn't new information even then — you could obtain the same value directly from either carrier's own check_carrier_identity or screen_carrier_identity response. usdot_number_a and usdot_number_b must differ (invalid_arguments, free — there is no comparison to make). Either number failing to resolve in carrier_identity_cluster is a free not_found, same as check_carrier_identity. Paid — pricier than check_carrier_identity, since it resolves two carriers' clusters per call, not one. A "not linked" result is a complete, valuable answer and bills the same as "linked", same reasoning as check_carrier_identity's cluster_size == 1.
identity
get_identity_sample
Free, unauthenticated sample of identity/fraud responses, covering both screen_carrier_identity's free IdentityScreen shape and check_carrier_identity's paid IdentityAssessment shape. Lets a buying agent see the paid response shape and evaluate data quality before spending USDC on check_carrier_identity.
lookup
lookup_carrier
Look up a single carrier's current profile by USDOT number. Paid — you pay only when a call returns records; an exact-key miss is free. Returns every carrier_status (Active, Inactive, Pending) — check the carrier_status field, don't assume Active. insurance_cancel_pending is true when an insurance cancellation is on file and not yet effective as of record_as_of (rare: dozens of carriers, not thousands). Compare soonest_cancel_effective_date with today: the data is a monthly snapshot, so the cancellation may already have taken effect. days_to_cancel_effective counts from record_as_of, not today. Carries no contact information (legal_name, dba_name, addresses, phone, email — removed 2026-09-19, see schemas.CarrierProfile). The one legitimate use those fields served — confirming a carrier's claimed identity against records, e.g. to catch a carrier-identity-theft ("double brokering") attempt — is available instead via claimed_name (matched against legal_name OR dba_name) and claimed_street/ claimed_city/claimed_state/claimed_zip (matched against physical_address; supply any subset). Returns name_match/ physical_address_match as a boolean per claim actually supplied, `null` for a claim not supplied — never the value on file itself.
safety
get_safety_history
Historical snapshots and changelog entries for a carrier. Paid — you pay only when a call returns records; an exact-key miss is free. changelog may legitimately be empty for a carrier without two distinct-date snapshots yet — a diff needs both. authority_types, oos_orders_active, insurance_bipd_on_file, insurance_cargo_on_file, insurance_bond_on_file, has_been_revoked, and last_revocation_date are null (not false/empty) on a history row recorded before 2026-09-02 — carrier_history wasn't tracking those fields yet, so null there means "not tracked on this date," not a negative answer. Likewise has_been_suspended/last_suspension_date are null before 2026-09-06, and has_authority_reinstated/last_reinstatement_date/ has_insurance_identity_mismatch are null before 2026-09-12, and insurance_cancel_pending/days_to_cancel_effective/ soonest_cancel_effective_date are null before 2026-10-04. changelog holds real changes only (change_kind "value_changed"): the row the warehouse writes when a field first starts being tracked is never returned. About 97% of authority_status changes are dated 2026-09-02, when FMCSA's licensing data switched systems; treat that date's authority_status changes with some caution. Likewise most safety_tier_derived changes dated 2026-10-10 come from a method change (a second SMS file added; never-inspected carriers moved from tier 1 to null), not from the carrier. Carries no contact information (legal_name, dba_name, addresses, phone, email — removed 2026-09-19, see schemas.CarrierProfile); changelog excludes field_name in {legal_name, dba_name, phone, email} for the same reason — a changed value is still the value.
sample
get_sample
Free, unauthenticated sample of carrier_profile rows. Lets a buying agent evaluate data quality before spending USDC on the paid tools.
screen
screen_carrier_identity
Free triage screen for a carrier: whether it's flagged under FMCSA's own chameleon-carrier methodology, how big its identity cluster is, and how many linked carriers carry a motive — with no member detail. Call check_carrier_identity (paid) for that. This is the entire discovery/sales motion in an agent-only channel, not a discount tier — free by design (Identity-API-Revision- 2026-09-06.md Section 1), so it never bills and never requires payment. By the same design, it withholds anything that identifies a linked carrier: no member USDOT number, no legal name, no link type, no identifier hash. A caller learns THAT there is something to look at here, not WHAT. confidence_caveat discloses the known ~6% artifact rate and that recall is not measurable in FMCSA's public data — read it, don't just check the flagged boolean. match_score_practical_ceiling is computed per carrier from which ARCHI terms were actually available for it, not a flat constant — most carriers cap out well below the theoretical 8.5. An unknown USDOT number returns a not_found error.

Endpoints

URLTransportStateLatencyChecked
https://fmcsa-mcp-843680657471.us-central1.run.app/mcp streamable-http answering 193 ms 12 min ago

Alternatives to FMCSA Carrier Intelligence

same job, measured the same way
CarrierScrub
by carrierscrub

Check a US motor carrier's FMCSA authority, insurance and safety record: a dated GO/CAUTION/STOP.

answering
Chainverdict
by chainverdict

Pay-per-call x402 checks before an agent moves money: token safety, wallet risk, identifiers.

20 tools answering
US Brand Intelligence
by timzinin-api

Pay-per-call US brand evidence and signal workflows with free MCP discovery and x402 payments.

21 tools answering
Agent Newsstand
by agentnewsstand

Market data and web intelligence for AI agents, paid per call in USDC on Base via x402.

16 tools answering
C
CryptoPulse Data API
by saascloud

Pay-per-call crypto market intelligence for AI agents. USDC on Base via x402.

11 tools answering
Lead Intelligence
by timzinin-api

Pay-per-call lead intelligence tools with free MCP discovery and x402 payments.

8 tools answering
XRPLME Country Intelligence
by daimyovegan

Source-backed country policy data for AI agents; pay-per-call via x402 (XRP or USDC).

9 tools answering
F
Freight Intel
by dropwatchhq

Freight carrier intel: new FMCSA authority feed, carrier lookup by DOT/MC, safety screen (CSA/SMS).

9 tools answering

FMCSA Carrier Intelligence — questions

Answers built from our own checks of this server.

What can FMCSA Carrier Intelligence do?
It exposes 11 tools, read directly from the server on our last check. Among them: check_address_consistency, check_applicant_against_roster, check_carrier_identity, confirm_identity_link, get_catalog, get_identity_sample and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is FMCSA Carrier Intelligence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 214 ms. The bar chart above shows every period we have measured.
How do I connect FMCSA Carrier Intelligence?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does FMCSA Carrier Intelligence need an API key?
No. FMCSA Carrier Intelligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is FMCSA Carrier Intelligence?
It answers our handshake in 214 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.