F
licenseNot graded
qualityC
maintenanceAn MCP server that provides real-time Hong Kong public transport ETA information.
-
wheels-router-mcp
OfficialRelated Servers
Alternatives to wheels-router-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server providing access to Hong Kong transportation data, including passenger traffic statistics at control points and real-time bus arrival information for KMB and Long Win Bus services.4MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides access to Hong Kong government city data, including ambulance service indicators, via a FastMCP interface.2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Japanese public transit journey planning with interactive map UI, enabling station search, route planning, and departure lookups via natural language.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for Korean public transit that enables route planning with real-time bus and subway arrivals, including fallback options. It combines ODsay route search with real-time data from Gyeonggi Bus and Seoul Metro systems.-
- AlicenseCqualityCmaintenanceMCP server for the UK Bus Open Data Service, enabling timetable queries, stop search, route discovery, journey planning, and real-time bus tracking.1623 PyPIMIT
TDQS
B3/5.0
Scored across 3 tools
Disambiguation4/5
plan_trip and search_location have clear, non-overlapping purposes, and hello_tool is obviously set apart. However, hello_tool is a vague stub that doesn't fit the travel domain, so there is a slight coherence cost.
Naming Consistency4/5
plan_trip and search_location both follow a verb_noun snake_case pattern. hello_tool breaks the pattern with a greeting-style verb, but since only one of three tools deviates, the naming is mostly consistent.
Tool Count3/5
Three tools is borderline for a transit router, and only two are actually useful. hello_tool is filler, which makes the effective functional surface feel thin for the stated purpose.
Completeness4/5
The core workflow is covered: search_location for origin/destination lookup and plan_trip for routing. Minor gaps exist, such as route/fare rule inspection or provider metadata, but agents can complete basic trip planning without dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues