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.

Tn Dmv

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

Tennessee DMV MCP — Department of Safety and Homeland Security: the 186 driver service centers…

0 this week 77 Trust /100

Last scanned (11 hours ago)

Scores higher than 55% of npm servers

Category Maps and Location

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-tn-dmv). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability55
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 831 tokens (~415/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 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 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

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.

What we tested

Checks we ran (14)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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 0
    • Security disclosure: fail → unverified ▼ functional
  • 2 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 1 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 77

    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-tn-dmv@0.2.0

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-tn-dmv
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-tn-dmv/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3560491811
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:4d4b165c7773047e02888c0a31e620a7d44d79bc808c52af3c7099dbba1566b6f1c4ed5c7d8c16a5ebd8621b7a66ad03fe056c6763c87d610f14f648d

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 · ~776 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
tn_dmv_driver_service_centers ~376

Find Tennessee driver service centers (Department of Safety and Homeland Security) with street address, county, hours, phone, coordinates, and exactly which services each of the 186 locations performs. Tennessee publishes a per-location capability matrix, so this answers questions a plain address list cannot: "which Tennessee driver service center issues a REAL ID", "where can I take the CDL skills test in Tennessee", "which Tennessee location does handgun permits", "where do I get a vision test near Knoxville", or "is there a driver services kiosk in Memphis". Locations split into full service centers, self-service kiosks, county clerk partners and express counters. Filter by city, county, ZIP, name or required service; call with no arguments for all 186.

NameTypeReqDescription
citystring–City name, e.g. "Nashville", "Oak Ridge". Matched loosely, so spacing does not matter.
countystring–Tennessee county name, matched as a substring, e.g. "Davidson", "Shelby".
limitnumber|string–Max locations to return (default 50, max 200).
namestring–Location-name substring, e.g. "Oak Ridge", "Express".
servicestring–Require a service, matched as a substring. Published services: REAL ID, new application, photo ID, handgun permit, vision test, road or motorcycle test, knowledge test, CDL skills test, renewal, name…
zipstring–Five-digit Tennessee ZIP code, or a prefix, e.g. "37830".

No output schema declared.

No examples provided.

tn_dmv_impaired_driving_crashes ~400

Count Tennessee injury and fatal traffic crashes involving alcohol or drugs, from the Department of Safety and Homeland Security crash file for calendar year 2022. Each record is one person involved in an impaired-driving crash, carrying crash severity (fatal, suspected serious injury, suspected minor injury), the driver age group and gender, the investigating law-enforcement agency, date, time and coordinates. Answers "how many fatal DUI crashes in Tennessee", "which age group is involved in the most alcohol-related crashes in Tennessee", "drug-involved crashes by police agency", or "impaired driving crashes by month". Group results by age_group, gender, severity, agency, substance or month, and get a sample of the underlying records with latitude and longitude for mapping.

NameTypeReqDescription
age_groupstring–Age band substring as published, e.g. "21 to 24", "80 & Up", "16 to 17".
agencystring–Investigating agency substring. State troopers are published as "THP District 3 - Nashville" and similar, so "THP" selects all of them; city forces read "METROPOLITAN NASHVILLE POLICE DEPT", "MEMPHIS…
genderstring–Published as "M" or "F"; "male"/"female" are accepted.
group_bystring–Breakdown dimension: age_group, gender, severity, agency, substance, month. Defaults to age_group.
limitnumber|string–Max sample records returned alongside the counts (default 10, max 200).
severitystring–Crash severity substring: "fatal", "serious injury", "minor injury".
substancestring–"alcohol", "drugs", "both" (alcohol and drugs together), or "either" (default — any impairment).

No output schema declared.

No examples provided.

Install

How do I install the Tn Dmv MCP server?

Tn Dmv runs locally as an npm package, launched with npx -y @pipeworx/mcp-tn-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-tn-dmv

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

What is the Tn Dmv MCP server?

Tn Dmv is an MCP server listed in the public MCP registry as io.github.pipeworx-io/tn-dmv. Tennessee DMV MCP, Department of Safety and Homeland Security: the 186 driver service centers… This page covers its npm package (@pipeworx/mcp-tn-dmv).

Is the Tn Dmv MCP server safe to use?

Tn Dmv scores 77 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 Tn Dmv MCP server expose?

Tn Dmv exposes 2 tools: tn_dmv_driver_service_centers, tn_dmv_impaired_driving_crashes. Their descriptions and schemas cost roughly 776 tokens of context every time the server is loaded.

Is the Tn Dmv MCP server still maintained?

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

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

VerifyMCP ran 14 checks on Tn Dmv, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Tn Dmv: Security disclosure and Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.