Hpms Aadt
NPM · @PIPEWORX/MCP-HPMS-AADT · 2 COMPONENTS
FHWA, Highway Performance Monitoring System (HPMS): annual average daily traffic (AADT) per…
Available components
Last scanned (10 hours ago)
Scores higher than 39% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 866 tokens (~216/item across 4 items; 4 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 68
First indexed and scored.
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 · Analysed npm/@pipeworx/mcp-hpms-aadt@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
aadt_by_route ~267
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, "IH0035" in Texas, "SHS_101" in California); use aadt_top_segments to see a state's id style. A highway may carry several ids (e.g. IH0035-KG, IH0035-LG). Busiest segments first.
| Name | Type | Req | Description |
|---|---|---|---|
| county | number | – | Optional state-coded county_id (county FIPS code). |
| limit | number | – | Max segments (1-500, default 50). |
| min_aadt | number | – | Optional minimum AADT. |
| route | string | yes | route_id prefix, e.g. "I089", "IH0035", "SHS_101". |
| state | string | yes | Two-letter USPS state code (50 states, DC, PR), e.g. "CA". Required: route_id and county_id are state-specific. |
| year | number | – | HPMS data year (e.g. 2024). Default: newest year published for the state. Call aadt_layers to see which years exist. |
No output schema declared.
No examples provided.
aadt_layers ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | Two-letter USPS state code (50 states, DC, PR), e.g. "CA". Required: route_id and county_id are state-specific. |
No output schema declared.
No examples provided.
aadt_near_point ~235
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 reported by the state (not a counter reading). state is required. Returns route_id, functional class, AADT with single-unit and combination-truck splits, milepost range, data_year.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude, WGS84 decimal degrees. |
| limit | number | – | Max segments (1-500, default 50). |
| lon | number | yes | Longitude, WGS84 decimal degrees (negative in the US). |
| radius_m | number | – | Search radius in metres (10-5000, default 500). |
| state | string | yes | Two-letter USPS state code (50 states, DC, PR), e.g. "CA". Required: route_id and county_id are state-specific. |
| year | number | – | HPMS data year (e.g. 2024). Default: newest year published for the state. Call aadt_layers to see which years exist. |
No output schema declared.
No examples provided.
aadt_top_segments ~225
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 reported by the state. Also the way to learn a state's route_id naming style.
| Name | Type | Req | Description |
|---|---|---|---|
| county | number | – | Optional state-coded county_id (county FIPS code). |
| f_system | number | – | Optional functional system 1-7: 1 Interstate, 2 other freeway, 3 other principal arterial, 4 minor arterial, 5 major collector, 6 minor collector, 7 local. |
| limit | number | – | Max segments (1-500, default 50). |
| state | string | yes | Two-letter USPS state code (50 states, DC, PR), e.g. "CA". Required: route_id and county_id are state-specific. |
| year | number | – | HPMS data year (e.g. 2024). Default: newest year published for the state. Call aadt_layers to see which years exist. |
No output schema declared.
No examples provided.
How do I install the Hpms Aadt MCP server?
Hpms Aadt runs locally as an npm package, launched with npx -y @pipeworx/mcp-hpms-aadt. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-hpms-aadt
claude mcp add pipeworx-io-hpms-aadt -- npx -y @pipeworx/mcp-hpms-aadt
What is the Hpms Aadt MCP server?
Hpms Aadt is an MCP server listed in the public MCP registry as io.github.pipeworx-io/hpms-aadt. FHWA, Highway Performance Monitoring System (HPMS): annual average daily traffic (AADT) per… This page covers its npm package (@pipeworx/mcp-hpms-aadt).
Is the Hpms Aadt MCP server safe to use?
Hpms Aadt scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Hpms Aadt MCP server expose?
Hpms Aadt exposes 4 tools: aadt_near_point, aadt_by_route, aadt_top_segments, aadt_layers. Their descriptions and schemas cost roughly 809 tokens of context every time the server is loaded.
Is the Hpms Aadt MCP server still maintained?
Hpms Aadt 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.
What licence is the Hpms Aadt MCP server under?
Hpms Aadt declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Hpms Aadt MCP server?
VerifyMCP ran 16 checks on Hpms Aadt, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.