{
  "markdown": "# @pipeworx/mo-dmv\n\nMissouri DMV data: the Department of Revenue's driver and motor-vehicle **license offices**,\nwith hours, the contract agent who runs each one, and the upcoming dates it will be closed.\nKeyless.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## What Missouri calls its DMV\n\nMissouri has no \"DMV\". Driver licensing and vehicle registration happen at **license offices**\nrun by the **Missouri Department of Revenue**, and — unusually — the state does not staff them\nitself. All 176 offices are contracted out to private agents, which is why `agent`,\n`officemanager` and `contractmanager` are real columns here and have no analogue in another\nstate's office file. Hours, phone numbers and closures follow the agent, not the state.\n\n## Tools\n\n| Tool | What it returns |\n|---|---|\n| `mo_dmv_license_offices` | Address, phone, days and hours open, coordinates, contract agent, office manager, and upcoming closure dates for all 176 offices |\n\nFilters: `city`, `name`, `zip`, `limit`.\n\n## Auth\n\nNone. `data.mo.gov` is a public Socrata portal and the public rate limit is ample without an\napp token.\n\n## Why this is the freshest DMV endpoint in any state\n\nMissouri **refreshes this dataset daily** — `as_of` came back as the current date on every\nverification call. That is what makes `additional_days_closed` worth returning: the closure\nlist is current enough to plan a visit around, which no other state's office file supports.\n\nEntries can be whole days (`11/27/2026`) or partial (`6/22/2026 Closed Partial Day PM`), and\nthey sit *ahead of* the separately published `holidays_closed` list rather than duplicating it.\n\n## Gotchas worth knowing\n\nThese are live-verified behaviours, not guesses:\n\n- **`county` is empty on all 176 rows.** The column exists upstream and is null everywhere, so\n  the tool passes it through as `null` rather than inventing one. Filter by `city` instead.\n- **`type` is `1MV` on every office.** Every Missouri license office does both driver licensing\n  and motor vehicle work, so the code carries no discriminating information today; it is\n  surfaced in `office_type` in case the state ever splits the categories.\n- **Some ZIPs are stored as ZIP+4 with no hyphen** (`658075187`). The `zip` filter is a\n  prefix match, so a five-digit ZIP still matches those rows.\n- **`url` is a Facebook page when it exists.** Many contract agents run a Facebook page instead\n  of a website, and that is the only per-office link the state publishes.\n- **`as_of` is fetched concurrently with the data**, not after it. Socrata throttles\n  unauthenticated bursts and the metadata helper does not retry, so a sequential call\n  intermittently lost the refresh date — on a file whose whole value is a daily refresh.\n\n## Data sources\n\n- [data.mo.gov](https://data.mo.gov) Socrata `835g-7keg` — Missouri Department of Revenue\n  Driver and Motor Vehicle License Offices\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"mo-dmv\": {\n      \"url\": \"https://gateway.pipeworx.io/mo-dmv/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/mo-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 Mo 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": 4972,
  "sha": "01f05fae34dd19f67fd92cee986e7a0205ac25b322660b87436769f4938d1b52",
  "repo_slug": "pipeworx-io/mcp-mo-dmv",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_mo_dmv_7933a768/readme"
}