{
  "markdown": "# @pipeworx/hi-dmv\n\nHawaii vehicle-registration MCP — the statewide cumulative count of hybrid and electric\nvehicles registered in Hawaii, as an annual series from 1999 to the present.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n- `hi_dmv_ev_registrations(year?, limit?)` — hybrid and battery-electric counts per year with a\n  combined total, plus the year-over-year change and growth rate. Answers \"how many electric\n  vehicles are in Hawaii\", \"how many EVs were registered in Hawaii in 2020\", \"EV adoption trend\n  in Hawaii\".\n\n## Auth\n\nKeyless.\n\n## Hawaii has no state DMV\n\nVehicle registration in Hawaii is administered by the **four counties** — Honolulu, Hawaii,\nMaui and Kauai — not by a state motor-vehicle agency. The statewide statistics are compiled and\npublished by **DBEDT**, the state Department of Business, Economic Development and Tourism.\nThat is why this pack has one statewide series and no office locator, and why the series\ncarries no county split: the counties register, DBEDT aggregates.\n\n## Grain\n\nA clean annual time series, one row per year, 1999 through 2024 (26 rows). Counts are\n**cumulative registered vehicles at the end of each year**, so a rising total means the fleet\ngrew; the tool computes `change_from_prior_year` and `growth_pct` per row so a trend question\nneeds no arithmetic from the caller. Rows are never summed across years — they are cumulative\nsnapshots of largely the same vehicles.\n\nVerified live 2026-07-29: 2024 → hybrid 31,284, electric 35,242, total 66,526 · 2023 → 27,658 /\n29,239 / 56,897 · 1999 → electric 10.\n\n## Data sources\n\n- `https://opendata.hawaii.gov/api/3/action/datastore_search?resource_id=4d4c0403-8f04-4f74-879d-64669f1437b1`\n  — DBEDT \"Cumulative Hybrid & Electric Vehicles Registered\".\n\nTwo shapes worth knowing before touching this resource:\n\n- Counts arrive as **thousands-separated strings** (`\"31,284\"`), not numbers.\n- A missing value arrives as the **padded string `\" -   \"`**, not null and not zero. 1999 has\n  no hybrid figure at all; reading that placeholder as 0 invents a data point, so the pack\n  resolves it to `null` and the response note says what null means.\n- Column names carry spaces and mixed case: `Year`, `Hybrid Electric Vehicles`,\n  `Electric Vehicle`, `Total`.\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"hi-dmv\": {\n      \"url\": \"https://gateway.pipeworx.io/hi-dmv/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/hi-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 Hi 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": 4355,
  "sha": "ff08c9e06f346110b9a7afdd7c50448992a1450b98280f609b1bc507058493f6",
  "repo_slug": "pipeworx-io/mcp-hi-dmv",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_hi_dmv_9b3e9bcf/readme"
}