{
  "markdown": "# @pipeworx/dc-dmv\n\nDistrict of Columbia DMV data: service centers, the record-level **vehicle inspection** file,\nand **traffic convictions**. Keyless.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Why DC gets its own pack\n\nDC's grain is unlike any state's. The District publishes **766,879 individual vehicle\ninspections** keyed by VIN and **330,728 individual traffic convictions** keyed by citation,\nboth as ArcGIS tables on the DCGIS server — not the county-level aggregates most states\npublish. So the tools take VINs, violation text and date ranges rather than a county argument.\n\n## Tools\n\n| Tool | What it returns |\n|---|---|\n| `dc_dmv_offices` | All 9 DMV locations — service centers, the inspection station, two self-service emissions kiosks, the Deanwood road-test/CDL center, and Adjudication Services |\n| `dc_dmv_vehicle_inspections` | Inspection records by VIN or VIN prefix, with inspection and expiration dates; or inspection volume per month/year |\n| `dc_dmv_convictions` | Traffic convictions counted by violation or court disposition, or individual citation records |\n\n## Auth\n\nNone. Every upstream is a public DCGIS ArcGIS MapServer layer.\n\n## The State Plane coordinate trap\n\n**The office layer's `XCOORD`/`YCOORD` columns are Maryland State Plane metres, not lat/lng.**\nGeorgetown Service Center reads `394380.55, 137456.23` — plausible-looking numbers that are\nwrong by the width of a hemisphere if treated as coordinates.\n\nEvery query here passes `geometry: true` to `arcgisQuery` (which sets `outSR=4326`) and reads\nlatitude and longitude off the **returned geometry**. `XCOORD`/`YCOORD` are deliberately left\nout of the response so they cannot be mistaken for coordinates downstream. Georgetown's real\nposition is `38.9050, -77.0648`.\n\n## Gotchas worth knowing\n\nThese are live-verified behaviours, not guesses:\n\n- **The inspection file's `STATUS` column is empty on all 766,879 rows**, so a pass/fail\n  outcome is *not* published. What you get is that an inspection happened, when, and when the\n  resulting certificate expires — an expiration roughly two years out is the usual sign of a\n  pass, a short one of a re-inspection window. The tool's `note` says so rather than letting a\n  caller read a null as \"unknown result\". For per-test pass/fail with make and model,\n  `nj_mvc_vehicle_inspections` publishes it.\n- **`GIS_ID`, `CREATOR` and `CREATED` are also empty** on the inspection table.\n- **About half the conviction rows prefix the violation text with a four-digit internal code** —\n  `0201SPEED IN EXCESS OF LIMIT` and `SPEED IN EXCESS OF LIMIT` are the same offence in two\n  buckets. A raw group-by therefore splits and mis-ranks every violation. The tool strips the\n  prefix and merges: \"DISOBEYING OFFICIAL SIGN OR SIGNAL DEVICE\" is 20,113 convictions, not the\n  10,369 a naive query reports.\n- **DCGIS caps any single response at 2,000 rows**, grouped statistics included. Month and year\n  rollups group by day upstream (1,874 distinct days across the whole file — inside the cap) and\n  aggregate in code; if that ever hits the cap the response flags `truncated` and says to narrow\n  with `inspected_since`.\n- **Coverage:** inspections run 2020-11-01 → 2026-06-30 and are still being appended;\n  convictions run 2002-07-01 → 2026-06-27. Both are returned in a `coverage` field rather than\n  assumed.\n- **Convictions are convictions.** A citation that was dismissed or never adjudicated is absent,\n  so these counts are not ticket counts.\n- **The office layer carries no ZIP and no hours.** `MATCHADDR` is the District's own geocoded\n  street address; dmv.dc.gov posts hours per location.\n\n## Available but not wrapped\n\nThe same `Transportation_DMV` MapServer carries further DMV tables that are queryable but not\nexposed as tools:\n\n| Layer | Table |\n|---|---|\n| 142 | DMV Business Information |\n| 143 | DMV Driver License Information |\n| 144 | DMV ID Card Information |\n| 145 | DMV Reciprocity Parking Permit |\n| 146 | DMV Personalized Plates |\n| 147 | DMV Disability Placard |\n| 149 | DMV Vehicle Inspections FY2003-2013 |\n| 150 | DMV Vehicle Inspections FY2014-2020 |\n| 166 | DMV Boot and Tow |\n\nLayers 149 and 150 are the historical inspection archives and share the current table's schema,\nincluding the same empty `STATUS`.\n\n## Data sources\n\n- [DCGIS Public_Service layer 4](https://maps2.dcgis.dc.gov/dcgis/rest/services/DCGIS_DATA/Public_Service_WebMercator/MapServer/4) — District agency locations, filtered to the 9 DMV rows\n- [DCGIS Transportation_DMV layer 1](https://maps2.dcgis.dc.gov/dcgis/rest/services/DCGIS_DATA/Transportation_DMV_WebMercator/MapServer/1) — DMV Vehicle Inspections\n- [DCGIS Transportation_DMV layer 151](https://maps2.dcgis.dc.gov/dcgis/rest/services/DCGIS_DATA/Transportation_DMV_WebMercator/MapServer/151) — DMV Convictions\n- Dataset discovery: [opendata.dc.gov](https://opendata.dc.gov/)\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"dc-dmv\": {\n      \"url\": \"https://gateway.pipeworx.io/dc-dmv/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/dc-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 Dc 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": 6954,
  "sha": "86d5dacc3153bed7bb0bac0995e9ad21108b5e086181f3ca51e6b3a5cab6a148",
  "repo_slug": "pipeworx-io/mcp-dc-dmv",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_dc_dmv_37857451/readme"
}