A
licenseA
qualityB
maintenanceProvides read-only access to structured Japanese railway data, enabling station searches without an API key and live Shinkansen timetable, fare, seat class, and stop queries with an Ekispert API key.
7
MIT
odpt-mcp
by koizumikento
Related Servers
Alternatives to odpt-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceIntegrates ODPT and JMA APIs to provide comprehensive transit information, route search, weather, and AI advice for the Tokyo metropolitan area.131MIT
- AlicenseNot gradedqualityBmaintenanceEnables interaction with official Japanese public data, including real-time train service status and live hazard alerts. It provides comprehensive lookups covering station context, accessible toilets, and municipality information.286 npmMIT
- AlicenseBqualityDmaintenanceEnables route planning and transit information retrieval for Japan using the public Transit API. Supports searching stations, planning routes, and checking departures.102MIT
- AlicenseNot gradedqualityCmaintenanceEnables real-time access to Boston MBTA transit data (subway, bus, commuter rail, etc.) via the MBTA v3 API.279 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables querying Swiss public transport (trains, buses, trams, boats) for stations, connections, and station boards via the opendata.ch API.-
TDQS
A4/5.0
Scored across 8 tools
Disambiguation5/5
Each tool targets a distinct resource+action: search (railway/stops) vs. schedule (timetable) vs. price (fare) vs. status, cleanly partitioned between the rail and bus domains. An agent can unambiguously route a transit query to one tool, and the descriptions reinforce the IDs each downstream tool needs.
Naming Consistency5/5
All names use consistent snake_case with a verb_noun structure (search_railway, get_station_timetable, get_bus_fare). The domain noun (railway vs. bus) is predictable across the set, with no mixed conventions.
Tool Count5/5
Eight tools is well within the ideal range and each earns its place: a search, timetable, fare, and status tool for each of the two transit domains. Nothing is redundant or obviously missing from a count perspective.
Completeness4/5
The surface covers the core lifecycle for both rail and bus: find the entity, get its schedule, get the fare, plus rail service status. Minor gaps remain, such as resolving a line to its full station sequence or listing all stops on a rail line (the bus side has get_bus_route but the rail side lacks an equivalent).
Maintenance
ActivityMaintained
ResponsivenessOutdated data