mcp-registry/io.github.pipeworx-io/google_maps/maps_directions / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/google_maps/maps_directions

The best live alternatives to mcp-registry/io.github.pipeworx-io/google_maps/maps_directions right now are mcp-registry/io.github.pipeworx-io/mapbox/directions, mcp-registry/io.github.pipeworx-io/openrouteservice/directions, mcp-registry/io.github.pipeworx-io/tomtom/route, mcp-registry/io.github.pipeworx-io/geoapify/routing, mcp-registry/io.github.vbhjckfd/timetable-api-node/plan_trip — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/google_maps/maps_directions itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/mapbox/directions	io.github.pipeworx-io/mapbox	live status →
mcp-registry/io.github.pipeworx-io/openrouteservice/directions	io.github.pipeworx-io/openrouteservice	live status →
mcp-registry/io.github.pipeworx-io/tomtom/route	io.github.pipeworx-io/tomtom	live status →
mcp-registry/io.github.pipeworx-io/geoapify/routing	io.github.pipeworx-io/geoapify	live status →
mcp-registry/io.github.vbhjckfd/timetable-api-node/plan_trip	io.github.vbhjckfd/timetable-api-node	live status →
mcp-registry/guide.capitol/capitolguide/route_between	guide.capitol/capitolguide	live status →
mcp-registry/io.github.tickadoo/tickadoo-mcp/get_transfer_info	io.github.tickadoo/tickadoo-mcp	live status →
mcp-registry/io.github.pipeworx-io/tfl/plan_journey	io.github.pipeworx-io/tfl	live status →
mcp-registry/io.github.vee3io/vee3/google-maps.search	io.github.Vee3io/vee3	live status →
mcp-registry/io.github.pipeworx-io/openrouteservice/matrix	io.github.pipeworx-io/openrouteservice	live status →
mcp-registry/io.github.pipeworx-io/transit-land/search_routes	io.github.pipeworx-io/transit-land	live status →
mcp-registry/io.github.pipeworx-io/mapbox/map_matching	io.github.pipeworx-io/mapbox	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/google_maps/maps_directions?

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

Is mcp-registry/io.github.pipeworx-io/google_maps/maps_directions down right now?

mcp-registry/io.github.pipeworx-io/google_maps/maps_directions's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fgoogle_maps%2Fmaps_directions.

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%2Fgoogle_maps%2Fmaps_directions or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/google_maps/maps_directions's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/google_maps/maps_directions.