A
licenseB
qualityD
maintenanceEnables route planning and transit information retrieval for Japan using the public Transit API. Supports searching stations, planning routes, and checking departures.
10
2
MIT
tokyo-transit-mcp
by loosephoto
Related Servers
Alternatives to tokyo-transit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides access to Tokyo's WBGT (Wet Bulb Globe Temperature) heat index forecast and real-time data from multiple observation points using Japan's Ministry of the Environment official data for heat stroke prevention.3MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to answer questions about Japan's railway network with accurate track-connection data, including station neighbors and local subgraphs for all 9,043 stations nationwide.2MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Japanese public transit journey planning with interactive map UI, enabling station search, route planning, and departure lookups via natural language.MIT
- AlicenseBqualityFmaintenanceEnables AI clients to access Boston's MBTA public transit data, including real-time predictions, schedules, route planning, and service alerts.321Apache 2.0
- AlicenseAqualityBmaintenanceJapan Operations OS for AI agents — 14 knowledge domains covering regulations, protocols, calendar, travel, food culture, language, disaster safety, daily life, and persistent memory. 31 MCP tools via REST + Streamable HTTP.31MIT
TDQS
A3.7/5.0
Scored across 13 tools
Disambiguation4/5
Tools are mostly distinct, split cleanly across resource domains (rail, bus, ferry, flight, weather, fare, timetable). Minor overlap exists between search_route and search_bus (both do transfer routing) and between get_operator_routes and list_transit_operators, but descriptions clarify the boundaries well enough.
Naming Consistency5/5
Consistent verb_noun pattern throughout: get_/list_/search_ prefixes paired with clear nouns (get_station_info, list_ferry_ports, search_flight, search_fare). No mixing of conventions.
Tool Count5/5
13 tools is a well-scoped set for a multi-modal transit server covering rail, bus, ferry, flight, weather, fares, and timetables. Each tool maps to a distinct transit query need with none feeling redundant.
Completeness4/5
Strong lifecycle coverage: operators, routes, stations, fares, timetables, running status, plus bus/ferry/flight and weather. Minor gaps like no station-level facility/disruption detail tool, but agents can work around these.
Maintenance
ActivityNo data
ResponsivenessSyncing