Hi Dmv

@pipeworx/hi-dmv

Hawaii vehicle-registration MCP — the statewide cumulative count of hybrid and electric vehicles registered in Hawaii, as an annual series from 1999 to the present.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

• hi_dmv_ev_registrations(year?, limit?) — hybrid and battery-electric counts per year with a combined total, plus the year-over-year change and growth rate. Answers "how many electric vehicles are in Hawaii", "how many EVs were registered in Hawaii in 2020", "EV adoption trend in Hawaii".

Auth

Keyless.

Hawaii has no state DMV

Vehicle registration in Hawaii is administered by the four counties — Honolulu, Hawaii, Maui and Kauai — not by a state motor-vehicle agency. The statewide statistics are compiled and published by DBEDT, the state Department of Business, Economic Development and Tourism. That is why this pack has one statewide series and no office locator, and why the series carries no county split: the counties register, DBEDT aggregates.

Grain

A clean annual time series, one row per year, 1999 through 2024 (26 rows). Counts are cumulative registered vehicles at the end of each year, so a rising total means the fleet grew; the tool computes change_from_prior_year and growth_pct per row so a trend question needs no arithmetic from the caller. Rows are never summed across years — they are cumulative snapshots of largely the same vehicles.

Verified live 2026-07-29: 2024 → hybrid 31,284, electric 35,242, total 66,526 · 2023 → 27,658 / 29,239 / 56,897 · 1999 → electric 10.

Data sources

• https://opendata.hawaii.gov/api/3/action/datastore_search?resource_id=4d4c0403-8f04-4f74-879d-64669f1437b1 — DBEDT "Cumulative Hybrid & Electric Vehicles Registered".

Two shapes worth knowing before touching this resource:

• Counts arrive as thousands-separated strings ("31,284"), not numbers.
• A missing value arrives as the padded string " - ", not null and not zero. 1999 has no hybrid figure at all; reading that placeholder as 0 invents a data point, so the pack resolves it to null and the response note says what null means.
• Column names carry spaces and mixed case: Year, Hybrid Electric Vehicles, Electric Vehicle, Total.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "hi-dmv": {
      "url": "https://gateway.pipeworx.io/hi-dmv/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/hi-dmv/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1679+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/hi_dmv_ev_registrations \
  -H 'Content-Type: application/json' \
  -d '{"year":"2024"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/hi_dmv_ev_registrations. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "hi-dmv": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-hi-dmv"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-hi-dmv

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Hi Dmv data" })

The gateway picks the right tool and fills the arguments automatically.

More

• Docs and guides
• pipeworx.io

License

MIT