mcp-registry/io.github.pipeworx-io/geoapify/routing / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/geoapify/routing

The best live alternatives to mcp-registry/io.github.pipeworx-io/geoapify/routing right now are mcp-registry/io.github.pipeworx-io/tomtom/route, mcp-registry/io.github.pipeworx-io/mapbox/directions, mcp-registry/io.github.pipeworx-io/openrouteservice/directions, mcp-registry/com.googleapis.mapstools/mcp/compute_routes, mcp-registry/io.github.pipeworx-io/openrouteservice/matrix — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/geoapify/routing itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/tomtom/route	io.github.pipeworx-io/tomtom	live status →
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/com.googleapis.mapstools/mcp/compute_routes	com.googleapis.mapstools/mcp	live status →
mcp-registry/io.github.pipeworx-io/openrouteservice/matrix	io.github.pipeworx-io/openrouteservice	live status →
mcp-registry/io.github.pipeworx-io/google_maps/maps_distance_matrix	io.github.pipeworx-io/google_maps	live status →
mcp-registry/io.github.pipeworx-io/osrm/route	io.github.pipeworx-io/osrm	live status →
mcp-registry/io.github.pipeworx-io/mapbox/directions_matrix	io.github.pipeworx-io/mapbox	live status →
mcp-registry/io.github.pipeworx-io/osrm/table	io.github.pipeworx-io/osrm	live status →
mcp-registry/io.github.foundrynet/foundrynet-geo/distance	io.github.FoundryNet/foundrynet-geo	live status →
mcp-registry/io.github.pipeworx-io/google_maps/maps_directions	io.github.pipeworx-io/google_maps	live status →
mcp-registry/io.github.vbhjckfd/timetable-api-node/plan_trip	io.github.vbhjckfd/timetable-api-node	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/geoapify/routing?

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

Is mcp-registry/io.github.pipeworx-io/geoapify/routing down right now?

mcp-registry/io.github.pipeworx-io/geoapify/routing's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fgeoapify%2Frouting.

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%2Fgeoapify%2Frouting or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/geoapify/routing's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/geoapify/routing.