mcp-registry/io.github.vbhjckfd/timetable-api-node/get_nearby_vehicles / alternatives

Live alternatives to mcp-registry/io.github.vbhjckfd/timetable-api-node/get_nearby_vehicles

The best live alternatives to mcp-registry/io.github.vbhjckfd/timetable-api-node/get_nearby_vehicles right now are mcp-registry/io.github.pipeworx-io/geonames/get_nearby, mcp-registry/io.github.srivastsh/muni-mcp/muni_nearby_stops, mcp-registry/work.latlng.mcp/latlng/find_nearby_places, mcp-registry/io.github.pipeworx-io/wmata/bus_stops, mcp-registry/io.github.pipeworx-io/tomtom/route — capability-matched and ranked by current reliability. mcp-registry/io.github.vbhjckfd/timetable-api-node/get_nearby_vehicles itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/geonames/get_nearby	io.github.pipeworx-io/geonames	live status →
mcp-registry/io.github.srivastsh/muni-mcp/muni_nearby_stops	io.github.srivastsh/muni-mcp	live status →
mcp-registry/work.latlng.mcp/latlng/find_nearby_places	work.latlng.mcp/latlng	live status →
mcp-registry/io.github.pipeworx-io/wmata/bus_stops	io.github.pipeworx-io/wmata	live status →
mcp-registry/io.github.pipeworx-io/tomtom/route	io.github.pipeworx-io/tomtom	live status →
mcp-registry/dev.infranode/infranode/transit_departures	dev.infranode/infranode	live status →
mcp-registry/io.github.tickadoo/tickadoo-mcp/find_nearby_experiences	io.github.tickadoo/tickadoo-mcp	live status →
mcp-registry/io.tooloracle/hoteloracle/nearby_attractions	io.tooloracle/hoteloracle	live status →
mcp-registry/io.github.pipeworx-io/ebird/nearby_observations	io.github.pipeworx-io/ebird	live status →
mcp-registry/io.github.pipeworx-io/transit-land/search_stops	io.github.pipeworx-io/transit-land	live status →
mcp-registry/io.github.pipeworx-io/foursquare/nearby_places	io.github.pipeworx-io/foursquare	live status →
mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search	io.github.Vee3io/vee3	live status →

FAQ

What is the best alternative to mcp-registry/io.github.vbhjckfd/timetable-api-node/get_nearby_vehicles?

mcp-registry/io.github.pipeworx-io/geonames/get_nearby is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.srivastsh/muni-mcp/muni_nearby_stops, mcp-registry/work.latlng.mcp/latlng/find_nearby_places, mcp-registry/io.github.pipeworx-io/wmata/bus_stops, mcp-registry/io.github.pipeworx-io/tomtom/route. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.vbhjckfd/timetable-api-node/get_nearby_vehicles down right now?

mcp-registry/io.github.vbhjckfd/timetable-api-node/get_nearby_vehicles'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_nearby_vehicles.

How does Glimind pick alternatives?

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.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.vbhjckfd%2Ftimetable-api-node%2Fget_nearby_vehicles or MCP find_alternatives. Check mcp-registry/io.github.vbhjckfd/timetable-api-node/get_nearby_vehicles's live status: https://glimind.com/tool/mcp-registry/io.github.vbhjckfd/timetable-api-node/get_nearby_vehicles.