Dc Dmv MCP server

@pipeworx/dc-dmv

District of Columbia DMV data: service centers, the record-level vehicle inspection file, and traffic convictions. Keyless.

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Why DC gets its own pack

DC's grain is unlike any state's. The District publishes 766,879 individual vehicle inspections keyed by VIN and 330,728 individual traffic convictions keyed by citation, both as ArcGIS tables on the DCGIS server — not the county-level aggregates most states publish. So the tools take VINs, violation text and date ranges rather than a county argument.

Tools

Auth

None. Every upstream is a public DCGIS ArcGIS MapServer layer.

The State Plane coordinate trap

The office layer's XCOORD/YCOORD columns are Maryland State Plane metres, not lat/lng. Georgetown Service Center reads 394380.55, 137456.23 — plausible-looking numbers that are wrong by the width of a hemisphere if treated as coordinates.

Every query here passes geometry: true to arcgisQuery (which sets outSR=4326) and reads latitude and longitude off the returned geometry. XCOORD/YCOORD are deliberately left out of the response so they cannot be mistaken for coordinates downstream. Georgetown's real position is 38.9050, -77.0648.

Gotchas worth knowing

These are live-verified behaviours, not guesses:

outcome is not published. What you get is that an inspection happened, when, and when the resulting certificate expires — an expiration roughly two years out is the usual sign of a pass, a short one of a re-inspection window. The tool's note says so rather than letting a caller read a null as "unknown result". For per-test pass/fail with make and model, njmvcvehicle_inspections publishes it.

• The inspection file's STATUS column is empty on all 766,879 rows, so a pass/fail

0201SPEED IN EXCESS OF LIMIT and SPEED IN EXCESS OF LIMIT are the same offence in two buckets. A raw group-by therefore splits and mis-ranks every violation. The tool strips the prefix and merges: "DISOBEYING OFFICIAL SIGN OR SIGNAL DEVICE" is 20,113 convictions, not the 10,369 a naive query reports.

• GISID, CREATOR and CREATED are also empty** on the inspection table.
• About half the conviction rows prefix the violation text with a four-digit internal code —

rollups group by day upstream (1,874 distinct days across the whole file — inside the cap) and aggregate in code; if that ever hits the cap the response flags truncated and says to narrow with inspected_since.

• DCGIS caps any single response at 2,000 rows, grouped statistics included. Month and year

convictions run 2002-07-01 → 2026-06-27. Both are returned in a coverage field rather than assumed.

• Coverage: inspections run 2020-11-01 → 2026-06-30 and are still being appended;

so these counts are not ticket counts.

• Convictions are convictions. A citation that was dismissed or never adjudicated is absent,

street address; dmv.dc.gov posts hours per location.

• The office layer carries no ZIP and no hours. MATCHADDR is the District's own geocoded

Available but not wrapped

The same Transportation_DMV MapServer carries further DMV tables that are queryable but not exposed as tools:

Shortened. The full README is on GitHub.