# Dc Dmv (npm · @pipeworx/mcp-dc-dmv)

District of Columbia DMV MCP — DMV service centers, the record-level vehicle-inspection file, and…

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-dc-dmv/dc-dmv-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-dc-dmv/dc-dmv-mcp)
- npm · `@pipeworx/mcp-dc-dmv`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-dc-dmv/pipeworx-mcp-dc-dmv.md), [page](https://verifymcp.io/servers/pipeworx-io-dc-dmv/pipeworx-mcp-dc-dmv)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-dc-dmv`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-dc-dmv).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 947 tokens (~315/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Dc Dmv MCP server?

Dc Dmv runs locally as an npm package, launched with npx -y @pipeworx/mcp-dc-dmv. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-dc-dmv -- npx -y @pipeworx/mcp-dc-dmv
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-dc-dmv": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-dc-dmv"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-dc-dmv": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-dc-dmv"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-dc-dmv -- npx -y @pipeworx/mcp-dc-dmv
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-dc-dmv": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-dc-dmv"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-dc-dmv --command npx --arg -y --arg @pipeworx/mcp-dc-dmv
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-dc-dmv:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-dc-dmv"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-dc-dmv": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-dc-dmv"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-dc-dmv -t stdio -c npx -a -y @pipeworx/mcp-dc-dmv
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-dc-dmv": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-dc-dmv"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 80, +1)

- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-30 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (3)

### `dc_dmv_offices` (~211 tokens)

Find a Washington DC DMV location — the District of Columbia Department of Motor Vehicles service centers where residents renew a license, register a vehicle or get a REAL ID, plus the Half Street inspection station, the two self-service emissions-inspection kiosks, the Deanwood road-test and CDL center, and Adjudication Services for ticket hearings. Returns street address, coordinates and the DMV website. Answers "DC DMV near Georgetown", "where is the DC vehicle inspection station", "DC DMV road test location", and "how many DMV service centers does Washington DC have". Covers all 9 published DMV locations.

Input parameters:

- `limit` (number|string): Max locations to return (default 25, max 50).
- `name` (string): Location-name substring, e.g. "Georgetown", "Benning", "Inspection", "Adjudication".
- `office_type` (string): Category substring: "service center", "inspection station", "kiosk", "road test", "adjudication".

### `dc_dmv_vehicle_inspections` (~365 tokens)

Look up Washington DC vehicle safety and emissions inspections by VIN, or count DC inspection volume over time. The District of Columbia DMV publishes 766,879 individual inspection records, each carrying the submitted VIN, the date the vehicle was inspected and the date that inspection expires, covering November 2020 to June 2026 and still being appended. Answers "when was VIN 1FMCU9BZ5NUA87486 last inspected in DC", "when does this car's DC inspection expire", "how many vehicles did DC inspect last month", and "DC inspection volume by month". A VIN prefix matches every vehicle of the same make, model and plant, so vin_prefix="1FMCU9BZ" counts one model line.

Input parameters:

- `expires_before` (string): Keep inspections expiring before this date, YYYY-MM-DD — the way to find vehicles due for re-inspection.
- `group_by` (string): none (default) returns individual inspection records; month or year returns inspection counts per period.
- `inspected_before` (string): Latest inspection date, YYYY-MM-DD, e.g. "2026-07-01".
- `inspected_since` (string): Earliest inspection date, YYYY-MM-DD, e.g. "2026-01-01".
- `limit` (number|string): Max records or periods to return (default 25, max 200).
- `vin` (string): Full 17-character VIN, e.g. "W1KAF4GB5SR257239". Case-insensitive.
- `vin_prefix` (string): Leading characters of a VIN, e.g. "1FMCU9BZ" — the first 8 identify make, model line and body, so this counts one model.

### `dc_dmv_convictions` (~316 tokens)

Count Washington DC traffic convictions by violation and court disposition, from the District of Columbia DMV conviction file — 330,728 citation records running from 2002 to 2026, each with the violation text (speeding, failure to use a seat belt, driving under the influence, no DC permit), the court disposition, and whether points were assessed. Answers "most common traffic violations in DC", "how many DUI convictions did DC record last year", "DC seat belt ticket convictions", and "what happens to DC speeding tickets in court". Group by violation or disposition, and narrow with a citation date range.

Input parameters:

- `before` (string): Latest citation date, YYYY-MM-DD, e.g. "2026-01-01".
- `code` (string): DC violation code, e.g. "T001", "T005".
- `disposition` (string): Court-disposition substring, e.g. "GUILTY", "LIABLE", "SUPERIOR".
- `group_by` (string): violation (default) counts convictions per violation; disposition counts them per court outcome; none returns individual citation records.
- `limit` (number|string): Max rows to return (default 25, max 200).
- `since` (string): Earliest citation date, YYYY-MM-DD, e.g. "2025-01-01".
- `violation` (string): Violation-text substring, e.g. "SPEED", "SEAT BELT", "INFLUENCE", "INSURANCE".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-dc-dmv/pipeworx-mcp-dc-dmv#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78

## Common questions

### What is the Dc Dmv MCP server?

Dc Dmv is an MCP server listed in the public MCP registry as io.github.pipeworx-io/dc-dmv. District of Columbia DMV MCP, DMV service centers, the record-level vehicle-inspection file, and… This page covers its npm package (@pipeworx/mcp-dc-dmv).

### Is the Dc Dmv MCP server safe to use?

Dc Dmv scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Dc Dmv MCP server expose?

Dc Dmv exposes 3 tools: dc_dmv_offices, dc_dmv_vehicle_inspections, dc_dmv_convictions. Their descriptions and schemas cost roughly 892 tokens of context every time the server is loaded.

### Is the Dc Dmv MCP server still maintained?

Dc Dmv is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Dc Dmv MCP server under?

Dc Dmv declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Dc Dmv MCP server?

VerifyMCP ran 16 checks on Dc Dmv, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-dc-dmv
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-dc-dmv
- Repository: https://github.com/pipeworx-io/mcp-dc-dmv
- Website: https://pipeworx.io/packs/dc-dmv
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-dc-dmv/pipeworx-mcp-dc-dmv.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-dc-dmv/pipeworx-mcp-dc-dmv/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-dc-dmv/pipeworx-mcp-dc-dmv.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-dc-dmv/pipeworx-mcp-dc-dmv