mcp-registry/io.github.pipeworx-io/tfl/plan_journey / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/tfl/plan_journey

The best live alternatives to mcp-registry/io.github.pipeworx-io/tfl/plan_journey right now are mcp-registry/io.github.vbhjckfd/timetable-api-node/plan_trip, mcp-registry/io.github.pipeworx-io/tomtom/route, mcp-registry/com.googleapis.mapstools/mcp/compute_routes, mcp-registry/io.github.pipeworx-io/openrouteservice/directions, mcp-registry/com.mydriverparis/booking/resolve_location — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/tfl/plan_journey itself is currently "healthy".

alternative	server
mcp-registry/io.github.vbhjckfd/timetable-api-node/plan_trip	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/com.googleapis.mapstools/mcp/compute_routes	com.googleapis.mapstools/mcp	live status →
mcp-registry/io.github.pipeworx-io/openrouteservice/directions	io.github.pipeworx-io/openrouteservice	live status →
mcp-registry/com.mydriverparis/booking/resolve_location	com.mydriverparis/booking	live status →
mcp-registry/io.github.pipeworx-io/geoapify/routing	io.github.pipeworx-io/geoapify	live status →
mcp-registry/io.github.pipeworx-io/google_maps/maps_directions	io.github.pipeworx-io/google_maps	live status →
mcp-registry/io.github.tickadoo/tickadoo-mcp/search_local_experiences	io.github.tickadoo/tickadoo-mcp	live status →
mcp-registry/io.github.yondry-ltd/day-planner/plan_day	io.github.yondry-ltd/day-planner	live status →
mcp-registry/io.github.tickadoo/tickadoo-mcp/plan_itinerary	io.github.tickadoo/tickadoo-mcp	live status →
mcp-registry/io.github.pipeworx-io/mapbox/directions	io.github.pipeworx-io/mapbox	live status →
mcp-registry/guide.capitol/capitolguide/route_between	guide.capitol/capitolguide	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/tfl/plan_journey?

mcp-registry/io.github.vbhjckfd/timetable-api-node/plan_trip is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/tomtom/route, mcp-registry/com.googleapis.mapstools/mcp/compute_routes, mcp-registry/io.github.pipeworx-io/openrouteservice/directions, mcp-registry/com.mydriverparis/booking/resolve_location. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/tfl/plan_journey down right now?

mcp-registry/io.github.pipeworx-io/tfl/plan_journey's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Ftfl%2Fplan_journey.

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%2Ftfl%2Fplan_journey or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/tfl/plan_journey's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/tfl/plan_journey.