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

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

The best live alternatives to mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stop_realtime right now are mcp-registry/io.github.srivastsh/muni-mcp/muni_departures_by_route_stop, mcp-registry/io.github.pipeworx-io/tfl/arrivals, mcp-registry/io.github.pipeworx-io/transit-land/departures_at_stop, mcp-registry/dev.infranode/infranode/transit_departures, mcp-registry/io.github.pipeworx-io/wmata/bus_predictions — capability-matched and ranked by current reliability. mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stop_realtime itself is currently "healthy".

alternative	server
mcp-registry/io.github.srivastsh/muni-mcp/muni_departures_by_route_stop	io.github.srivastsh/muni-mcp	live status →
mcp-registry/io.github.pipeworx-io/tfl/arrivals	io.github.pipeworx-io/tfl	live status →
mcp-registry/io.github.pipeworx-io/transit-land/departures_at_stop	io.github.pipeworx-io/transit-land	live status →
mcp-registry/dev.infranode/infranode/transit_departures	dev.infranode/infranode	live status →
mcp-registry/io.github.pipeworx-io/wmata/bus_predictions	io.github.pipeworx-io/wmata	live status →
mcp-registry/io.github.srivastsh/muni-mcp/muni_departures	io.github.srivastsh/muni-mcp	live status →
mcp-registry/io.github.pipeworx-io/wmata/bus_stops	io.github.pipeworx-io/wmata	live status →
mcp-registry/io.github.pipeworx-io/transit-land/search_stops	io.github.pipeworx-io/transit-land	live status →
mcp-registry/dev.infranode/infranode/transit	dev.infranode/infranode	live status →
mcp-registry/io.github.pipeworx-io/wmata/bus_route_details	io.github.pipeworx-io/wmata	live status →
mcp-registry/io.github.pipeworx-io/tfl/stop_search	io.github.pipeworx-io/tfl	live status →
mcp-registry/io.github.pipeworx-io/tomtom/route	io.github.pipeworx-io/tomtom	live status →

FAQ

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

mcp-registry/io.github.srivastsh/muni-mcp/muni_departures_by_route_stop is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/tfl/arrivals, mcp-registry/io.github.pipeworx-io/transit-land/departures_at_stop, mcp-registry/dev.infranode/infranode/transit_departures, mcp-registry/io.github.pipeworx-io/wmata/bus_predictions. Glimind ranks alternatives by semantic similarity and live health.

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

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

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_stop_realtime or MCP find_alternatives. Check mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stop_realtime's live status: https://glimind.com/tool/mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stop_realtime.