Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Hpms Aadt is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
22
downloads a day
local
or remote
261
downloads in 30d
What it does
FHWA, Highway Performance Monitoring System (HPMS): annual average daily traffic (AADT) per…
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user hpms-aadt-mcp '--' npx -y @pipeworx/mcp-hpms-aadt
# 2 — ask your agent for something these tools do
# aadt_near_point, aadt_by_route, aadt_top_segments and 1 more
Hpms Aadt costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PIAll 1913 servers
pipeworx-io1913 servers
29 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user hpms-aadt-mcp '--' npx -y @pipeworx/mcp-hpms-aadtReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://gateway.pipeworx.io/hpms-aadt/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http hpms-aadt-mcp https://gateway.pipeworx.io/hpms-aadt/mcpFree on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take PIPEWORX_API_KEY (Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lat | number | yes | Latitude, WGS84 decimal degrees. |
| lon | number | yes | Longitude, WGS84 decimal degrees (negative in the US). |
| state | string | yes | Two-letter USPS state code (50 states, DC, PR), e.g. "CA". Required: route_id and county_id are state-specific. |
| radius_m | number | no | Search radius in metres (10-5000, default 500). |
| year | number | no | HPMS data year (e.g. 2024). Default: newest year published for the state. Call aadt_layers to see which years exist. |
| limit | number | no | Max segments (1-500, default 50). |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter USPS state code (50 states, DC, PR), e.g. "CA". Required: route_id and county_id are state-specific. |
| route | string | yes | route_id prefix, e.g. "I089", "IH0035", "SHS_101". |
| county | number | no | Optional state-coded county_id (county FIPS code). |
| min_aadt | number | no | Optional minimum AADT. |
| year | number | no | HPMS data year (e.g. 2024). Default: newest year published for the state. Call aadt_layers to see which years exist. |
| limit | number | no | Max segments (1-500, default 50). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter USPS state code (50 states, DC, PR), e.g. "CA". Required: route_id and county_id are state-specific. |
| county | number | no | Optional state-coded county_id (county FIPS code). |
| f_system | number | no | 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. |
| year | number | no | HPMS data year (e.g. 2024). Default: newest year published for the state. Call aadt_layers to see which years exist. |
| limit | number | no | Max segments (1-500, default 50). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter USPS state code (50 states, DC, PR), e.g. "CA". Required: route_id and county_id are state-specific. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Hpms Aadt or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.1.0 · scanned 1 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digeste70d80286278eac2a0695c8d960330c7d5c1c589fe47ec92790ba01b9b98dec2
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digeste70d80286278eac2
Scanned2026-11-01
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Hpms Aadt can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.