Server data from the Official MCP Registry
Washington DC DMV: service centers, vehicle inspections by VIN, traffic convictions
Washington DC DMV: service centers, vehicle inspections by VIN, traffic convictions
Remote endpoints: streamable-http: https://gateway.pipeworx.io/dc-dmv/mcp
Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: trusted author (1273/1286 approved). 1 finding(s) downgraded by scanner intelligence.
34 tools verified · Open access · 2 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-pipeworx-io-dc-dmv": {
"url": "https://gateway.pipeworx.io/dc-dmv/mcp"
}
}
}From the project's GitHub README.
District of Columbia DMV data: service centers, the record-level vehicle inspection file, and traffic convictions. Keyless.
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.
| Tool | What it returns |
|---|---|
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 |
dc_dmv_vehicle_inspections | Inspection records by VIN or VIN prefix, with inspection and expiration dates; or inspection volume per month/year |
dc_dmv_convictions | Traffic convictions counted by violation or court disposition, or individual citation records |
None. Every upstream is a public DCGIS ArcGIS MapServer layer.
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.
These are live-verified behaviours, not guesses:
STATUS column is empty on all 766,879 rows, so a pass/fail
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,
nj_mvc_vehicle_inspections publishes it.GIS_ID, CREATOR and CREATED are also empty on the inspection table.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.truncated and says to narrow
with inspected_since.coverage field rather than
assumed.MATCHADDR is the District's own geocoded
street address; dmv.dc.gov posts hours per location.The same Transportation_DMV MapServer carries further DMV tables that are queryable but not
exposed as tools:
| Layer | Table |
|---|---|
| 142 | DMV Business Information |
| 143 | DMV Driver License Information |
| 144 | DMV ID Card Information |
| 145 | DMV Reciprocity Parking Permit |
| 146 | DMV Personalized Plates |
| 147 | DMV Disability Placard |
| 149 | DMV Vehicle Inspections FY2003-2013 |
| 150 | DMV Vehicle Inspections FY2014-2020 |
| 166 | DMV Boot and Tow |
Layers 149 and 150 are the historical inspection archives and share the current table's schema,
including the same empty STATUS.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"dc-dmv": {
"url": "https://gateway.pipeworx.io/dc-dmv/mcp"
}
}
}
Or connect to the full Pipeworx gateway for access to all 1392+ data sources:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Instead of calling tools directly, you can ask questions in plain English:
ask_pipeworx({ question: "your question about District of Columbia DMV data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.