
Tx Dmv MCP server
online · 100% uptimeTexas DMV MCP — statewide vehicle, pickup and motorcycle registration totals by fiscal year, from…
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Tx Dmv yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Tx Dmv tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Tx Dmv compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 304 ms
- faster than 47% of 30,031 servers
Release history: 3 versions in the registry since 2026-07-30, latest 2026-10-29, typically one every 56 days.
Install Tx Dmv in Claude Code, Cursor or VS Code
claude mcp add --transport http tx-dmv https://gateway.pipeworx.io/tx-dmv/mcp
What the publisher says
From the Tx Dmv repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/tx-dmv
Texas DMV (TxDMV) MCP — statewide vehicle, pickup and motorcycle registration totals by fiscal year, from TxDMV's own published series.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tools
for a fiscal year, split into passenger cars, pickup trucks of one ton or less and motorcycles, each with its share of the fleet. Answers "how many vehicles are registered in Texas", "how many motorcycles are registered in Texas", and growth across years.
- txdmvvehicleregistrations(fiscalyear?, limit?) — total vehicles registered in Texas
Auth
Keyless.
Grain and vintage — read this before quoting a number
Two things about this dataset trip people up, so both are reported on every response:
no county, city or ZIP breakdown in this series, and no make/model/fuel split. Passing county, zip, make, modelyear or fueltype returns { found: false, reason: "grainunavailable" } with a hint rather than silently ignoring the argument. For a ZIP-level fleet breakdown, cadmvvehicleregistrations covers California at ZIP × make × model-year × fuel.
- Statewide only. TxDMV publishes one row per fiscal year for the whole state. There is
fiscal years 2001 through 2021 and recent years are simply absent. asof carries the refresh date, coversfiscalyears the span, and a note says so in words. Asking for fiscalyear="2024" returns fiscalyearunavailable rather than an empty row list.
- The series stops at FY2021. TxDMV last refreshed it on 2023-03-06, so it covers
totalvehicles is only set when a single fiscal year is requested, because that row genuinely is the whole Texas fleet for that year. Rows from different fiscal years are not** summed: they are cumulative snapshots of largely the same vehicles, so a sum would double-count every car that stayed registered.
Verified live 2026-07-29: FY2001 totalallvehicles_registered = 17,906,116; FY2021 = 25,236,442.
Data sources
and Pickup Truck Registrations by Year". 21 rows, FY2001–FY2021.
- https://data.texas.gov/resource/cbmj-zeje.json — TxDMV "Passenger Vehicle, Motorcycle,
- https://data.texas.gov/api/views/cbmj-zeje.json — rowsUpdatedAt, used for as_of.
The three ofallvehicles columns are fractions of 1 (0.5831), not percentages; the pack converts them to percentages. fiscalyear is stored as text, so it is filtered with a string equality and ordered as a string — which is safe for four-digit years.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"tx-dmv": {
"url": "https://gateway.pipeworx.io/tx-dmv/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/tx-dmv/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Tx Dmv: common questions
- Is Tx Dmv MCP server safe?
- Mostly: it is graded B (77/100). Read the Tx Dmv safety report
- How do I install Tx Dmv?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Tx Dmv need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Tx Dmv maintained?
- The last commit was 47 days ago (2026-09-18). The latest release is v0.2.0.
- Is Tx Dmv up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Tx Dmv compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 304 ms (faster than 47% of 30,031 servers). Full comparison.