Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Md Dmv

NPM · @PIPEWORX/MCP-MD-DMV · 2 COMPONENTS

Maryland DMV MCP — monthly registered-vehicle counts and electric/plug-in hybrid adoption by…

+3 this week 81 Trust /100

Last scanned (11 hours ago)

Scores higher than 68% of npm servers

Category Data and Analytics

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

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

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 1 Nov 26 +1

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

  • 30 Oct 26 +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.

  • 29 Oct 26 78

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-md-dmv@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-md-dmv
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-md-dmv/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3655318119
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:72cfff08b8245b4dc0e3b387e18899c0d851a7fea8370ead01c80c5710a82ba79552a8b23c6247d7e616423110f67acb14d856dd8605bbacfa892c9ab

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~589 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
md_dmv_ev_adoption ~337

Measure electric-vehicle adoption in Maryland from Maryland MVA registration counts: how many battery-electric and plug-in hybrid vehicles are registered in a county or a ZIP code each month, split by fuel category, with a statewide Maryland total for context. Answers "how many EVs are registered in Montgomery County Maryland", "EV registrations in ZIP 20852", "which Maryland county has the most electric vehicles", "which Maryland ZIP codes have the most EVs", and EV growth over time via the `month` argument (monthly since 2020). Pass `zip` or group_by="zip" for the ZIP-level file, otherwise results come back by county. For Maryland's whole registered fleet across every fuel type use md_dmv_vehicle_registrations.

NameTypeReqDescription
countystring–Maryland county or Baltimore City, e.g. "Montgomery", "Prince George's". Apostrophes are optional. Results are flagged in_maryland because this file also carries out-of-state counties of residence.
group_bystring–Breakdown dimension: "county" (default) or "zip". Passing `zip` implies group_by="zip".
limitnumber|string–Max counties or ZIP codes to return (default 30, max 500).
monthstring–Month as YYYY/MM, e.g. "2026/06". Defaults to the most recent month Maryland has published. The series starts at 2020/07.
zipstring–Five-digit ZIP code, e.g. "20852". Supplying this reads the ZIP-level file instead of the county file.

No output schema declared.

No examples provided.

md_dmv_vehicle_registrations ~252

Count vehicles registered in Maryland by county for a given month, from Maryland Motor Vehicle Administration (MVA) data published monthly since 2020. Returns each county's registered-vehicle count plus the genuine statewide total for that month and each county's share of it, so it answers "how many vehicles are registered in Montgomery County Maryland", "which Maryland county has the most registered vehicles", "how many cars are registered in Maryland", and month-over-month trend questions via the `month` argument. Counts the whole registered fleet of every fuel type; for the electric and plug-in hybrid slice of it use md_dmv_ev_adoption.

NameTypeReqDescription
countystring–Maryland county or Baltimore City, e.g. "Montgomery", "Prince George's", "Baltimore City". Apostrophes and periods are optional.
limitnumber|string–Max counties to return (default 30, max 200). Maryland publishes 25 rows per month, so the default returns them all.
monthstring–Month as YYYY/MM, e.g. "2026/06". Defaults to the most recent month Maryland has published. The series starts at 2020/07.

No output schema declared.

No examples provided.

Install

How do I install the Md Dmv MCP server?

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

npm · @pipeworx/mcp-md-dmv

# add to Claude Code
claude mcp add pipeworx-io-md-dmv -- npx -y @pipeworx/mcp-md-dmv
Common questions

What is the Md Dmv MCP server?

Md Dmv is an MCP server listed in the public MCP registry as io.github.pipeworx-io/md-dmv. Maryland DMV MCP, monthly registered-vehicle counts and electric/plug-in hybrid adoption by… This page covers its npm package (@pipeworx/mcp-md-dmv).

Is the Md Dmv MCP server safe to use?

Md 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 Md Dmv MCP server expose?

Md Dmv exposes 2 tools: md_dmv_vehicle_registrations, md_dmv_ev_adoption. Their descriptions and schemas cost roughly 589 tokens of context every time the server is loaded.

Is the Md Dmv MCP server still maintained?

Md 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 Md Dmv MCP server under?

Md 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.