mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stops_around_location / alternatives
mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stops_around_locationThe best live alternatives to mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stops_around_location right now are mcp-registry/io.github.pipeworx-io/transit-land/search_stops, mcp-registry/io.github.pipeworx-io/wmata/bus_stops, mcp-registry/io.github.srivastsh/muni-mcp/muni_nearby_stops, mcp-registry/io.github.pipeworx-io/transit-land/departures_at_stop, mcp-registry/io.github.pipeworx-io/tfl/arrivals — capability-matched and ranked by current reliability. mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stops_around_location itself is currently "healthy".
mcp-registry/io.github.pipeworx-io/transit-land/search_stops is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/wmata/bus_stops, mcp-registry/io.github.srivastsh/muni-mcp/muni_nearby_stops, mcp-registry/io.github.pipeworx-io/transit-land/departures_at_stop, mcp-registry/io.github.pipeworx-io/tfl/arrivals. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stops_around_location's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.vbhjckfd%2Ftimetable-api-node%2Fget_stops_around_location.
By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.vbhjckfd%2Ftimetable-api-node%2Fget_stops_around_location
or MCP find_alternatives. Check mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stops_around_location's live status: https://glimind.com/tool/mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stops_around_location.