{
  "markdown": "# @pipeworx/tx-dmv\n\nTexas DMV (TxDMV) MCP — statewide vehicle, pickup and motorcycle registration totals by\nfiscal year, from TxDMV's own published series.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n- `tx_dmv_vehicle_registrations(fiscal_year?, limit?)` — total vehicles registered in Texas\n  for a fiscal year, split into passenger cars, pickup trucks of one ton or less and\n  motorcycles, each with its share of the fleet. Answers \"how many vehicles are registered in\n  Texas\", \"how many motorcycles are registered in Texas\", and growth across years.\n\n## Auth\n\nKeyless.\n\n## Grain and vintage — read this before quoting a number\n\nTwo things about this dataset trip people up, so both are reported on every response:\n\n1. **Statewide only.** TxDMV publishes one row per fiscal year for the whole state. There is\n   no county, city or ZIP breakdown in this series, and no make/model/fuel split. Passing\n   `county`, `zip`, `make`, `model_year` or `fuel_type` returns\n   `{ found: false, reason: \"grain_unavailable\" }` with a hint rather than silently ignoring\n   the argument. For a ZIP-level fleet breakdown, `ca_dmv_vehicle_registrations` covers\n   California at ZIP × make × model-year × fuel.\n2. **The series stops at FY2021.** TxDMV last refreshed it on **2023-03-06**, so it covers\n   **fiscal years 2001 through 2021** and recent years are simply absent. `as_of` carries the\n   refresh date, `covers_fiscal_years` the span, and a `note` says so in words. Asking for\n   `fiscal_year=\"2024\"` returns `fiscal_year_unavailable` rather than an empty row list.\n\n`total_vehicles` is only set when a single fiscal year is requested, because that row genuinely\nis the whole Texas fleet for that year. Rows from different fiscal years are **not** summed:\nthey are cumulative snapshots of largely the same vehicles, so a sum would double-count every\ncar that stayed registered.\n\nVerified live 2026-07-29: FY2001 `total_all_vehicles_registered` = 17,906,116;\nFY2021 = 25,236,442.\n\n## Data sources\n\n- `https://data.texas.gov/resource/cbmj-zeje.json` — TxDMV \"Passenger Vehicle, Motorcycle,\n  and Pickup Truck Registrations by Year\". 21 rows, FY2001–FY2021.\n- `https://data.texas.gov/api/views/cbmj-zeje.json` — `rowsUpdatedAt`, used for `as_of`.\n\nThe three `*_of_all_vehicles` columns are fractions of 1 (`0.5831`), not percentages; the pack\nconverts them to percentages. `fiscal_year` is stored as text, so it is filtered with a string\nequality and ordered as a string — which is safe for four-digit years.\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"tx-dmv\": {\n      \"url\": \"https://gateway.pipeworx.io/tx-dmv/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/tx-dmv/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Tx Dmv data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 4600,
  "sha": "9de3fa46b899ecda35a5f174273edfb1d4b2d8232d8532be9bf08078e61a92ea",
  "repo_slug": "pipeworx-io/mcp-tx-dmv",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_tx_dmv_d1149ab0/readme"
}