{
  "markdown": "# @pipeworx/ct-dmv\n\nConnecticut DMV MCP — electric-vehicle registrations at vehicle level, aggregated on demand by\ntown, make, model, model year or body type.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n- `ct_dmv_ev_registrations(group_by?, city?, make?, model?, model_year?, vehicle_type?, limit?)`\n  — counts of registered electric vehicles. Answers \"how many EVs are registered in\n  Connecticut\", \"how many Teslas are registered in Connecticut\", \"which Connecticut town has\n  the most EVs\", \"most popular EV models in Connecticut\".\n\n`group_by` accepts `city` (default), `make`, `model`, `model_year`, `vehicle_type`, `body`,\n`fuel`, `color`, `plate_type`, `usage`, `category`.\n\n## Auth\n\nKeyless.\n\n## Vintage — read this before quoting a number\n\nThe file is a **snapshot taken 2025-02-28**. Connecticut has not refreshed it since, so it\ncovers the electric vehicles registered as of February 2025 and a count read as \"today\" is\nwrong by more than a year. `as_of` carries the refresh date, `covers` states the period in\nwords, and a `note` repeats it on every response.\n\n## Grain\n\nOne row per registered vehicle — 60,489 of them, each with plate type, owner town, weight,\ncolour, model year and expiry. The pack never returns those individual records; it aggregates\nserver-side with `$select=<col>,count(1)&$group=<col>` and returns counts.\n\n`sum_of_returned_rows` is the sum of the rows actually returned, and `truncated` says whether\n`limit` cut the list off. There are ~170 Connecticut towns and hundreds of models, so a default\ncall is usually truncated — which is why no field claims to be a statewide EV total.\n\nVerified live 2026-07-29, `group_by=\"make\"`: Tesla 21,405 · Toyota 5,759 · Jeep 5,302 ·\nChevrolet 2,982 · KIA 2,916. Total rows in the file: 60,489.\n\n## Data sources\n\n- `https://data.ct.gov/resource/y7ky-5wcz.json` — CT DMV \"Electric Vehicle Registration Data\".\n- `https://data.ct.gov/api/views/y7ky-5wcz.json` — `rowsUpdatedAt`, used for `as_of`.\n\nColumn names are lowercase and unseparated: `primarycustomercity`, `vehiclemake`,\n`vehiclemodel`, `vehicleyear`, `vehicletype`, `vehiclebody`, `fuelcode`, `platetype`,\n`registrationusage`. Town names are stored upper-case (`WEST HARTFORD`) while makes are mixed\ncase (`Tesla`, `KIA`), so both are matched with `upper(col) like`.\n\n**Rejected while building:** `apne-w8c6`, published as \"Licensed Automobile Dealers And\nRepairers\", sounds like a dealer locator but holds **138 manufacturer licences**, mostly held\nby out-of-state RV and trailer makers — 23 in Indiana, 18 in California, 2 in Connecticut, and\nevery row is `MANUFACTURER LICENSE`. It cannot answer \"find a licensed dealer or repairer near\nme\", so no tool wraps it. Do not re-probe it expecting a dealer list.\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"ct-dmv\": {\n      \"url\": \"https://gateway.pipeworx.io/ct-dmv/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/ct-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 Ct 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": 4839,
  "sha": "24e77e25f7b57a432f11c12c8ba53af113a13abfa4fc260d299fdc09b1afb79b",
  "repo_slug": "pipeworx-io/mcp-ct-dmv",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_ct_dmv_311aaa5f/readme"
}