mcp-registry/io.github.pipeworx-io/osrm/trip / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/osrm/trip

The best live alternatives to mcp-registry/io.github.pipeworx-io/osrm/trip right now are mcp-registry/io.github.vbhjckfd/timetable-api-node/plan_trip, mcp-registry/com.pricetik/mcp-server/pricetik_trip_plan, mcp-registry/io.github.pipeworx-io/tomtom/route, mcp-registry/com.gojinko.mcp/jinko/trip, mcp-registry/io.github.srivastsh/bart-mcp/bart_trip — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/osrm/trip 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/com.pricetik/mcp-server/pricetik_trip_plan	com.pricetik/mcp-server	live status →
mcp-registry/io.github.pipeworx-io/tomtom/route	io.github.pipeworx-io/tomtom	live status →
mcp-registry/com.gojinko.mcp/jinko/trip	com.gojinko.mcp/jinko	live status →
mcp-registry/io.github.srivastsh/bart-mcp/bart_trip	io.github.srivastsh/bart-mcp	live status →
mcp-registry/io.github.pipeworx-io/openrouteservice/matrix	io.github.pipeworx-io/openrouteservice	live status →
mcp-registry/io.github.dynamitecircle/dc/trips_overlaps	io.github.dynamitecircle/dc	live status →
mcp-registry/ai.snowsure/snow/plan_ski_road_trip	ai.snowsure/snow	live status →
mcp-registry/io.github.dynamitecircle/dc/trips	io.github.dynamitecircle/dc	live status →
mcp-registry/com.pricetik/mcp-server/pricetik_group_trip_create	com.pricetik/mcp-server	live status →
mcp-registry/com.viatsy/mcp/get_trip_details	com.viatsy/mcp	live status →
mcp-registry/io.github.dynamitecircle/dc/trips_create	io.github.dynamitecircle/dc	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/osrm/trip?

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/com.pricetik/mcp-server/pricetik_trip_plan, mcp-registry/io.github.pipeworx-io/tomtom/route, mcp-registry/com.gojinko.mcp/jinko/trip, mcp-registry/io.github.srivastsh/bart-mcp/bart_trip. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/osrm/trip down right now?

mcp-registry/io.github.pipeworx-io/osrm/trip's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fosrm%2Ftrip.

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%2Fosrm%2Ftrip or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/osrm/trip's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/osrm/trip.