{
  "markdown": "# @pipeworx/de-dmv\n\nDelaware DMV MCP — registered vehicles by fuel type, EV adoption, the state's electric\nvehicle and charging-equipment rebate awards, and reported traffic crashes.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n- `de_dmv_vehicle_registrations(fuel_type?)` — the whole Delaware fleet by fuel type, with a\n  statewide total. Answers \"how many vehicles are registered in Delaware\".\n- `de_dmv_ev_adoption()` — battery-electric and plug-in hybrid counts plus their share of\n  every registered Delaware vehicle. Answers \"what percentage of cars in Delaware are electric\".\n- `de_dmv_ev_rebates(group_by?, county?, make?, vehicle_type?, purchase_year?, limit?)` —\n  Delaware Clean Vehicle Rebate Program awards: amount, county, city, ZIP, purchase date,\n  vehicle type, make, model. Answers \"does Delaware have an EV rebate and how much is it\".\n- `de_dmv_charger_rebates(group_by?, county?, brand?, year?, limit?)` — rebates paid toward\n  home and workplace charging stations. Answers \"does Delaware pay for a home EV charger\".\n- `de_dmv_crash_stats(group_by?, year?, county?, alcohol_involved?, …, limit?)` — reported\n  traffic crashes by year, county, weather, light, road surface, impact or day of week.\n\n## Auth\n\nKeyless.\n\n## `Electric+Gas` means plug-in hybrid\n\nDelaware's fuel-type snapshot uses two labels a reader will misread:\n\n| Published label | What it actually is |\n|---|---|\n| `Electric` | battery-electric vehicle (BEV) |\n| `Electric+Gas` | **plug-in hybrid** — a grid-charged battery plus a petrol engine |\n\n`Electric+Gas` is not flex-fuel and not a conventional hybrid. It is also the *larger* of the\ntwo categories (42,287 vs 17,075), so treating it as anything else moves Delaware's EV numbers\nby a factor of three. `de_dmv_ev_adoption` reports both separately and sums them into\n`plugin_vehicles`.\n\nVerified live 2026-07-29 (snapshot refreshed 2026-07-01): Gas 798,738 · Other (Or None) 88,899\n· Electric+Gas 42,287 · Diesel 36,217 · Electric 17,075 · Propane 627 · Comp. Nat. Gas 68 ·\nLiquefied Gas 54 · Convertible 16 · Ethanol 1. Statewide total **983,982**; plug-in share 6.0%.\n\n## Grain\n\nThe fuel snapshot is **statewide** — no county or ZIP breakdown exists in it, and the returned\n`total_vehicles` genuinely is the whole Delaware fleet. The rebate and crash files *do* carry\ncounty, city and ZIP, so those tools group by them.\n\n## Hand-typed values in the rebate files\n\nBoth rebate files were keyed by hand and the pack folds the variants together, because a raw\ngroup-by splits one county across four spellings:\n\n- county: `New Castle` / `new Castle` / `new castle` / `New Caslte`, plus the *city* `Newark`\n  and `Rehoboth Beach` sitting in the county column.\n- vehicle type: `Electric` / `electric` / `BEV`; `Plug-in Hybrid` / `plug in hybrid`.\n- charger brand: `Juicebox` / `JuiceBox` / `Juice Box`.\n- a few purchase dates are transcription errors — one reads **1953** — so filter by\n  `purchase_year` rather than trusting min/max of the date column.\n- two charger-rebate rows carry a corrupted award year of **2081**; real years run 2015 onward.\n\nCharger rebates range from **$18.66** (a home cord) to **$48,816** (a multi-port workplace or\npublic installation) in the same file, so an average rebate sits far above what a household\nreceives. The tool reports awards, total dollars, average rebate and average station cost\ntogether for exactly that reason.\n\n## Data sources\n\n- `https://data.delaware.gov/resource/ity3-3688.json` — Registered Vehicles by Fuel Type\n  (10 rows, statewide, refreshed monthly; 2026-07-01 at time of writing).\n- `https://data.delaware.gov/resource/8z8z-di7f.json` — State Rebates for Alternative Fuel\n  Vehicles: 7,758 awards, ~$17.15M paid, 2015 onward.\n- `https://data.delaware.gov/resource/a9zd-p6sk.json` — Electric Vehicle Charging Equipment\n  Rebates: 778 awards, ~$2.81M paid.\n- `https://data.delaware.gov/resource/827n-m6xc.json` — Public Crash Data: ~37,000 reported\n  crashes a year, crash years 2009 through 2025, three counties.\n\n**Rejected while building:** `f3pu-7vjx` (\"Alternative Vehicle Rebates, by Year, 2014 to\nPresent\") reports the same 7,758-row count as `8z8z-di7f` but publishes **no columns** — every\nrow comes back as `{}` and its metadata column list is empty. It is an unusable duplicate of\nthe rebate file, so no tool wraps it.\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"de-dmv\": {\n      \"url\": \"https://gateway.pipeworx.io/de-dmv/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/de-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 De 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": 6423,
  "sha": "31ad4a37a964981587e26a2a2e97dbcfe6b85b5c4c143bb9ba98ddefc5daba1a",
  "repo_slug": "pipeworx-io/mcp-de-dmv",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_de_dmv_6db71aaf/readme"
}