# Delaware DMV [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/pipeworx-io/mcp-de-dmv  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/delaware-dmv

## Description
Delaware DMV: registrations by fuel type, EV and charger rebates, crash statistics

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "delaware-dmv": {
    "url": "https://pipeworx.io"
  }
}
```

## Documentation & README

# @pipeworx/de-dmv

Delaware DMV MCP — registered vehicles by fuel type, EV adoption, the state's electric
vehicle and charging-equipment rebate awards, and reported traffic crashes.

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.

## Tools

- `de_dmv_vehicle_registrations(fuel_type?)` — the whole Delaware fleet by fuel type, with a
  statewide total. Answers "how many vehicles are registered in Delaware".
- `de_dmv_ev_adoption()` — battery-electric and plug-in hybrid counts plus their share of
  every registered Delaware vehicle. Answers "what percentage of cars in Delaware are electric".
- `de_dmv_ev_rebates(group_by?, county?, make?, vehicle_type?, purchase_year?, limit?)` —
  Delaware Clean Vehicle Rebate Program awards: amount, county, city, ZIP, purchase date,
  vehicle type, make, model. Answers "does Delaware have an EV rebate and how much is it".
- `de_dmv_charger_rebates(group_by?, county?, brand?, year?, limit?)` — rebates paid toward
  home and workplace charging stations. Answers "does Delaware pay for a home EV charger".
- `de_dmv_crash_stats(group_by?, year?, county?, alcohol_involved?, …, limit?)` — reported
  traffic crashes by year, county, weather, light, road surface, impact or day of week.

## Auth

Keyless.

## `Electric+Gas` means plug-in hybrid

Delaware's fuel-type snapshot uses two labels a reader will misread:

| Published label | What it actually is |
|---|---|
| `Electric` | battery-electric vehicle (BEV) |
| `Electric+Gas` | **plug-in hybrid** — a grid-charged battery plus a petrol engine |

`Electric+Gas` is not flex-fuel and not a conventional hybrid. It is also the *larger* of the
two categories (42,287 vs 17,075), so treating it as anything else moves Delaware's EV numbers
by a factor of three. `de_dmv_ev_adoption` reports both separately and sums them into
`plugin_vehicles`.

Verified live 2026-07-29 (snapshot refreshed 2026-07-01): Gas 798,738 · Other (Or None) 88,899
· Electric+Gas 42,287 · Diesel 36,217 · Electric 17,075 · Propane 627 · Comp. Nat. Gas 68 ·
Liquefied Gas 54 · Convertible 16 · Ethanol 1. Statewide total **983,982**; plug-in share 6.0%.

## Grain

The fuel snapshot is **statewide** — no county or ZIP breakdown exists in it, and the returned
`total_vehicles` genuinely is the whole Delaware fleet. The rebate and crash files *do* carry
county, city and ZIP, so those tools group by them.

## Hand-typed values in the rebate files

Both rebate files were keyed by hand and the pack folds the variants together, because a raw
group-by splits one county across four spellings:

- county: `New Castle` / `new Castle` / `new castle` / `New Caslte`, plus the *city* `Newark`
  and `Rehoboth Beach` sitting in the county column.
- vehicle type: `Electric` / `electric` / `BEV`; `Plug-in Hybrid` / `plug in hybrid`.
- charger brand: `Juicebox` / `JuiceBox` / `Juice Box`.
- a few purchase dates are transcription errors — one reads **1953** — so filter by
  `purchase_year` rather than trusting min/max of the date column.
- two charger-rebate rows carry a corrupted award year of **2081**; real years run 2015 onward.

Charger rebates range from **$18.66** (a home cord) to **$48,816** (a multi-port workplace or
public installation) in the same file, so an average rebate sits far above what a household
receives. The tool reports awards, total dollars, average rebate and average station cost
together for exactly that reason.

## Data sources

- `https://data.delaware.gov/resource/ity3-3688.json` — Registered Vehicles by Fuel Type
  (10 rows, statewide, refreshed monthly; 2026-07-01 at time of writing).
- `https://data.delaware.gov/resource/8z8z-di7f.json` — State Rebates for Alternative Fuel
  Vehicles: 7,758 awards, ~$17.15M paid, 2015 onward.
- `https://data.delaware.gov/resource/a9zd-p6sk.json` — Electric Vehicle Charging Equipment
  Rebates: 778 awards, ~$2.81M paid.
- `https://data.delaware.gov/resource/827n-m6xc.json` — Public Crash Data: ~37,000 reported
  crashes a year, crash years 2009 through 2025, three counties.

**Rejected while building:** `f3pu-7vjx` ("Alternative Vehicle Rebates, by Year, 2014 to
Present") reports the same 7,758-row count as `8z8z-di7f` but publishes **no columns** — every
row comes back as `{}` and its metadata column list is empty. It is an unusable duplicate of
the rebate file, so no tool wraps it.

## Quick Start

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

```json
{
  "mcpServers": {
    "de-dmv": {
      "url": "https://gateway.pipeworx.io/de-dmv/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/de-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:

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

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

## 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 De Dmv data" })
```

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

## More

- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)

## License

MIT