A
licenseA
qualityC
maintenanceEnables users to search for stops, retrieve live departures with real-time delays, and plan public transport journeys in the Hannover region via the EFA interface.
3
MIT
Busse Göttingen MCP-Server
by gebab88
Related Servers
Alternatives to Busse Göttingen MCP-Server
No user-submitted related servers found.
Related Servers
- FlicenseDqualityDmaintenanceProvides access to Berlin's public transport data through the VBB API, enabling users to search stops, get departures, and plan journeys across Berlin-Brandenburg.36-
- FlicenseNot gradedqualityDmaintenanceEnables querying Swiss public transport (trains, buses, trams, boats) for stations, connections, and station boards via the opendata.ch API.-
mcp-db-railofficial
AlicenseNot gradedqualityBmaintenanceEnables keyless access to German and European rail and public transport data, including station search, live departures and arrivals, and multi-leg journey planning with real-time updates.261 npmMIT- AlicenseAqualityCmaintenanceEnables querying public transit data through the Transitous MOTIS API, including station search, journey routing, and generic API actions with caching and rate limiting.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying global transit data including agencies, routes, stops, and departures through a GTFS aggregator.8 npmMIT
TDQS
A3.6/5.0
Scored across 4 tools
Disambiguation4/5
Each tool targets a distinct operation: stop_search returns stop references, departures gives a two-hour departure window, journey computes connections between stops, and timetable returns a full-day schedule. departures and timetable both relate to a stop but differ by time horizon and real-time inclusion, so confusion is limited.
Naming Consistency3/5
stop_search uses a verb_noun snake_case pattern, while departures, journey, and timetable are bare nouns. The set is readable but lacks a single predictable naming convention.
Tool Count5/5
Four tools cover the core read-only transit queries without redundancy. Each earns its place and the count is well within a healthy range.
Completeness4/5
The surface covers stop lookup, departures, journey planning, and timetable, which are the main transit information needs. Minor gaps remain, such as nearby-stop search or line/disruption details, but agents can work around them.
Maintenance
ActivityMaintained
ResponsivenessNo issues