A
licenseNot graded
qualityD
maintenanceEnables querying real-time BART and SF Muni transit data, including departures, trip planning, fares, advisories, routes, alerts, vehicle positions, and schedules, from any MCP-compatible client.
1
MIT
tdx-taiwan-mcp
Related Servers
Alternatives to tdx-taiwan-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables public-transport journey planning, place search, realtime departures and timetables, usable from any MCP client.9MIT
- AlicenseAqualityBmaintenanceEnables querying Swedish Transport Administration open data for live train departures and arrivals, railway disruptions, road incidents, and measured road weather through MCP tools.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying Swiss public transport data (stations, departures, connections) from the Transport Open Data API via natural language through an MCP gateway.278 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables realtime bus arrival queries, route and stop searches, nearby station lookups, and transit planning for Chelaile-supported cities through MCP tools.11MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides tools for querying live transit data (stops, departures, routes, vehicles, alerts) from any WP GTFS Pro site, enabling AI assistants to answer rider questions.14 npmGPL 2.0
TDQS
A3.7/5.0
Scored across 50 tools
Disambiguation4/5
Tools are mostly distinct by transport mode and action, and descriptions clarify live vs scheduled vs station vs route. Some subtle overlaps remain, such as bus_stop_arrivals vs bus_eta, rail_station_departures vs mode-specific timetables, and flight_status vs flight_board, so an agent could occasionally misselect among the 50.
Naming Consistency4/5
All names use snake_case and a predictable domain-prefix plus descriptor pattern (bus_*, thsr_*, metro_*, traffic_*). Minor inconsistencies include singular/plural variation (bus_stops_nearby vs bus_stop_arrivals), noun vs action suffixes, and the generic tdx_get outlier.
Tool Count3/5
50 tools is heavy, but the server covers a genuinely broad multi-modal transport domain, so many tools are justified. Still, the count is unwieldy and several mode-specific tools could be consolidated or grouped to reduce selection load.
Completeness4/5
Coverage is extensive across buses, rail, metro, ferries, flights, traffic, parking, EV charging, and bike share, including live data, timetables, fares, alerts, and station information. The main gap is integrated cross-modal journey planning/trip routing; tdx_get helps fill obscure data gaps but not complex workflows.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues