{
  "markdown": "# @pipeworx/tn-dmv\n\nTennessee Department of Safety and Homeland Security: the 186 driver service centers with their\nper-location service capabilities, plus the state's impaired-driving crash file. Keyless.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Why Tennessee gets its own pack\n\nThis came out of splitting a single multiplexed `us-dmv` tool into one pack per state agency.\nTennessee's grain is a **per-counter capability matrix** — REAL ID, CDL skills test, handgun\npermit, vision test — published on the department's own ArcGIS, which has nothing in common\nwith California's ZIP-level registration snapshot. A union schema across states leaves most\narguments ignored on every call, so Tennessee's arguments are Tennessee's.\n\n## Tools\n\n| Tool | What it returns |\n|---|---|\n| `tn_dmv_driver_service_centers` | Address, county, hours, phone, coordinates and the 21 service capabilities each location publishes |\n| `tn_dmv_impaired_driving_crashes` | Alcohol- and drug-involved injury and fatal crashes for 2022, grouped by age, gender, severity, agency, substance or month, with a mappable sample |\n\n`tn_dmv_driver_service_centers` filters: `city`, `county`, `zip` (prefix), `name`, `service`, `limit`.\n`tn_dmv_impaired_driving_crashes` filters: `substance`, `severity`, `age_group`, `gender`,\n`agency`, `group_by`, `limit`.\n\n## The distinctive fields\n\nREAL ID, **CDL skills test** (only 4 of 186 locations do it), **handgun permit** (47 locations)\nand **vision test** are the filters worth knowing about — they are the questions a plain address\nlist cannot answer. `office_type` separates the 44 full-service centers from 93 self-service\nkiosks, 46 county-clerk partners and 3 express counters, which matters because a kiosk performs\nonly a handful of the listed services.\n\n## Auth\n\nNone. `tnmap.tn.gov` is a public state ArcGIS host.\n\n## Gotchas worth knowing\n\n- **City names run together.** `USER_City` is published as `OakRidge`, `MtJuliet` and similar,\n  so `city` is matched after stripping both sides to letters and digits — a caller typing\n  \"Oak Ridge\" gets the Oak Ridge center rather than a not-found.\n- **`X` is longitude and `Y` is latitude**, both as attribute columns, so no geometry\n  round-trip is needed.\n- **Two HTML blob columns had to be excluded.** `USER_Website_Name` and `USER_Website_Services`\n  are pre-rendered `<br>`-separated markup that duplicates columns already returned and roughly\n  triples the payload; with them included the full-layer fetch failed outright rather than\n  merely running slowly. The query names its fields explicitly to leave them behind.\n- **The crash layer is person-level, and 2022 only.** `SAFETY/DUICrashesArrestsAgeGender`\n  layer 0 holds one row per person involved: ~1,543 person records across ~603 distinct crashes.\n  Both numbers are reported (`person_records`, `distinct_crashes`) because quoting the row count\n  as a crash count would overstate it by 2.5×. It covers injury and fatal crashes; property-damage-only\n  crashes sit outside it. The whole file is calendar year 2022, reported as `as_of`.\n- **State troopers are not called \"Highway Patrol\" in the data.** They appear as\n  `THP District 3 - Nashville` and seven other districts, so `agency: \"THP\"` selects all of\n  them; `agency: \"HIGHWAY PATROL\"` matches nothing.\n- **\"Unknown\" is a real age group**, the agency's own value for records where age was never\n  recorded, and it is the largest bucket (386 of 1,543). It is left in rather than silently\n  dropped.\n- The wider `SAFETY/` ArcGIS folder also carries `DeerCrashes2019to2023` and `I24_CrashHotspots`.\n  Both are cartographic multi-layer map services (severity-split display layers, basemap\n  boundaries, a weighted-likelihood raster) rather than one queryable table, so they are left\n  out; the DUI layer was the one that returned real, aggregatable records.\n\n## Data sources\n\n- [TN SAFETY ArcGIS `DriverServiceCenters/MapServer/0`](https://tnmap.tn.gov/arcgis/rest/services/SAFETY/DriverServiceCenters/MapServer/0)\n- [TN SAFETY ArcGIS `DUICrashesArrestsAgeGender/MapServer/0`](https://tnmap.tn.gov/arcgis/rest/services/SAFETY/DUICrashesArrestsAgeGender/MapServer/0)\n\nBoth verified live 2026-07-30.\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"tn-dmv\": {\n      \"url\": \"https://gateway.pipeworx.io/tn-dmv/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/tn-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 Tn 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": 6274,
  "sha": "14101709d130ecc5ad54ba4edc999ac704841c07cdabe22171b1fb0abb82ef65",
  "repo_slug": "pipeworx-io/mcp-tn-dmv",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_tn_dmv_5da590aa/readme"
}