FMCSA Carrier Intelligence
v0.2.0US carrier vetting on FMCSA data: authority, insurance, safety, identity links. Pay per call (x402)
Endpoint health
online- Last checked
- 11/20/2026, 4:17:01 AM
- Latency
- 57 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.KMCTO%2Ffmcsa-carrier-intelligence
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.KMCTO/fmcsa-carrier-intelligence": {
"url": "https://fmcsa-mcp-843680657471.us-central1.run.app/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
16 shown · authentication unknown
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. Paid via x402: 0.01 USDC per call (on Solana, Base or Polygon), or prepaid API-key credit. Billed only when the call returns records; a miss is free.
Schema valid · SHA-256 f40a7bc1166b…
View input schema
{ "type": "object", "properties": { "usdot_number": { "description": "Carrier USDOT number (digits only), the canonical FMCSA carrier identifier.", "title": "Usdot Number", "type": "integer" } }, "required": [ "usdot_number" ], "title": "check_address_consistencyArguments" }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. Paid via x402: 0.08 USDC + 0.01 USDC per roster entry (on Solana, Base or Polygon), or prepaid API-key credit. Billed only when the call returns records; a miss is free.
Connections
streamable-http
https://fmcsa-mcp-843680657471.us-central1.run.app/mcp