Or Dmv
NPM · @PIPEWORX/MCP-OR-DMV · 2 COMPONENTS
Oregon DMV MCP — live wait times at all 60 Oregon DMV field offices, plus the office locator the…
Available components
Last scanned (5 hours ago)
Scores higher than 68% 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-or-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 605 tokens (~302/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
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 0
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 +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.
- 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.
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-or-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-or-dmv |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-or-dmv/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685184726 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:641e132c5d828858e52ccafc1ba51f75605126c4e0ca56f80f1015c3fb0df508decc3161ca9f3672446f0ded63a6c69f65e88e711f814b41e5d212f91 |
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 →
or_dmv_offices ~253
Find Oregon DMV field offices with street address, city, ZIP, phone number, latitude and longitude, and the ODOT region each belongs to. Covers all 60 DMV offices in Oregon, so it answers "DMV office in Eugene", "address and phone for the Bend DMV", "Oregon DMV offices near the coast", or "which DMV offices are in the Portland area". Each office also carries whether it is appointment-only and a link to its ODOT page. For the live queue length at these same offices use or_dmv_wait_times.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name, matched as a substring, e.g. "Portland", "Salem". |
| limit | number|string | – | Max offices to return (default 60, max 100). |
| office | string | – | Case-insensitive office-name substring, e.g. "Gresham", "Albany". |
| region | string | – | ODOT region substring. One of Central Oregon, Eastern Oregon, Portland Area, Southern Oregon, The Coast, Willamette Valley. |
| zip | string | – | Five-digit ZIP code, e.g. "97321". A prefix such as "973" also matches. |
No output schema declared.
No examples provided.
or_dmv_wait_times ~298
Live wait times at Oregon DMV field offices, published by ODOT DMV itself: the current average minutes until served and how many customers are queued at each of the 60 offices statewide. Answers "how long is the wait at the Portland DMV", "which Oregon DMV office is fastest right now", "is the Salem DMV busy", or "shortest DMV line near Eugene". Oregon is one of only two states whose DMV publishes a live queue feed. Offices report only during business hours; outside them each comes back as not_reporting with a null wait, which is the agency switching the feed off rather than an office with no line.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name, matched as a substring, e.g. "Eugene", "Medford". |
| limit | number|string | – | Max offices to return (default 60, max 100). |
| office | string | – | Case-insensitive office-name substring, e.g. "Portland", "Beaverton", "Bend". |
| open_only | boolean|string | – | When true, keep only offices currently reporting a live wait. |
| region | string | – | ODOT region substring. One of Central Oregon, Eastern Oregon, Portland Area, Southern Oregon, The Coast, Willamette Valley. |
| sort | string | – | "wait" ranks shortest reported wait first (reporting offices first); "name" (default) keeps the agency's own order. |
No output schema declared.
No examples provided.
How do I install the Or Dmv MCP server?
Or Dmv runs locally as an npm package, launched with npx -y @pipeworx/mcp-or-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-or-dmv
claude mcp add pipeworx-io-or-dmv -- npx -y @pipeworx/mcp-or-dmv
What is the Or Dmv MCP server?
Or Dmv is an MCP server listed in the public MCP registry as io.github.pipeworx-io/or-dmv. Oregon DMV MCP, live wait times at all 60 Oregon DMV field offices, plus the office locator the… This page covers its npm package (@pipeworx/mcp-or-dmv).
Is the Or Dmv MCP server safe to use?
Or 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 Or Dmv MCP server expose?
Or Dmv exposes 2 tools: or_dmv_wait_times, or_dmv_offices. Their descriptions and schemas cost roughly 551 tokens of context every time the server is loaded.
Is the Or Dmv MCP server still maintained?
Or 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 Or Dmv MCP server under?
Or 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.