dmv_ev_adoption
Pack: us-dmv · Endpoint: https://gateway.pipeworx.io/us-dmv/mcp
Electric-vehicle adoption from state DMV registration records: how many battery-electric and plug-in hybrid vehicles are registered in a place, which makes and models people actually own there, and what share of all registered vehicles is electric. Covers California (ZIP-level fuel mix with EV share, 2019-2026 snapshots), Washington (VIN-level EV population by county, city, ZIP, make, model), New York (electric registrations by county or ZIP), Maryland (EV and plug-in hybrid by county or ZIP, monthly), Pennsylvania (BEV/PHEV/hybrid plus EV percentage by county, quarterly), Delaware, Hawaii (annual series since 1999) and Connecticut. Answers “how many Teslas are registered in King County”, “EV share in ZIP 94002”, “which Maryland county has the most EVs”, or “EV adoption trend in Hawaii”. Returns plug-in counts, and total-fleet share wherever the state publishes a denominator.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
state | string | yes | Two-letter state code. Supported: CA, CT, DE, HI, MD, NY, PA, WA. |
county | string | no | County name, e.g. “King” (WA), “Montgomery” (MD/PA), “WESTCHESTER” (NY). |
zip | string | no | Five-digit ZIP code (CA, WA, NY, MD), e.g. “94002”. |
make | string | no | Vehicle make substring, e.g. “TESLA”, “RIVIAN”, “HYUNDAI”. |
model_year | string | no | Four-digit model year, e.g. “2025”. |
year | string | no | Snapshot year: CA 2019-2026, PA 2023-2026, HI any year from 1999. Defaults to the most recent. |
month | string | no | Maryland only — YYYY/MM, e.g. “2026/06”. Defaults to the latest month published. |
group_by | string | no | Breakdown dimension. CA: fuel (default, returns full mix + EV share), zip, make, model_year. WA: county, city, zip, make, model, model_year, ev_type, legislative_district. NY: county, zip, city, make. CT: city, make, model, model_year. |
limit | number,string | no | Max rows to return (default 25, max 200). |
_apiKey | string | no | Optional Socrata app token; the public endpoints work without one. |
Example call
Arguments
{
"state": "CA",
"zip": "94002"
}
curl
curl -X POST https://gateway.pipeworx.io/us-dmv/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"dmv_ev_adoption","arguments":{"state":"CA","zip":"94002"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('dmv_ev_adoption', {
"state": "CA",
"zip": "94002"
});
More examples
{
"state": "WA",
"county": "King",
"group_by": "make",
"limit": 10
}
{
"state": "MD",
"county": "Montgomery"
}
{
"state": "HI",
"limit": 10
}
Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"us-dmv": {
"url": "https://gateway.pipeworx.io/us-dmv/mcp"
}
}
}
See Getting Started for client-specific install steps.