onvaou-itineraires-mcp
OfficialRelated Servers
Alternatives to onvaou-itineraires-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables planning bike routes using the BRouter engine, with support for waypoints, route profiles, and exporting routes as GPX or other formats.5-
- AlicenseNot gradedqualityCmaintenanceAI-powered route optimization MCP server for heavy vehicles and logistics. Calculate truck-optimized routes, predict traffic congestion with LSTM neural networks, compute toll costs, fuel costs and CO2 emissions, find truck stops and check weather along any European route.MIT
- AlicenseAqualityCmaintenanceEnables comparing door-to-door travel times by bicycle, motorbike, and public transport alongside local weather, and provides place lookup and API usage tracking.4Apache 2.0
- AlicenseAqualityDmaintenanceMCP server for planning routes (hiking, biking, driving, etc.) using the OpenRouteService API. Provides tools to find coordinates, create routes with GPX/PNG/HTML output, search POIs, and compute reachable areas.637 PyPI2MIT
- AlicenseNot gradedqualityAmaintenanceBikeScout is a specialized MCP (Model Context Protocol) server designed for cyclists and mountain bikers. It provides intelligent trail recommendations by combining real-world map data with advanced routing analysis.20AGPL 3.0

ThinAir Geoofficial
AlicenseAqualityCmaintenanceLocation & routing intelligence for AI agents — geocoding, truck routing, traffic, weather, and place search.161929 npm1MIT
TDQS
Scored across 1 tool
With only one tool, there is no ambiguity; the tool's purpose is clearly defined and distinct from any potential peers.
The single tool name 'compute_route' follows a clear verb_noun pattern and is descriptive, though there are no other tools to compare against.
A single tool feels insufficient for a routing service, especially since the description references geocoding as a prerequisite, which is not provided. A typical server would include at least geocoding and route management tools.
The server only covers route computation, but the workflow implies a need for geocoding (to get coordinates) and possibly route saving or sharing, which are absent. This creates a significant dead-end for agents.