Wa Dmv
NPM · @PIPEWORX/MCP-WA-DMV · 2 COMPONENTS
Washington State DMV MCP — the Department of Licensing's VIN-level electric-vehicle population…
Available components
Last scanned (14 hours ago)
Scores higher than 69% 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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-wa-dmv). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability55
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1008 tokens (~504/item across 2 items; 2 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 Management23
- Stability observed for 7 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +3
- Stability: unverified → 0.20 ▲ functional
- 29 Oct 26 77
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-wa-dmv@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-wa-dmv |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-wa-dmv/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560990521 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:cb8d6a6363b580c7940cb1f7b1bf21036e99cfe1fd49667e4da76d0fb29d78771dce09b9000b21b786d53b600e3a891bc89a1823a7f10819dacac1117 |
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 →
wa_dmv_ev_population ~480
Count electric vehicles currently registered in Washington State, from the Department of Licensing (Washington DMV) VIN-level Electric Vehicle Population file — one row per registered vehicle, so these are fleet counts rather than sales or transactions. Breaks down by county, city, ZIP code, make, model, model year, legislative district, electric utility, or vehicle type, and separates battery-electric (BEV) from plug-in hybrid (PHEV). Reports average and median electric range and clean-alternative-fuel-vehicle eligibility. Answers "how many EVs are registered in Washington", "how many Teslas are in King County", "EV count by ZIP in Seattle", "BEV versus PHEV split in Washington", and "which Washington legislative district has the most electric vehicles".
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name in plain mixed case, e.g. "Seattle", "Bellevue", "Tacoma". |
| county | string | – | Washington county in plain mixed case, e.g. "King", "Pierce", "Snohomish", "Spokane". |
| ev_type | string | – | Drivetrain: "BEV" or "battery electric" for Battery Electric Vehicle (BEV), "PHEV" or "plug-in hybrid" for Plug-in Hybrid Electric Vehicle (PHEV). |
| group_by | string | – | Breakdown dimension: county, city, zip, make, model, model_year, ev_type, cafv_type, legislative_district, electric_utility. Defaults to county. |
| legislative_district | string | – | Washington legislative district number, e.g. "44". |
| limit | number|string | – | Max rows to return (default 25, max 200). Raise it to 39 to cover every Washington county. |
| make | string | – | Vehicle make, upper case in the source and matched as a substring, e.g. "TESLA", "CHEVROLET", "RIVIAN". |
| model | string | – | Model name, upper case in the source and matched as a substring, e.g. "MODEL 3", "BOLT EV", "LEAF". |
| model_year | string | – | Four-digit model year, e.g. "2025". |
| zip | string | – | Five-digit ZIP code, e.g. "98052". |
No output schema declared.
No examples provided.
wa_dmv_registration_transactions ~474
Count Washington State vehicle registration transactions — original registrations and renewals processed by the Department of Licensing (Washington DMV) — for one fiscal year or one calendar month, broken down by county of the registered owner, county where the transaction happened, fuel type, use class, or month. Answers "how many vehicle registrations did King County process in fiscal 2026", "monthly registration volume in Washington", "diesel registration transactions by county", and "which Washington counties process the most registrations". Each transaction is an event, so a county with 1.9 million transactions in a year has far fewer vehicles than that; for the size of Washington's registered electric fleet use wa_dmv_ev_population.
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | – | County of the registered owner, plain mixed case, e.g. "King", "Pierce", "Spokane". |
| fuel_type | string | – | Fuel; plain words are mapped to the published labels, e.g. "gas" → Gasoline, "flex" → Flex Fuel/Gasoline, "cng" → Compressed Natural Gas. Published labels: Gasoline, Unpowered, Diesel, Flex Fuel/Gaso… |
| group_by | string | – | Breakdown dimension: county, transaction_county, fuel, use_class, month, fiscal_year. Defaults to county. |
| limit | number|string | – | Max rows to return (default 25, max 200). Raise it to 39 to cover every Washington county. |
| month | string | – | A single calendar month as YYYY-MM, e.g. "2026-05". Takes precedence over `year`. |
| transaction_county | string | – | County where the transaction was processed, plain mixed case, e.g. "King". Differs from `county` when an owner registers away from home. |
| use_class | string | – | Use class as published, matched as a substring, e.g. "Passenger Car", "Truck", "Trailer", "Motorcycle". |
| year | string | – | Four-digit state fiscal year from 2017 onward, e.g. "2026". Defaults to the latest year published. |
No output schema declared.
No examples provided.
How do I install the Wa Dmv MCP server?
Wa Dmv runs locally as an npm package, launched with npx -y @pipeworx/mcp-wa-dmv. 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-wa-dmv
claude mcp add pipeworx-io-wa-dmv -- npx -y @pipeworx/mcp-wa-dmv
What is the Wa Dmv MCP server?
Wa Dmv is an MCP server listed in the public MCP registry as io.github.pipeworx-io/wa-dmv. Washington State DMV MCP, the Department of Licensing's VIN-level electric-vehicle population… This page covers its npm package (@pipeworx/mcp-wa-dmv).
Is the Wa Dmv MCP server safe to use?
Wa Dmv scores 81 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. Its build provenance is signed and verified. 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 Wa Dmv MCP server expose?
Wa Dmv exposes 2 tools: wa_dmv_ev_population, wa_dmv_registration_transactions. Their descriptions and schemas cost roughly 954 tokens of context every time the server is loaded.
Is the Wa Dmv MCP server still maintained?
Wa Dmv 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 Wa Dmv MCP server under?
Wa Dmv declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.