Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
DMV Transit is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Unofficial DC, Maryland and Virginia transit: trips, Metro, buses, rail, fares and alerts.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http dmv-transit-mcp https://dmvtransit.com/mcp
# 2 — ask your agent for something these tools do
# search_transit_info, get_service_alerts, get_rider_reports and 15 more
DMV Transit costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http dmv-transit-mcp https://dmvtransit.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Full-text search of the agencies' web pages: fares, how to pay, accessibility, safety, rules, new-rider/visitor guides, and service-change notices. NOT a source for routes, stops, schedules, hours or service days — use get_metro_route, plan_connection, get_route or transfers_at (GTFS schedule data) for those. Args: query: Natural-language search terms, e.g. "pay with phone" or "bringing a bik
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| category | no | — | |
| limit | integer | no | — |
Live service disruptions: WMATA incidents (Metrorail, Metrobus, elevators) and agencies' GTFS-realtime alerts (detours, closed stops, missed trips). Args: line: Metrorail line code (RD, BL, YL, OR, GR, SV) or bus route number. station: Metrorail station name or code. mode: "rail", "bus", or "elevator_escalator". agency: Agency slug, e.g. "wmata", "metrobus", "fairfax-connector".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| line | no | — | |
| station | no | — | |
| mode | no | — | |
| agency | no | — |
Recent reports from other RIDERS (crowdsourced on this site): delays, crowding, broken elevators, tips. Unverified and unofficial: always present them as "riders reported ...", with how long ago, never as agency information, and never let them replace the timetable or official alerts. Args: station: A station or stop name to filter by (matched loosely). line: A line or route to filter by,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| station | no | — | |
| line | no | — | |
| days | integer | no | — |
Elevators and escalators currently out of service, optionally for one station. Answer only from this tool's results: never add routes, hours, phone numbers, addresses or tips from memory. Unofficial tool, not affiliated with WMATA or any transit agency.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| station | no | — |
Lines served, address, parking availability, transfers, and entrances for a station (accepts a name like "Gallery Place" or a code like "B01"). Answer only from this tool's results: never add routes, hours, phone numbers, addresses or tips from memory. Unofficial tool, not affiliated with WMATA or any transit agency.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| station | string | yes | — |
Station-to-station Metrorail fare. Args: origin: Origin station name or code. destination: Destination station name or code. rider_type: "regular"/"peak", "offpeak", or "senior"/"disabled"/"reduced". Answer only from this tool's results: never add routes, hours, phone numbers, addresses or tips from memory. Unofficial tool, not affiliated with WMATA or any transit agency.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | — |
| destination | string | yes | — |
| rider_type | string | no | — |
Find where a street address, hotel, attraction or other place is, in the DC, Maryland and Northern Virginia area. Call this whenever a rider names a place that isn't plainly a station, before planning a trip from or to it. Check that the result is the place they meant, and ask them if several fit. Pass a result's point to plan_trip, plan_connection or find_stops_near. Args: query: What the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| limit | integer | no | — |
Real trip options from the agencies' timetables, like the site's map: trips leaving in the 3 hours after the given time from each agency's closest stops (up to about a mile's walk; the walking time is part of each option), direct trips first, one transfer only when needed, two transfers only when nothing simpler works, and transfers only between stops within 0.3 km. Options with short transfer wai
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | — |
| destination | string | yes | — |
| depart_at | no | — |
How to ride Metrorail between two stations: which line(s), where to change trains, which direction ("toward ..."), number of stops, and the fare. Use this for EVERY Metrorail trip — never assume two stations share a line. Args: origin: Station name, code (e.g. "C10"), or airport name/code ("DCA", "Dulles"). destination: Station name, code, or airport name/code. Answer only from this tool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | — |
| destination | string | yes | — |
List content categories with document counts and data freshness. Answer only from this tool's results: never add routes, hours, phone numbers, addresses or tips from memory. Unofficial tool, not affiliated with WMATA or any transit agency.
No parameter schema on file.
Full text of the primary guide for a topic: new_rider, visitor, payment, fares, accessibility, safety, or maps. Answer only from this tool's results: never add routes, hours, phone numbers, addresses or tips from memory. Unofficial tool, not affiliated with WMATA or any transit agency.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | — |
Every transit system in the region (WMATA + VRE, Virginia Breeze, Fairfax Connector, ART, DASH, CUE, Loudoun, OmniRide): mode, role, strengths, service area, a one-line fare/payment summary, and data freshness. Answer only from this tool's results: never add routes, hours, phone numbers, addresses or tips from memory. Unofficial tool, not affiliated with WMATA or any transit agency.
No parameter schema on file.
Stops and stations within walking distance of a place, across all agencies. Args: place: A Metro station name, a stop name, or "lat,lon". radius_m: Search radius in meters (default 400). agency: Optional feed slug to restrict to (e.g. "dash", "vre", "wmata"). Answer only from this tool's results: never add routes, hours, phone numbers, addresses or tips from memory. Unofficial tool,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| place | string | yes | — |
| radius_m | integer | no | — |
| agency | no | — |
One route from an agency's GTFS schedule: days and hours of service, typical frequency, endpoints, fare, and any live disruptions on it. Args: agency: Agency slug or name (e.g. "metrobus", "wmata" for Metrorail lines, "fairfax-connector", "OmniRide", "loudoun"). query: Route number or name (e.g. "A11", "Blue", "599", "Metro Express"). Answer only from this tool's results: never a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agency | string | yes | — |
| query | string | yes | — |
Routes from OTHER systems reachable on foot from a station or stop, grouped by agency, each with walk time and its service window from the GTFS schedules. Pass day (e.g. "saturday") and/or time ("HH:MM") to get a per-connection feasibility check. Answer only from this tool's results: never add routes, hours, phone numbers, addresses or tips from memory. Unofficial tool, not affiliated with WM
| Parameter | Type | Required | Notes |
|---|---|---|---|
| place | string | yes | — |
| day | no | — | |
| time | no | — |
How to pay to ride one agency. fare_page_text is the agency's own fare page (the source for prices, discounts and transfer rules); the other fields are a shorter hand-maintained summary that the fare page overrides. Args: agency: Agency slug or name (e.g. "vre", "dash", "omniride", "wmata", "metrobus"). Answer only from this tool's results: never add routes, hours, phone numbers, a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agency | string | yes | — |
Advise on getting between two places across systems: which system for each leg, the transfer hub, WHICH DAYS/TIMES the connection works, and the fare + how to pay per leg. Guidance, not a booked itinerary. Args: origin: Address, place name, station, or "lat,lon". destination: Address, place name, station, or "lat,lon". when: Optional — a day ("sunday", "weekday") to check feasibility
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | — |
| destination | string | yes | — |
| when | no | — |
Estimate the total fare for a cross-system trip: per-leg fares, how to pay each, and a total — noting each leg is usually a separate payment. Origin and destination can be addresses, places, stations or "lat,lon". Answer only from this tool's results: never add routes, hours, phone numbers, addresses or tips from memory. Unofficial tool, not affiliated with WMATA or any transit agency.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | — |
| destination | string | yes | — |
| when | no | — | |
| rider_category | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install DMV Transit or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_transit_info | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_service_alerts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_rider_reports | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_elevator_escalator_status | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_station_info | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_fare | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| geocode_address | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| plan_trip | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_metro_route | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_topics | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_guide | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_agencies | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| find_stops_near | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_route | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| transfers_at | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| how_to_pay | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| plan_connection | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| estimate_trip_cost | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish DMV Transit can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.