Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
FMCSA Carrier Intelligence is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
US carrier vetting on FMCSA data: authority, insurance, safety, identity links. Pay per call (x402)
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http fmcsa-carrier-intelligence-mcp https://fmcsa-mcp-843680657471.us-central1.run.app/mcp
# 2 — ask your agent for something these tools do
# get_catalog, get_sample, lookup_carrier and 8 more
FMCSA Carrier Intelligence costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http fmcsa-carrier-intelligence-mcp https://fmcsa-mcp-843680657471.us-central1.run.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Free, unauthenticated dataset catalog. Describes every table this service sells, its fields, current pricing, and freshness. Read this before paying for anything.
No parameter schema on file.
Free, unauthenticated sample of carrier_profile rows. Lets a buying agent evaluate data quality before spending USDC on the paid tools.
No parameter schema on file.
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 tho
| Parameter | Type | Required | Notes |
|---|---|---|---|
| usdot_number | integer | yes | — |
| claimed_name | no | — | |
| claimed_street | no | — | |
| claimed_city | no | — | |
| claimed_state | no | — | |
| claimed_zip | no | — |
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 s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | no | — | |
| safety_tier | no | — | |
| authority_status | no | — | |
| cargo_type | no | — | |
| include_inactive | boolean | no | — |
| limit | integer | no | — |
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 ar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| usdot_number | integer | yes | — |
| since_date | no | — |
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 Secti
| Parameter | Type | Required | Notes |
|---|---|---|---|
| usdot_number | integer | yes | — |
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 ow
| Parameter | Type | Required | Notes |
|---|---|---|---|
| usdot_number | integer | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| usdot_number | integer | yes | — |
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 sup
| Parameter | Type | Required | Notes |
|---|---|---|---|
| usdot_number_a | integer | yes | — |
| usdot_number_b | integer | yes | — |
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 lis
| Parameter | Type | Required | Notes |
|---|---|---|---|
| usdot_number | integer | yes | — |
| roster_usdot_numbers | array | yes | — |
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.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install FMCSA Carrier Intelligence or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish FMCSA Carrier Intelligence can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.