Pa Dmv
NPM · @PIPEWORX/MCP-PA-DMV · 2 COMPONENTS
Pennsylvania DMV MCP — registered vehicles and electric-vehicle adoption by county and by ZIP…
Available components
Last scanned (6 hours ago)
Scores higher than 62% of npm servers
Category Maps and Location
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-pa-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 Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 900 tokens (~300/item across 3 items; 3 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 79
First indexed and scored.
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-pa-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-pa-dmv |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-pa-dmv/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685234590 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:fe47ed03b66a64f145aa1d3c4e0952c460c06c85b8fd16eab4873ea7407c8604c31d3137d943f938f38dc429d18d5f1ada07db6b4a3c322de63523083 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
pa_dmv_ev_adoption ~309
Measure electric-vehicle adoption in Pennsylvania from PennDOT Driver & Vehicle Services registration data: how many battery-electric, plug-in hybrid, hydrogen fuel-cell and conventional hybrid vehicles are registered in each Pennsylvania county in a given quarter, and what share of that county's registered fleet is plug-in. Returns a genuine statewide Pennsylvania total alongside every county, so it answers "how many EVs are registered in Pennsylvania", "EV share in Allegheny County", "which Pennsylvania county has the most electric vehicles", "how many Teslas-era battery-electric cars are registered in Philadelphia", and quarter-over-quarter growth via the `year` and `quarter` arguments (2023 onward). For ZIP-code detail use pa_dmv_ev_adoption_by_zip; for the whole registered fleet across every fuel type use pa_dmv_vehicle_registrations.
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | – | Pennsylvania county name, matched as a substring, e.g. "Allegheny", "Montgomery", "Philadelphia". |
| limit | number|string | – | Max counties to return (default 30, max 70). Pennsylvania has 67 counties. |
| quarter | string | – | Quarter of that registration year: "Q1", "Q2", "Q3" or "Q4". Defaults to the latest quarter PennDOT has actually filed for that year. |
| year | string | – | Registration year, one of 2023, 2024, 2025, 2026. Defaults to 2026. |
No output schema declared.
No examples provided.
pa_dmv_ev_adoption_by_zip ~270
Break Pennsylvania electric-vehicle registrations down to the ZIP code, from PennDOT Driver & Vehicle Services: battery-electric, plug-in hybrid, fuel-cell and conventional hybrid counts for each of roughly 1,830 Pennsylvania ZIP codes, with that ZIP code's total registered vehicles and plug-in share. Answers "how many EVs are registered in ZIP 19103", "which Pennsylvania ZIP code has the most electric vehicles", "EV share in ZIP 15213", and neighbourhood-level adoption questions that a county figure averages away. Supply `zip` for one ZIP code, or omit it to rank them. For county figures and the statewide Pennsylvania total use pa_dmv_ev_adoption.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number|string | – | Max ZIP codes to return (default 30, max 500). |
| quarter | string | – | Quarter of that registration year: "Q1", "Q2", "Q3" or "Q4". Defaults to the latest quarter PennDOT has actually filed for that year. |
| year | string | – | Registration year, one of 2023, 2024, 2025, 2026. Defaults to 2026. |
| zip | string | – | Five-digit Pennsylvania ZIP code, e.g. "19103", "15213". |
No output schema declared.
No examples provided.
pa_dmv_vehicle_registrations ~267
Count all vehicles registered in Pennsylvania by county for a given quarter, from PennDOT Driver & Vehicle Services. Covers the entire registered fleet of every fuel type, returns a genuine statewide Pennsylvania total plus each county's share of it, and carries the plug-in count alongside for context. Answers "how many vehicles are registered in Pennsylvania", "how many cars are registered in Allegheny County", "which Pennsylvania county has the most registered vehicles", and quarterly trend questions via the `year` and `quarter` arguments (2023 onward). For the electric and hybrid breakdown by drivetrain use pa_dmv_ev_adoption.
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | – | Pennsylvania county name, matched as a substring, e.g. "Allegheny", "Montgomery", "Philadelphia". |
| limit | number|string | – | Max counties to return (default 30, max 70). Pennsylvania has 67 counties. |
| quarter | string | – | Quarter of that registration year: "Q1", "Q2", "Q3" or "Q4". Defaults to the latest quarter PennDOT has actually filed for that year. |
| year | string | – | Registration year, one of 2023, 2024, 2025, 2026. Defaults to 2026. |
No output schema declared.
No examples provided.
How do I install the Pa Dmv MCP server?
Pa Dmv runs locally as an npm package, launched with npx -y @pipeworx/mcp-pa-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-pa-dmv
claude mcp add pipeworx-io-pa-dmv -- npx -y @pipeworx/mcp-pa-dmv
What is the Pa Dmv MCP server?
Pa Dmv is an MCP server listed in the public MCP registry as io.github.pipeworx-io/pa-dmv. Pennsylvania DMV MCP, registered vehicles and electric-vehicle adoption by county and by ZIP… This page covers its npm package (@pipeworx/mcp-pa-dmv).
Is the Pa Dmv MCP server safe to use?
Pa Dmv scores 79 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 Pa Dmv MCP server expose?
Pa Dmv exposes 3 tools: pa_dmv_ev_adoption, pa_dmv_vehicle_registrations, pa_dmv_ev_adoption_by_zip. Their descriptions and schemas cost roughly 846 tokens of context every time the server is loaded.
Is the Pa Dmv MCP server still maintained?
Pa 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 Pa Dmv MCP server under?
Pa 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.