mcp-registry/io.github.outdoorithm/outdoorithm/calculate_drive_times / alternatives
mcp-registry/io.github.outdoorithm/outdoorithm/calculate_drive_timesThe best live alternatives to mcp-registry/io.github.outdoorithm/outdoorithm/calculate_drive_times right now are mcp-registry/com.googleapis.mapstools/mcp/compute_routes, mcp-registry/io.github.pipeworx-io/google_maps/maps_distance_matrix, mcp-registry/io.github.pipeworx-io/openrouteservice/matrix, mcp-registry/io.github.pipeworx-io/mapbox/directions_matrix, mcp-registry/io.github.vbhjckfd/timetable-api-node/plan_trip — capability-matched and ranked by current reliability. mcp-registry/io.github.outdoorithm/outdoorithm/calculate_drive_times itself is currently "healthy".
mcp-registry/com.googleapis.mapstools/mcp/compute_routes is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/google_maps/maps_distance_matrix, mcp-registry/io.github.pipeworx-io/openrouteservice/matrix, mcp-registry/io.github.pipeworx-io/mapbox/directions_matrix, mcp-registry/io.github.vbhjckfd/timetable-api-node/plan_trip. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.outdoorithm/outdoorithm/calculate_drive_times's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.outdoorithm%2Foutdoorithm%2Fcalculate_drive_times.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.outdoorithm%2Foutdoorithm%2Fcalculate_drive_times
or MCP find_alternatives. Check mcp-registry/io.github.outdoorithm/outdoorithm/calculate_drive_times's live status: https://glimind.com/tool/mcp-registry/io.github.outdoorithm/outdoorithm/calculate_drive_times.