space-journey-mcp-engine
Related Servers
Alternatives to space-journey-mcp-engine
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables flight planning and aviation operations through intelligent airport resolution, great-circle route calculation, and aircraft performance estimation. Supports 28,000+ airports worldwide and 190+ aircraft types for comprehensive flight planning via natural language.4664 PyPI4MIT
- AlicenseBqualityDmaintenanceIntegration platform for aviation data sources including weather, NOTAMs, airport information, and flight planning APIs, enabling comprehensive pre-flight preparation and in-flight decision support.111MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to translate natural-language vacation or business travel goals into multi-leg flight segments, lodging selections, layover buffers, baggage-fee optimization, and consolidated reservation manifests.7MIT
- AlicenseAqualityBmaintenanceEnables an AI agent to look up airports, retrieve METAR/TAF weather, inspect live ADS-B traffic and arrivals/departures, and triage disruptions by composing multiple aviation data sources behind a single governed interface. It handles OAuth2 machine-to-machine credentials, credit-aware rate limiting with actionable structured errors, and PII-free logging, and reports missing data as explicit unknowns rather than implying an all-clear.8MIT
- FlicenseNot gradedqualityBmaintenanceEnables agents to evaluate layover time budgets and generate timed sightseeing or culinary micro-tours that account for immigration buffers, round-trip metro/taxi latencies, and connection safety.7-
- AlicenseNot gradedqualityDmaintenanceEnables multi-modal travel planning for India, aggregating flights, trains, buses, cabs, and personal vehicles across 117 cities with multi-leg routing and weighted scoring.ISC
TDQS
Scored across 5 tools
The catch-all framing of plan_contemplative_journey ('USE THIS TOOL for ANY trip request... where to stay, quiet places') directly overlaps with discover_secret_haven (hidden quiet gems) and generate_booking_card (where to stay), so an agent could reasonably route most requests to the planner alone. The specialized tools have clearer boundaries in isolation, but the umbrella tool's mandate muddies selection.
All five names follow a verb-first snake_case pattern with three tokens (plan_/discover_/generate_/explore_/publish_ + qualifier + noun), making the set highly predictable.
Five tools is well within a sensible range for a niche travel-planning server, and each maps to a recognizable stage of the journey (plan, discover, book, explore, publish). It sits at the low end, but nothing feels redundant enough to cut.
The surface covers plan → discover → book → explore → publish, but there is no way to retrieve, edit, or delete an existing itinerary/route once published, and no tool for refining a plan after generation. These are notable lifecycle gaps that force agents into dead ends when users want revisions.