fr.ohmywind/sailing-planner · v1.9.0 · location-and-travel
OhMyWind is healthy: it completed an MCP handshake in 1821 ms and exposes 4 tools.
Sailing passage planner for any coast, with high-precision tides on the French Atlantic.
Endpoint: https://mcp.ohmywind.fr/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 4 |
| Latency | 1821 ms |
| Last checked (UTC) | 2026-10-16T03:00:15.278Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T03:00:15.278Z | Healthy | 1821 | |
| 2026-10-15T00:00:42.746Z | Healthy | 4237 | |
| 2026-10-15T00:00:42.727Z | Healthy | 3617 |
read_me | Return OhMyWind's calculation methodology as Markdown. Call this when the user asks how passage timing, complexity, or boat speed are computed (e.g. "comment c'est calculé ?", "what assumptions does the model use?", "is tacking modelled?"). The returned text covers: |
list_boat_archetypes | List the boat archetypes with descriptive metadata. The LLM (or user) maps a commercial model (e.g. "Sun Odyssey 32") to one of these archetypes from the metadata — there is no server-side mapping. ``voile_aviron_16ft`` is for open sail-and-oar dinghies only (no cabin, |
get_marine_forecast | Fetch wind (and sea, when available) for a point and time window. Args: lat: latitude in degrees. lon: longitude in degrees. start: ISO-8601 datetime, timezone-aware (e.g. "2026-05-01T06:00:00+00:00"). end: ISO-8601 datetime, timezone-aware. |
plan_passage | Plan an A→B passage. Compare departure windows by default; pin a single departure only when the user gives an explicit time. ## Tool routing: read this first Before calling, classify the user's question: 1. **Pure weather lookup at a point** ("y aura-t-il du vent à |