mcp-registry/io.github.mfukushim/map-traveler-mcp/set_traveler_destination_address / alternatives

Live alternatives to mcp-registry/io.github.mfukushim/map-traveler-mcp/set_traveler_destination_address

The best live alternatives to mcp-registry/io.github.mfukushim/map-traveler-mcp/set_traveler_destination_address right now are mcp-registry/io.github.naeem-jtr/jtr-holidays/get_destinations, mcp-registry/com.gojinko.mcp/jinko/find_destination, mcp-registry/com.pricetik/mcp-server/pricetik_destinations, mcp-registry/com.skiplagged/mcp/sk_destinations_anywhere, mcp-registry/io.github.statico-alt/spacemolt/travel — capability-matched and ranked by current reliability. mcp-registry/io.github.mfukushim/map-traveler-mcp/set_traveler_destination_address itself is currently "unknown".

alternative	server
mcp-registry/io.github.naeem-jtr/jtr-holidays/get_destinations	io.github.naeem-jtr/jtr-holidays	live status →
mcp-registry/com.gojinko.mcp/jinko/find_destination	com.gojinko.mcp/jinko	live status →
mcp-registry/com.pricetik/mcp-server/pricetik_destinations	com.pricetik/mcp-server	live status →
mcp-registry/com.skiplagged/mcp/sk_destinations_anywhere	com.skiplagged/mcp	live status →
mcp-registry/io.github.statico-alt/spacemolt/travel	io.github.statico-alt/spacemolt	live status →
mcp-registry/ai.snowsure/snow/get_destination	ai.snowsure/snow	live status →

FAQ

What is the best alternative to mcp-registry/io.github.mfukushim/map-traveler-mcp/set_traveler_destination_address?

mcp-registry/io.github.naeem-jtr/jtr-holidays/get_destinations is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.gojinko.mcp/jinko/find_destination, mcp-registry/com.pricetik/mcp-server/pricetik_destinations, mcp-registry/com.skiplagged/mcp/sk_destinations_anywhere, mcp-registry/io.github.statico-alt/spacemolt/travel. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.mfukushim/map-traveler-mcp/set_traveler_destination_address down right now?

mcp-registry/io.github.mfukushim/map-traveler-mcp/set_traveler_destination_address's current verdict is "unknown". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.mfukushim%2Fmap-traveler-mcp%2Fset_traveler_destination_address.

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.mfukushim%2Fmap-traveler-mcp%2Fset_traveler_destination_address or MCP find_alternatives. Check mcp-registry/io.github.mfukushim/map-traveler-mcp/set_traveler_destination_address's live status: https://glimind.com/tool/mcp-registry/io.github.mfukushim/map-traveler-mcp/set_traveler_destination_address.