@pipeworx/hpms-aadt

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/hpms-aadt’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 4

US road traffic volume (AADT, annual average daily traffic) per roadway section, by state and data year, from the Federal Highway Administration’s Highway Performance Monitoring System.

Tools

• aadt_near_point(lat, lon, state, radius_m?, year?, limit?) - road segments within a radius of a point, busiest first.
• aadt_by_route(state, route, county?, min_aadt?, year?, limit?) - segments whose route_id starts with a prefix, e.g. “I089” (Vermont), “IH0035” (Texas), “SHS_101” (California).
• aadt_top_segments(state, county?, f_system?, year?, limit?) - the busiest segments in a state, optionally by county or functional class (1 Interstate to 7 Local). Also shows a state’s route_id naming style.
• aadt_layers(state) - which data years exist for a state and which columns each carries.

Every response carries data_year, data_as_of, source, a caveat, total_matching, returned and truncated. A query that matches no segment with a reported AADT fails with a narrowing hint rather than returning an empty list.

Auth

Keyless.

Data sources

• FHWA (U.S. Department of Transportation), Highway Performance Monitoring System (HPMS) - public-release state datasets, one per state and data year (50 states, DC, PR; data years 2020 and 2022-2025 for nearly all). US federal data, public domain. Answered live on every request; nothing is copied.

Things to know

• AADT is the value for a roadway section as reported by the state to FHWA, partly sampled and expanded. It is not a raw counter reading, and rows are segments (begin and end milepost), not count stations.
• route_id is state-specific free text. There is no national route key, so “I-95 across states” is not one query. A highway can carry several ids in one state (for example a mainline and a frontage designation).
• state is required: county codes and route ids only mean something within a state, and the pack does not guess a state from a point.
• The newest data years drop the route number and route name columns, and one state drops section length. The pack reads each year’s column list and asks only for columns that exist, because requesting a missing column is a hard error upstream.
• Many segments have no reported AADT; every query filters to segments that do. Sorting without that filter puts the empty ones first.
• Large states can be slow on a cold row count, so total_matching is best-effort; when it does not arrive in time it is null and truncated is inferred from the page size.
• Duplicate-looking rows can occur (the same section reported more than once); they are returned as published.

Tools

• aadt_near_point — US road traffic volume (AADT, annual average daily traffic) for road segments within a radius of a lat/lon, busiest first. Data: FHWA Highway Performance Monitoring System, per roadway section as repo
• aadt_by_route — US road traffic volume (AADT) for segments of a named route in one state, from FHWA HPMS. route is a case-insensitive PREFIX of the state’s route_id (state-specific free text, e.g. “I089” in Vermont,
• aadt_top_segments — The busiest road segments in a US state by AADT (annual average daily traffic), optionally within one county or functional class (1 Interstate … 7 Local). From FHWA HPMS; per roadway section as repo
• aadt_layers — Which FHWA HPMS data years exist for a US state and which columns each year carries (the newest years drop route number/name columns), so callers can pick a year before querying.