mcp-registry/io.github.pipeworx-io/wmata/bus_route_details / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/wmata/bus_route_details

The best live alternatives to mcp-registry/io.github.pipeworx-io/wmata/bus_route_details right now are mcp-registry/io.github.vbhjckfd/timetable-api-node/get_route_static, mcp-registry/io.github.srivastsh/muni-mcp/muni_departures_by_route_stop, mcp-registry/io.github.vbhjckfd/timetable-api-node/get_vehicle_info, mcp-registry/io.github.vbhjckfd/timetable-api-node/get_route_realtime, mcp-registry/run.cityheart/heart-routes/get_route_details — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/wmata/bus_route_details itself is currently "healthy".

alternative	server
mcp-registry/io.github.vbhjckfd/timetable-api-node/get_route_static	io.github.vbhjckfd/timetable-api-node	live status →
mcp-registry/io.github.srivastsh/muni-mcp/muni_departures_by_route_stop	io.github.srivastsh/muni-mcp	live status →
mcp-registry/io.github.vbhjckfd/timetable-api-node/get_vehicle_info	io.github.vbhjckfd/timetable-api-node	live status →
mcp-registry/io.github.vbhjckfd/timetable-api-node/get_route_realtime	io.github.vbhjckfd/timetable-api-node	live status →
mcp-registry/run.cityheart/heart-routes/get_route_details	run.cityheart/heart-routes	live status →
mcp-registry/com.moltravel/travel/tourradar_b2b-tour-map	com.moltravel/travel	live status →
mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stops_around_location	io.github.vbhjckfd/timetable-api-node	live status →
mcp-registry/io.github.vbhjckfd/timetable-api-node/get_stop_realtime	io.github.vbhjckfd/timetable-api-node	live status →
mcp-registry/io.github.pipeworx-io/tomtom/route	io.github.pipeworx-io/tomtom	live status →
mcp-registry/io.github.pipeworx-io/transit-land/search_routes	io.github.pipeworx-io/transit-land	live status →
mcp-registry/io.github.vbhjckfd/timetable-api-node/plan_trip	io.github.vbhjckfd/timetable-api-node	live status →
mcp-registry/io.github.pipeworx-io/geoapify/routing	io.github.pipeworx-io/geoapify	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/wmata/bus_route_details?

mcp-registry/io.github.vbhjckfd/timetable-api-node/get_route_static is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.srivastsh/muni-mcp/muni_departures_by_route_stop, mcp-registry/io.github.vbhjckfd/timetable-api-node/get_vehicle_info, mcp-registry/io.github.vbhjckfd/timetable-api-node/get_route_realtime, mcp-registry/run.cityheart/heart-routes/get_route_details. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/wmata/bus_route_details down right now?

mcp-registry/io.github.pipeworx-io/wmata/bus_route_details's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fwmata%2Fbus_route_details.

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.pipeworx-io%2Fwmata%2Fbus_route_details or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/wmata/bus_route_details's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/wmata/bus_route_details.