Servidor MCP de DMV Transit

• Nombre en el registrocom.dmvtransit/transitverificado en el registro MCP

El nombre en el registro está bajo dmvtransit.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-11-03
• Herramientas18
• El servidor se llamadmv-transit
• Versión del servidor1.30.0
• Versión del protocolo2025-06-18

El 2026-11-03 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 228 ms.

• Sus herramientas hacen todos los casos de uso comprobados: plan a trip between two places from agency timetables; ask fare and rider questions and see the agency source.
• Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
• Qué puede hacer un agente con él2 de 2 casos de uso
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta296 ms
• Espacio en el contexto del agente≈ 3692 tokenslas definiciones de todas sus herramientas (18), que el agente lleva en cada turno
• Definiciones de herramientasB · 85 de 100
• Resultados tipados7 de 18 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 16 de 18

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• search_transit_info

  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…

• get_service_alerts

  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…

• get_rider_reports

  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…

• get_elevator_escalator_status

  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…

• get_station_info

  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…

• get_fare

  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…

• geocode_address

  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…

• plan_trip

  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…

• get_metro_route

  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…

• list_topics

  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.

• get_guide

  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…

• list_agencies

  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…

• find_stops_near

  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…

• get_route

  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"…

• transfers_at

  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…

• how_to_pay

  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…

• plan_connection

  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…

• estimate_trip_cost

  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…