OhMyWind
REMOTE · MCP.OHMYWIND.FR · SCANNED SEP 24
Sailing passage planner for any coast, with high-precision tides on the French Atlantic.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3080 tokens (~616/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the OhMyWind MCP server?
OhMyWind is a hosted endpoint at https://mcp.ohmywind.fr/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.ohmywind.fr
claude mcp add --transport http fr-ohmywind-sailing-planner 'https://mcp.ohmywind.fr/mcp'
{
"mcpServers": {
"fr-ohmywind-sailing-planner": {
"url": "https://mcp.ohmywind.fr/mcp"
}
}
} {
"servers": {
"fr-ohmywind-sailing-planner": {
"type": "http",
"url": "https://mcp.ohmywind.fr/mcp"
}
}
} [mcp_servers.fr-ohmywind-sailing-planner] url = "https://mcp.ohmywind.fr/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fr-ohmywind-sailing-planner": {
"type": "remote",
"url": "https://mcp.ohmywind.fr/mcp",
"enabled": true
}
}
} openclaw mcp add fr-ohmywind-sailing-planner --url 'https://mcp.ohmywind.fr/mcp' --transport streamable-http
mcp_servers:
fr-ohmywind-sailing-planner:
url: "https://mcp.ohmywind.fr/mcp" {
"McpServers": {
"fr-ohmywind-sailing-planner": {
"Transport": "http",
"Url": "https://mcp.ohmywind.fr/mcp"
}
}
} assistant mcp add fr-ohmywind-sailing-planner -t streamable-http -u 'https://mcp.ohmywind.fr/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 −1
- Tool “plan_passage” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- 31 Aug 26 +1
- Stability: 0.97 → pass security
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +6
- Authorization: unverified → partial ▲ security
- Tool “get_marine_forecast” rewrote its description, which is the text the model reads security
- Tool “plan_passage” rewrote its description, which is the text the model reads security
- Schema quality: 483 → 603 ▼ functional
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 69
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Aug 26 0
- Tool “plan_passage” rewrote its description, which is the text the model reads security
- “plan_passage” added an optional parameter “min_upwind_twa_deg” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://mcp.ohmywind.fr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ohmywind.fr | CN=WE1,O=Google Trust Services,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a929a515319d4941137306fb065771ab |
| SANs: ohmywind.fr, *.ohmywind.fr | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.ohmywind.fr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | present | 65381 | 13 | Verified |
| ohmywind.fr. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | frame-ancestors 'self' https://huggingface.co https://*.hf.space |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.ohmywind.fr/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.ohmywind.fr/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_marine_forecast ~202
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. Pass a point at sea. Over land Open-Meteo still returns wind, but every sea value comes back null, so the ``sea`` array is present and empty of information rather than absent. Note: the first request after inactivity may incur ~5s of cold-start.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | – |
| lat | number | yes | – |
| lon | number | yes | – |
| models | – | – | – |
| start | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_boat_archetypes ~65
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
plan_passage ~2,556
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**, passing ``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. ## Waypoints must stay in the water This server does no land check. It samples wind and sea along the polyline you pass, then reports distance, ETA and complexity for that polyline, whatever it crosses. A leg drawn through a peninsul…
| Name | Type | Req | Description |
|---|---|---|---|
| archetype | string | yes | – |
| departure | string | yes | – |
| efficiency | number | – | – |
| latest_departure | – | – | – |
| max_hs_m | – | – | – |
| min_upwind_twa_deg | – | – | – |
| model | string | – | – |
| motor_speed_kn | – | – | – |
| motor_threshold_kn | – | – | – |
| segment_length_nm | number | – | – |
| sweep_interval_hours | integer | – | – |
| target_eta | – | – | – |
| waypoints | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
read_me ~129
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the OhMyWind MCP server?
OhMyWind is an MCP server listed in the public MCP registry as fr.ohmywind/sailing-planner. Sailing passage planner for any coast, with high-precision tides on the French Atlantic. This page covers its hosted endpoint (https://mcp.ohmywind.fr/mcp).
Is the OhMyWind MCP server safe to use?
OhMyWind scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the OhMyWind MCP server expose?
OhMyWind exposes 4 tools: read_me, list_boat_archetypes, get_marine_forecast, plan_passage. Their descriptions and schemas cost roughly 2,952 tokens of context every time the server is loaded.
Does the OhMyWind MCP server require authentication?
No. We connected to OhMyWind without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the OhMyWind MCP server still maintained?
OhMyWind is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.