{
  "markdown": "# @pipeworx/ca-dmv\n\nCalifornia DMV data: registered vehicles and EV adoption by ZIP code, all 187 field offices with\nthe services each performs, the official forms catalog, insurer NAIC codes, and licensed-driver\ncounts by county. Keyless.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Why this is one state per pack\n\nPart of the `dmv` category — one pack per state motor-vehicle agency. The states do not share a\ngrain: California publishes a ZIP × make × model-year × fuel snapshot, New York a record-level\nfile, Washington monthly transaction counts, Maryland county-months, Pennsylvania county-quarters.\nA single cross-state tool meant a schema where most arguments were ignored for most states and a\n\"total\" that was never comparable, so each agency gets its own tools with its own real arguments.\nFor every DMV tool in one connection, use `/mcp?vertical=dmv`.\n\n## Tools\n\n| Tool | What it returns |\n|---|---|\n| `ca_dmv_vehicle_registrations` | Registered vehicle counts by ZIP, make, model year, fuel or duty class |\n| `ca_dmv_ev_adoption` | Battery-electric and plug-in hybrid counts with share of the local fleet |\n| `ca_dmv_offices` | All 187 field offices — address, per-day hours, coordinates, services performed |\n| `ca_dmv_forms` | Official DMV forms by topic, with REG/DL form numbers and download pages |\n| `ca_dmv_insurance_lookup` | Insurer NAIC codes by company name |\n| `ca_dmv_driver_licenses` | Valid licences and ID cards held, by county, annually from 2008 |\n\n## Auth\n\nNone. Every endpoint is public California state infrastructure. The CKAN-backed tools accept an\noptional CKAN API key, which the public datasets do not require.\n\n## Gotchas worth knowing\n\nLive-verified behaviours, not guesses:\n\n- **Snapshots are one CKAN resource per year, 2019–2026**, and the rows carry the *prior*\n  December 31 as their as-of date — the \"2026\" file describes the fleet on 2025-12-31.\n- **Grouping by ZIP surfaces a literal `OOS` bucket** — out-of-state registrants, ~638k vehicles —\n  which outranks every real ZIP. Ignore it when ranking ZIPs; the tool flags it in `note`.\n- **`OTHER/UNK` is a real make value** that absorbs small-count suppression and can outrank\n  genuine makes in a by-make ranking.\n- **`total_vehicles` appears only when it is honest.** Grouping by fuel returns every category, so\n  its sum is the true fleet total; any other grouping can be cut off by `limit`, and those\n  responses carry `sum_of_returned_rows` plus `truncated` instead.\n- **Fuel labels are specific strings** (`Battery Electric`, `Plug-in Hybrid`, `Hybrid Gasoline`,\n  `Diesel and Diesel Hybrid`, `Hydrogen Fuel Cell`). Plain words like \"electric\", \"phev\" or\n  \"hydrogen\" are mapped for you.\n- **Form search uses the DMV site's own relevance ranking**, so a broad phrase like\n  \"title transfer\" can put a vessel-title form above the vehicle one.\n- **California publishes no wait-time feed.** Only North Carolina (`nc-dmv`) and Oregon (`or-dmv`)\n  do; `ca_dmv_offices` returns posted hours instead.\n- **Lien lookup and appointment booking are unavailable**: the lien endpoint requires a reCAPTCHA\n  token and appointments run on a session-based kiosk system.\n\n## Data sources\n\n- [Vehicle Fuel Type Count by Zip Code](https://data.ca.gov/dataset/vehicle-fuel-type-count-by-zip-code) — data.ca.gov CKAN, `datastore_search_sql`\n- [Driver Licenses Outstanding by County](https://data.ca.gov/dataset/driver-licenses-outstanding-by-county) — data.ca.gov CKAN\n- [Field office directory](https://www.dmv.ca.gov/portal/wp-json/wp/v2/dmv_field-office) — dmv.ca.gov WP REST, hours and per-office service tags\n- [Forms catalog](https://www.dmv.ca.gov/portal/wp-json/wp/v2/dmv_forms) — dmv.ca.gov WP REST\n- Insurance carrier NAIC lookup — `https://www.dmv.ca.gov/portal/wp-json/dmv/v1/naic-lookup?s=<name>`\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"ca-dmv\": {\n      \"url\": \"https://gateway.pipeworx.io/ca-dmv/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/ca-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 Ca 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": 5886,
  "sha": "7618d68e3c85bb0a6425086c2f2b7bbfe82c13d71ac787983126f3906f751698",
  "repo_slug": "pipeworx-io/mcp-ca-dmv",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_ca_dmv_9ac66208/readme"
}