Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FMCSA Carrier Intelligence

REMOTE · FMCSA-MCP-843680657471.US-CENTRAL1.RUN.APP

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

+2 this week 73 Trust /100

Last scanned (4 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4443 tokens (~277/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 +1
    • Stability: 0.97 → pass security
  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://fmcsa-mcp-843680657471.us-central1.run.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.a.run.app CN=WR2,O=Google Trust Services,C=US 7 Oct 2026 30 Dec 2026 ECDSA 256 SHA256-RSA 53da11951e5eb49012fb872c3cb3e54d
SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more
CN=WR2,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a07c4cded100ad9d66a5107b98
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of fmcsa-mcp-843680657471.us-central1.run.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
run.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://fmcsa-mcp-843680657471.us-central1.run.app/mcp Verified 200
http (plaintext) http://fmcsa-mcp-843680657471.us-central1.run.app/mcp HTTPS enforced 302 https://fmcsa-mcp-843680657471.us-central1.run.app/mcp
MCP tools · 16 exposed · ~4,396 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_address_consistency ~90

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.

NameTypeReqDescription
usdot_numberintegeryes–

No output schema declared.

No examples provided.

check_applicant_against_roster ~419

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.

NameTypeReqDescription
roster_usdot_numbersarrayyes–
usdot_numberintegeryes–

No output schema declared.

No examples provided.

check_broker_authority ~396

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.

NameTypeReqDescription
mc_number–––
usdot_number–––

No output schema declared.

No examples provided.

check_carrier_identity ~459

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.

NameTypeReqDescription
usdot_numberintegeryes–

No output schema declared.

No examples provided.

check_roster_changes ~327

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.

NameTypeReqDescription
roster_usdot_numbersarrayyes–
sincestringyes–

No output schema declared.

No examples provided.

confirm_identity_link ~325

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.

NameTypeReqDescription
usdot_number_aintegeryes–
usdot_number_bintegeryes–

No output schema declared.

No examples provided.

find_carrier_by_mc ~276

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.

NameTypeReqDescription
mc_numberstringyes–

No output schema declared.

No examples provided.

get_carrier_selection_record ~361

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.

NameTypeReqDescription
usdot_numberintegeryes–

No output schema declared.

No examples provided.

get_catalog ~40

Free, unauthenticated dataset catalog. Describes every table this service sells, its fields, current pricing, and freshness. Read this before paying for anything.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_identity_sample ~69

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_inspection_crash_summary ~307

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.

NameTypeReqDescription
usdot_numberintegeryes–

No output schema declared.

No examples provided.

get_safety_history ~432

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.

NameTypeReqDescription
since_date–––
usdot_numberintegeryes–

No output schema declared.

No examples provided.

get_sample ~36

Free, unauthenticated sample of carrier_profile rows. Lets a buying agent evaluate data quality before spending USDC on the paid tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lookup_carrier ~323

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.

NameTypeReqDescription
claimed_city–––
claimed_name–––
claimed_state–––
claimed_street–––
claimed_zip–––
usdot_numberintegeryes–

No output schema declared.

No examples provided.

screen_carrier_identity ~267

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.

NameTypeReqDescription
usdot_numberintegeryes–

No output schema declared.

No examples provided.

search_carriers ~269

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.

NameTypeReqDescription
authority_status–––
cargo_type–––
include_inactiveboolean––
limitinteger––
safety_tier–––
state–––

No output schema declared.

No examples provided.

Install

How do I install the FMCSA Carrier Intelligence MCP server?

FMCSA Carrier Intelligence is a hosted endpoint at https://fmcsa-mcp-843680657471.us-central1.run.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · fmcsa-mcp-843680657471.us-central1.run.app

# add to Claude Code
claude mcp add --transport http kmcto-fmcsa-carrier-intelligence 'https://fmcsa-mcp-843680657471.us-central1.run.app/mcp'
Common questions

What is the FMCSA Carrier Intelligence MCP server?

FMCSA Carrier Intelligence is an MCP server listed in the public MCP registry as io.github.KMCTO/fmcsa-carrier-intelligence. US carrier vetting on FMCSA data: authority, insurance, safety, identity links. Pay per call (x402). This page covers its hosted endpoint (https://fmcsa-mcp-843680657471.us-central1.run.app/mcp).

Is the FMCSA Carrier Intelligence MCP server safe to use?

FMCSA Carrier Intelligence scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the FMCSA Carrier Intelligence MCP server expose?

FMCSA Carrier Intelligence exposes 16 tools: get_catalog, get_sample, lookup_carrier, search_carriers, get_safety_history, and 11 more. Their descriptions and schemas cost roughly 4,396 tokens of context every time the server is loaded.

Does the FMCSA Carrier Intelligence MCP server require authentication?

No. We connected to FMCSA Carrier Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the FMCSA Carrier Intelligence MCP server still maintained?

FMCSA Carrier Intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.