Skip to content

FMCSA Carrier Intelligence MCP server

io.github.KMCTO/fmcsa-carrier-intelligenceKMCTOstreamable-httpv0.2.2Scanned

US carrier vetting on FMCSA data: authority, insurance, safety, identity links. Pay per call (x402)

16 tools: 7 change things and 9 only read.

Tools: 0 delete, 0 irreversible, 7 write, 9 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

7 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 FMCSA Carrier Intelligence MCP server can do

The FMCSA Carrier Intelligence MCP server is published by the GitHub account KMCTO. It has 16 tools. It can create or change data (7 tools: screen_carrier_identity, check_carrier_identity, check_address_consistency, confirm_identity_link and 3 more), but cannot delete data. 9 tools only read.

None of its tools reads private data, brings in text other people write, or sends data 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 once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 0.2.2.

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.

16 tools

Changes things 7Claude Code: ask
  • check_address_consistencyHow 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 sel…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_applicant_against_rosterScreens 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 cas…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_broker_authorityDoes this broker hold active broker authority, and what does FMCSA's record say around it?No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Does this broker hold active broker authority, and what does FMCSA's record say around it? Give exactly one of mc_number (the broker's MC docket, written MC123456, MC-123456 or 123456) or usdot_number. Paid, flat price; billed whenever the carrier resolves, including when it holds no broker authority (that is the answer). An unknown docket or USDOT number is a free not_found; giving neither or both, or a docket FMCSA lists under several carriers without naming a holder, is a free error. Returns holds_active_broker_authority and the broker dockets (docket number, status, how current that status is, active types, first grant and last event dates); the bond (BMC-84/85) on-file flag with its continuity (coverage unbroken since, current gap, closed lapses in 24 and 60 months, longest gap, data-through date); the authority event history (grants, reinstatements, revocations, suspensions, in total and over 24 and 60 months); revocation, suspension and reinstatement flags; and the identity linkage screen. A record, not a recommendation or a rating. How far to trust "holds active broker authority": it is as complete as the two FMCSA sources behind it. FMCSA froze its legacy licensing archive on 2026-05-14, so a docket known only from it (status_source legacy_li) describes that date, and a docket whose status changed afterwards and is not yet on FMCSA's live MOTUS roster is not seen. There is no independent count of real brokers to check against. Confirm the broker's current authority and bond with FMCSA before relying on it.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_carrier_identityFull identity-linkage detail for a carrier: why it's flagged and how confident that is.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_roster_changesWhich carriers on your roster changed on or after a date, and what changed: authority, insurance, out-of-service and the other tracked fields, each with its old and new value.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Which carriers on your roster changed on or after a date, and what changed: authority, insurance, out-of-service and the other tracked fields, each with its old and new value. Paid, metered: a base price plus a per-roster-entry price, both shown in get_catalog. roster_usdot_numbers is your own list of USDOT numbers (non-empty, at most settings.roster_screen_max_size distinct entries, currently 100: over the limit is a free invalid_arguments, never a truncation). since is an ISO date, YYYY-MM-DD. A roster entry that matches no carrier is listed in roster_not_found but still counts toward the price. "Nothing changed" is a complete answer and bills like any other; a roster where no entry resolves is a free not_found. How fresh this is: changes appear only when the underlying data is refreshed (roughly weekly lately, with no committed schedule), so a change made at FMCSA today may not be here yet. provenance.record_as_of says how current the data is. Only real changes are returned (the warehouse's one-time "field started being tracked" rows are not). At most settings.roster_changes_max_rows changes come back, newest first; truncated says whether more existed. Carries no contact information, and no change to legal_name, dba_name, phone or email, same as get_safety_history.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • screen_carrier_identityFree 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 9Show 9 read-only tools
  • find_carrier_by_mcFree.No findings

    Why it is in this group

    • The name "find_carrier_by_mc" says "find": a word for reading.
    Description, as the server wrote it
    Free. Finds the USDOT number for an operating-authority docket number (MC, MX or FF), so a broker holding the MC number from a rate confirmation can reach the other tools, which take a USDOT number. mc_number may be written "MC123456", "MC-123456", "mc 123456" or just "123456" (a bare number is taken as MC); zero-padding is ignored, because FMCSA's own files disagree on it. authority_holder_usdot_number is the carrier FMCSA's authority records tie the docket to, and there is never more than one. usdot_numbers lists every carrier that lists the docket (FMCSA's census lists about 26,000 dockets under a second carrier too, so a docket can legitimately appear under two), the holder first. docket_status and status_source say how current that is: "motus" is live, "legacy_li" is FMCSA's archive as of 2026-05-14, "census" is the census file's code. Returns only identifiers and a status, no names or addresses. An unknown docket is a not_found error; an unreadable one is invalid_arguments. Never billed.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_carrier_selection_recordOne dated, hashed record of what public FMCSA data shows about a carrier, built for a broker's carrier-vetting file.No findings

    Why it is in this group

    • The name "get_carrier_selection_record" says "get": a word for reading.
    Description, as the server wrote it
    One dated, hashed record of what public FMCSA data shows about a carrier, built for a broker's carrier-vetting file. Paid, flat price. It gathers, in one response: the carrier's current profile (authority, insurance flags, FMCSA safety rating and its date, out-of-service orders, fleet and classifications, MCS-150 filing date, first authority grant, revocation, suspension and reinstatement history), the SMS inspection and violation summary with out-of-service rates, the trailing-24-month crash summary, the last year's changes, and the identity-linkage triage screen, the insurance continuity history (gaps and cancellations, each with its data-through date) and the authority event history (grants, reinstatements, revocations, suspensions). review_factors lists each factor a documented review commonly considers and whether this record carries it. It is a record, not a score. It never says a carrier is safe or unsafe, "Unrated" is reported as exactly that, and it is not legal advice or a statement that choosing a carrier was reasonable. This project's own safety_tier_derived is deliberately left out. Integrity: record_hash is the SHA-256 of the record's canonical JSON (see hash_method) without record_hash and verify_url. Keep the record; later, GET verify_url (free) confirms that we issued exactly that hash, when, and for which carrier, so an edited copy is detectable. If the hash cannot be registered the call returns registry_unavailable and is not billed. An unknown USDOT number is a free not_found.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_catalogFree, unauthenticated dataset catalog.No findings

    Why it is in this group

    • The name "get_catalog" says "get": a word for reading.
    Description, as the server wrote it
    Free, unauthenticated dataset catalog. Describes every table this service sells, its fields, current pricing, and freshness. Read this before paying for anything.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_identity_sampleFree, unauthenticated sample of identity/fraud responses, covering both screen_carrier_identity's free IdentityScreen shape and check_carrier_identity's paid IdentityAssessment sha…No findings

    Why it is in this group

    • The name "get_identity_sample" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_inspection_crash_summaryA carrier's roadside inspection, violation and crash summary on its own.No findings

    Why it is in this group

    • The name "get_inspection_crash_summary" says "get": a word for reading.
    Description, as the server wrote it
    A carrier's roadside inspection, violation and crash summary on its own. Paid, flat price; billed whenever the USDOT number resolves, even if the carrier had no inspections (that is the finding). An unknown number is a free not_found. inspections (SMS data, a 24-month window that ends weeks before today: read window_end): inspection counts by driver and vehicle, out-of-service counts and rates (FMCSA's own method; no national average is carried, so cite FMCSA's), violation counts in total and by BASIC, last inspection date. When there were no inspections the measures are null, never zero, and data_quality_flags says why: inspection_summary_no_inspections (in SMS, none in the window) or inspection_summary_unavailable (in neither SMS file, so SMS says nothing either way). A carrier inspected only after window_end reads as having none. crashes (federally recordable crashes, trailing 730 days ending at the build date): counts by fatal, injury, tow-away and hazmat release, plus fatalities and injuries and the last crash date. A floor, not a total: about 19% of crash records carry no USDOT number and cannot be attributed to any carrier. Counts, not a rating: this does not say a carrier is safe or unsafe, and it carries no contact information.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_safety_historyHistorical snapshots and changelog entries for a carrier.No findings

    Why it is in this group

    • The name "get_safety_history" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_sampleFree, unauthenticated sample of carrier_profile rows.No findings

    Why it is in this group

    • The name "get_sample" says "get": a word for reading.
    Description, as the server wrote it
    Free, unauthenticated sample of carrier_profile rows. Lets a buying agent evaluate data quality before spending USDC on the paid tools.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • lookup_carrierLook up a single carrier's current profile by USDOT number.No findings

    Why it is in this group

    • The name "lookup_carrier" says "lookup": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_carriersFiltered carrier search.No findings

    Why it is in this group

    • The name "search_carriers" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:24 UTC, unchanged since Oct 22, 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
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://fmcsa-mcp-843680657471.us-central1.run.app/mcp: tools/list returned 16 tools to an anonymous client, including screen_carrier_identity (write), check_carrier_identity (write), check_address_consistency (write), confirm_identity_link (write), check_applicant_against_roster (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "confirm_identity_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "confirm_identity_link" says "link": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools16 changed.~16 changedView diff

Install

Pinned to version 0.2.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http fmcsa-carrier-intelligence https://fmcsa-mcp-843680657471.us-central1.run.app/mcp
claude mcp add --transport http fmcsa-carrier-intelligence https://fmcsa-mcp-843680657471.us-central1.run.app/mcp

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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__fmcsa-carrier-intelligence__get_catalog",
      "mcp__fmcsa-carrier-intelligence__get_sample",
      "mcp__fmcsa-carrier-intelligence__lookup_carrier",
      "mcp__fmcsa-carrier-intelligence__search_carriers",
      "mcp__fmcsa-carrier-intelligence__get_safety_history",
      "mcp__fmcsa-carrier-intelligence__get_identity_sample",
      "mcp__fmcsa-carrier-intelligence__find_carrier_by_mc",
      "mcp__fmcsa-carrier-intelligence__get_carrier_selection_record",
      "mcp__fmcsa-carrier-intelligence__get_inspection_crash_summary"
    ],
    "ask": [
      "mcp__fmcsa-carrier-intelligence__screen_carrier_identity",
      "mcp__fmcsa-carrier-intelligence__check_carrier_identity",
      "mcp__fmcsa-carrier-intelligence__check_address_consistency",
      "mcp__fmcsa-carrier-intelligence__confirm_identity_link",
      "mcp__fmcsa-carrier-intelligence__check_applicant_against_roster",
      "mcp__fmcsa-carrier-intelligence__check_roster_changes",
      "mcp__fmcsa-carrier-intelligence__check_broker_authority"
    ],
    "deny": []
  }
}

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 fmcsa-carrier-intelligence. Review it before you use it.

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/io.github.KMCTO/fmcsa-carrier-intelligence/verify?hash=61dc794af7e0131251cb9a56db600c920c6df923a7e2f2913e0269f5a506cfd5" | jq -e '.changed == false'

Pinned hash 61dc794af7e0, from Nov 9, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.KMCTO/fmcsa-carrier-intelligence/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.KMCTO/fmcsa-carrier-intelligence
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.KMCTO/fmcsa-carrier-intelligence.svg)](https://radar.anlyon.com/servers/io.github.KMCTO/fmcsa-carrier-intelligence)

Source: MCP Registry · repository. Synced Nov 9, 2026, 22:17 UTC.

FMCSA Carrier Intelligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the FMCSA Carrier Intelligence MCP server safe?

No scan can promise that. What its definitions show: 16 tools, 7 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 FMCSA Carrier Intelligence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the FMCSA Carrier Intelligence 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 FMCSA Carrier Intelligence MCP server have?

16 tools: 7 write, 9 read. screen_carrier_identity, check_carrier_identity, check_address_consistency, confirm_identity_link, check_applicant_against_roster, check_roster_changes, check_broker_authority, get_catalog and 8 more.

Does the FMCSA Carrier Intelligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the FMCSA Carrier Intelligence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the FMCSA Carrier Intelligence MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.