{
  "markdown": "# @pipeworx/wa-dmv\n\nWashington State DMV MCP — the Department of Licensing's VIN-level electric-vehicle population and its monthly vehicle-registration transaction counts. Keyless.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\nWashington has no agency called \"the DMV\": vehicle registration and driver licensing are run by the **Department of Licensing (DOL)**. Both names appear in the tool descriptions because agents search for \"WA DMV\".\n\n## Tools\n\n| Tool | What it returns |\n|------|-----------------|\n| `wa_dmv_ev_population(...)` | Counts of registered electric vehicles by county, city, ZIP, make, model, model year, legislative district, electric utility or drivetrain, with BEV/PHEV split and average electric range. A true fleet snapshot — one source row per registered vehicle. |\n| `wa_dmv_registration_transactions(...)` | Registration transactions (new registrations and renewals) for one fiscal year or one calendar month, by owner county, transaction county, fuel type, use class or month. |\n\n## Auth\n\nKeyless. Both datasets are public Socrata resources on `data.wa.gov`; no app token is required at the volumes this pack issues.\n\n## Per-state gotchas\n\n- **`hmzg-s6q4` counts transactions, not vehicles.** This is the trap in this state. King County processes roughly 160,000 registration transactions a month, so summing every month back to fiscal 2017 returns 17.6M for one county — arithmetically correct and completely misleading. `wa_dmv_registration_transactions` therefore pins every query to one fiscal year (the latest by default) or one calendar month, and labels the result \"registration transactions during \\<period\\>\". For the size of a registered fleet, use `wa_dmv_ev_population`.\n- **Washington fiscal years run July 1 – June 30.** Fiscal 2026 covers July 2025 through June 2026. Data starts at fiscal 2017.\n- **The `month` column stores the last day of the month.** Filter it with `date_trunc_ym`, which the `month` argument (`YYYY-MM`) does for you; results are reported back as `YYYY-MM`.\n- **Case differs by column.** Counties and cities are plain mixed case (`King`, `Seattle`); makes and models are upper case (`TESLA`, `MODEL 3`).\n- **Roughly two-thirds of EV rows carry `electric_range` 0.** 188,456 of 289,564 vehicles sit in the \"Eligibility unknown as battery range has not been researched\" CAFV bucket with a literal zero range, which drags any average down. The genuinely researched vehicles average ~133 miles. Treat `average_electric_range_miles` as a floor, not a spec.\n- **Socrata reports an all-zero average as the string `\"0E-24\"`.** The shared `govNumber` helper strips exponent notation into NaN, so this pack parses averages with its own `avgMiles`.\n- **`ev_type` has exactly two values**, spelled in full: `Battery Electric Vehicle (BEV)` and `Plug-in Hybrid Electric Vehicle (PHEV)`. The `ev_type` argument accepts `BEV` / `PHEV` / plain phrases.\n- **`sum_of_returned_rows` is not a total.** Row lists are cut off by `limit`; `total_electric_vehicles` and `total_transactions_in_period` are separate full counts over the same filters and are the figures to quote.\n\n## Data sources\n\n- EV population — https://data.wa.gov/resource/f6w7-q2d2.json (Electric Vehicle Population Data)\n- Registration transactions — https://data.wa.gov/resource/hmzg-s6q4.json (Vehicle Registration Transactions by County)\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"wa-dmv\": {\n      \"url\": \"https://gateway.pipeworx.io/wa-dmv/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/wa-dmv/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Wa Dmv data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 5441,
  "sha": "3dd5ddec8e4bca94b91dcacb2117447ad823237634c361cfdd06f0af0533f9bb",
  "repo_slug": "pipeworx-io/mcp-wa-dmv",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_wa_dmv_9d4c43ec/readme"
}