# OhMyWind (remote · mcp.ohmywind.fr)

Sailing passage planner for any coast, with high-precision tides on the French Atlantic.

- Trust score: 55/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.ohmywind.fr`: 55/100 (this document), [markdown](https://verifymcp.io/servers/fr-ohmywind-sailing-planner/mcp.md), [page](https://verifymcp.io/servers/fr-ohmywind-sailing-planner/mcp)

## Channel facts

- Endpoint: `https://mcp.ohmywind.fr/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2350 tokens (~470/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http fr-ohmywind-sailing-planner https://mcp.ohmywind.fr/mcp
```

### Codex

```toml
[mcp_servers.fr-ohmywind-sailing-planner]
url = "https://mcp.ohmywind.fr/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fr-ohmywind-sailing-planner": {
      "type": "remote",
      "url": "https://mcp.ohmywind.fr/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fr-ohmywind-sailing-planner --url https://mcp.ohmywind.fr/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fr-ohmywind-sailing-planner:
    url: "https://mcp.ohmywind.fr/mcp"
```

### Other

```json
{
  "mcpServers": {
    "fr-ohmywind-sailing-planner": {
      "type": "http",
      "url": "https://mcp.ohmywind.fr/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 55, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-01 (score 54)

First indexed and scored.

## MCP tools (4)

### `read_me` (~129 tokens)

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: polar lookup, default efficiency 0.75,
        VMG / tacking correction, wave derate, single-pass timing,
        compare-windows mode semantics, Mediterranean simplifications
        (tides, currents), and what is intentionally NOT modelled in V1.

Output parameters:

- `result` (string)

### `list_boat_archetypes` (~65 tokens)

List the 7 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.

Output parameters:

- `result` (array)

### `get_marine_forecast` (~157 tokens)

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.
            models: optional list of model names; defaults to AROME for the Med.

        Note: the first request after inactivity may incur ~5s of cold-start.

Input parameters:

- `end` (string, required)
- `lat` (number, required)
- `lon` (number, required)
- `models`
- `start` (string, required)

### `plan_passage` (~1871 tokens)

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 à Cassis
           samedi à 14h ?", "quelles vagues dimanche au cap Sicié ?") — call
           ``get_marine_forecast`` and answer in text. Do NOT call
           ``plan_passage``: there's no route to plan.

        2. **Trajet question with a flexible date** ("Marseille → Porquerolles
           ce week-end", "demain ou après-demain", "dans les prochains jours")
           — call ``plan_passage`` in **compare-windows mode**: pass
           ``latest_departure`` (e.g. earliest+48h) and ``sweep_interval_hours``
           (3 or 6 typically) so the user sees several departure scenarios
           side-by-side. Then pick 2-3 good ones and let the user choose.
           This is the **default** for trajet planning — same API cost as a
           single passage thanks to cache prewarm, much more value.

        3. **Trajet with a precise hour pinned by the user** ("je pars demain
           à 8h", "départ Saturday 9am") — call ``plan_passage`` in single
           mode (no ``latest_departure``). Used for the final "show me the
           detailed plan for THIS departure" view, often after step 2.

        4. **Methodology question** ("comment c'est calculé ?",
           "quelle efficacité par défaut ?") — call ``read_me``.

        Rule of thumb: if the user does NOT give an exact hour, prefer
        compare-windows. The widget renders one of the windows by default
        and the chat lets the user pick another.

        ## Returned payload

        Single mode:

        - ``passage``: per-segment timing report (distance_nm, duration_h,
          model used, segments[] with TWS/TWA/boat_speed/Hs, warnings).
        - ``complexity``: 1-5 difficulty score with wind/sea brea…

Input parameters:

- `archetype` (string, required)
- `departure` (string, required)
- `efficiency` (number)
- `latest_departure`
- `max_hs_m`
- `model` (string)
- `motor_speed_kn`
- `motor_threshold_kn`
- `segment_length_nm` (number)
- `sweep_interval_hours` (integer)
- `target_eta`
- `waypoints` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fr-ohmywind-sailing-planner/mcp#diagnostics

## Score history

- 2026-08-03: 55
- 2026-08-02: 55
- 2026-08-01: 54

## Links

- Remote endpoint: https://mcp.ohmywind.fr/mcp
- Repository: https://github.com/qdonnars/ohmywind
- Website: https://ohmywind.fr/
- Changelog RSS feed: https://verifymcp.io/servers/fr-ohmywind-sailing-planner/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/fr-ohmywind-sailing-planner/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/fr-ohmywind-sailing-planner/mcp