# Clairwave (remote · www.clairwave.com)

Ocean acoustics: propagation models, bathymetry, sound speed, vessel noise, live AIS. Open.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `www.clairwave.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/clairwave-clairwave/www.md), [page](https://verifymcp.io/servers/clairwave-clairwave/www)

## Channel facts

- Endpoint: `https://www.clairwave.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.0`

## 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-10-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2473 tokens (~190/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Clairwave MCP server?

Clairwave is a hosted endpoint at https://www.clairwave.com/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.

### Claude

```bash
claude mcp add --transport http clairwave-clairwave 'https://www.clairwave.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "clairwave-clairwave": {
      "url": "https://www.clairwave.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "clairwave-clairwave": {
      "type": "http",
      "url": "https://www.clairwave.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.clairwave-clairwave]
url = "https://www.clairwave.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "clairwave-clairwave": {
      "type": "remote",
      "url": "https://www.clairwave.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add clairwave-clairwave --url 'https://www.clairwave.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  clairwave-clairwave:
    url: "https://www.clairwave.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "clairwave-clairwave": {
      "Transport": "http",
      "Url": "https://www.clairwave.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add clairwave-clairwave -t streamable-http -u 'https://www.clairwave.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "clairwave-clairwave": {
      "type": "http",
      "url": "https://www.clairwave.com/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-10-02 (score 79, +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.

### 2026-09-30 (score 78, +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.

### 2026-09-28 (score 77, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 77, +1)

- [security] Tool “estimate_detection_range” rewrote its description, which is the text the model reads
- [security] Tool “vessel_source_level” rewrote its description, which is the text the model reads
- [cosmetic] “vessel_source_level” added an optional parameter “vessel_class”

### 2026-09-25 (score 76, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 75, −1)

- [security] Tool “estimate_detection_range” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 140 → 180
- [cosmetic] “estimate_detection_range” added an optional parameter “bandwidth_hz”
- [cosmetic] “estimate_detection_range” added an optional parameter “directivity_index_db”
- [cosmetic] “estimate_detection_range” added an optional parameter “integration_time_s”
- [cosmetic] “estimate_detection_range” added an optional parameter “mode”
- [cosmetic] “estimate_detection_range” added an optional parameter “pd”
- [cosmetic] “estimate_detection_range” added an optional parameter “pfa”
- [cosmetic] “estimate_detection_range” added an optional parameter “pulse_length_s”
- [cosmetic] “estimate_detection_range” added an optional parameter “target_depth_m”
- [cosmetic] “estimate_detection_range” added an optional parameter “target_strength_db”
- [cosmetic] “estimate_detection_range” made “frequency_hz” optional
- [cosmetic] “estimate_detection_range” made “noise_level_db” optional
- [cosmetic] “estimate_detection_range” made “receiver_depth_m” optional
- [cosmetic] “estimate_detection_range” made “source_depth_m” optional
- [cosmetic] “estimate_detection_range” made “source_level_db” optional
- [cosmetic] Tool “estimate_detection_range” changed its title: Detection range (sonar equation) → Detection range (sonar equation, passive or active)

### 2026-09-23 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (13)

### `resolve_place` (~178 tokens)

Resolve place name

Turn a place name ('outside Halifax', 'Strait of Hormuz', 'Bergen,
    Norway') into water coordinates. Maritime gazetteer first (ports resolve
    to their approaches, straits/seas to a representative point), then
    OpenStreetMap. Points on land or shallower than min_depth_m are walked
    seaward along the gazetteer bearing (or the nearest direction) until deep
    enough; the original point and the snap are reported. offshore_km pushes
    the point further out along seaward_bearing_deg. All location tools also
    accept `place` directly, so a separate call is only needed to inspect.

Input parameters:

- `min_depth_m` (number)
- `offshore_km`
- `place` (string, required)
- `seaward_bearing_deg`

Output parameters:

- `depth_m`
- `lat`
- `lon`
- `matched`
- `offshore_km`
- `original`
- `provenance`
- `query`
- `seaward_bearing_deg`
- `snap`
- `snapped_to_water`
- `source`

### `get_bathymetry` (~128 tokens)

Bathymetry

Seafloor depth from Clairwave-served global bathymetry (~450 m resolution). Location:
    lat/lon or `place` (name resolved to a water point, echoed in `location`).
    Without a bearing: depth at the point. With a bearing (compass degrees,
    0 = north): a depth profile along that transect out to range_km.

Input parameters:

- `bearing_deg`
- `lat`
- `lon`
- `n_points` (integer)
- `place`
- `range_km` (number)

Output parameters:

- `bearing_deg`
- `depth_m`
- `lat`
- `location`
- `lon`
- `max_depth_m`
- `min_depth_m`
- `profile`
- `provenance`
- `range_km`

### `get_sound_speed_profile` (~121 tokens)

Sound speed profile

Seasonal sound-speed profile c(z) at a location (lat/lon or `place`
    name, e.g. "Halifax approaches") for a calendar month
    (1-12), from Clairwave-served seasonal temperature/salinity climatology, plus the seabed
    parameters (compressional/shear speed, density ratio, attenuation,
    sediment type) at the same point. Cached per 0.1 degree.

Input parameters:

- `lat`
- `lon`
- `month` (integer, required)
- `place`

Output parameters:

- `bottom`
- `bottom_params_raw`
- `files`
- `lat`
- `location`
- `lon`
- `max_depth_m`
- `month`
- `open_url`
- `open_url_note`
- `provenance`
- `run_id`
- `ssp`

### `run_transmission_loss` (~187 tokens)

Transmission loss (RAM PE)

Run a physically grounded transmission-loss simulation (RAM parabolic
    equation) from a source at (lat, lon or `place`, depth) along a compass bearing.
    Bathymetry, the seasonal sound-speed profile (`month`) and
    seabed parameters are fetched for the location automatically. Returns TL
    vs range at the receiver depths (default: source depth, 10 m, 100 m,
    mid-water), grid statistics, and the full replication bundle. Show
    `open_url` to the user as a clickable link.

Input parameters:

- `bearing_deg` (number, required)
- `frequency_hz` (number, required)
- `lat`
- `lon`
- `month` (integer)
- `place`
- `range_km` (number)
- `receiver_depths_m`
- `source_depth_m` (number, required)

Output parameters:

- `grid`
- `inputs`
- `location`
- `method`
- `open_url`
- `open_url_note`
- `provenance`
- `replication`
- `solver_meta`
- `stats`
- `tl_vs_range`

### `estimate_detection_range` (~760 tokens)

Detection range (sonar equation, passive or active)

Sonar detection range along a bearing from a location (lat/lon or `place`).
    Transmission loss (TL) is ALWAYS computed: RAM parabolic equation with the
    location's bathymetry, seasonal sound speed (`month`, default: current month)
    and seabed. Every other sonar-equation term is optional — anything not given
    gets a stated, typical default listed in `assumptions` with its source.
    Tell the user which values were assumed.

    Detection threshold DT is derived from processing gain (unless given):
    detection index d from `pd`/`pfa` (default 0.5 / 1e-4 → d ≈ 13.8), then
      passive (incoherent energy detector): DT = 5·log10(d / (B·T)),
        B = analysis band, T = `integration_time_s` (default 1 s);
      active (matched filter): DT = 10·log10(d / (2·B·τ)),
        B = `bandwidth_hz` (default 100 Hz LFM), τ = `pulse_length_s` (default 0.5 s).
    DT is in-band SNR, so it can be negative — that IS the processing gain.

    mode="passive": SE = SL − TL − (NL − DI) − DT. Default target = merchant ship
      (bulk carrier, AIS 70, 200 m @ 12 kn, JOMOPANS-ECHO decidecade band level) at
      6 m; receiver ½ water depth (≤ 30 m), omni (DI 0 — give directivity_index_db
      for an array). `frequency_hz` is optional: the tool always also evaluates
      the target's MOST DETECTABLE 1/3-octave band in 50–2000 Hz (`best_band`) —
      ships are loudest there; a user frequency is reported as asked. If you give
      `source_level_db` without `frequency_hz`, the range is evaluated at 50 Hz.
    mode="active" (monostatic, `frequency_hz` required): SE = SL − 2·TL + TS −
      (NL − DI) − DT, TL from the sonar to the target depth. Defaults: hull sonar
      at 7 m, SL 220 dB, TS 10 dB (submarine-sized, beam aspect), target ½ water
      depth (≤ 50 m), DI 20 dB (hull array). Noise-limited only: reverberation is
      NOT included (often the limit in shallow water).
    NL (unless given) = Wenz ambient noise at the CURRENT forecast wind at the point
    (Clairwa…

Input parameters:

- `bandwidth_hz`
- `bearing_deg` (number)
- `detection_threshold_db`
- `directivity_index_db`
- `frequency_hz`
- `integration_time_s`
- `lat`
- `lon`
- `max_range_km`
- `mode` (string)
- `month`
- `noise_level_db`
- `pd` (number)
- `pfa` (number)
- `place`
- `pulse_length_s`
- `receiver_depth_m`
- `source_depth_m`
- `source_level_db`
- `target_depth_m`
- `target_strength_db`

Output parameters:

- `assumptions`
- `bearing_deg`
- `best_band`
- `caveats`
- `continuous_detection_range_km`
- `detectable_fraction_of_track`
- `detection_threshold_db`
- `environment_run_id`
- `furthest_detectable_range_km`
- `inputs`
- `limited_by_max_range`
- `location`
- `method`
- `mode`
- `noise_level_db`
- `open_url`
- `open_url_note`
- `provenance`
- `receiver_below_seafloor_fraction`
- `replication`
- `se_db`
- `signal_excess_vs_range`
- `sonar_equation`
- `source_level_db`

### `run_bellhop_volume` (~172 tokens)

Bellhop 3D TL volume (stored run)

Full 3D transmission-loss volume around a source (lat/lon or `place`)
    with Bellhop (all bearings), stored on the platform under a run id. Show
    `open_url` to the user as a clickable link: it opens this run visualized. Returns the run id,
    the replication metadata (SSP, seabed, bounding box) and file links
    (uint8 TL cube .npy + JSON sidecar). Any frequency and radius (keep radius
    <= ~50 km for reasonable run times).

Input parameters:

- `frequency_hz` (number)
- `lat`
- `lon`
- `month` (integer)
- `place`
- `radius_km` (number)
- `source_depth_m` (number)

Output parameters:

- `decode`
- `files`
- `location`
- `metadata`
- `open_url`
- `open_url_note`
- `provenance`
- `run_id`
- `ssp`

### `search_vessels` (~38 tokens)

Search vessels (AIS)

Search live AIS vessels by name or MMSI prefix (global feed).

Input parameters:

- `limit` (integer)
- `query` (string, required)

Output parameters:

- `provenance`
- `results`

### `vessels_near` (~79 tokens)

Vessels near a point (AIS)

Live AIS vessels within radius_km of a point (lat/lon or `place`), nearest first, with
    position, course/speed, type, dimensions and last-update time.

Input parameters:

- `lat`
- `limit` (integer)
- `lon`
- `place`
- `radius_km` (number)

Output parameters:

- `center`
- `count`
- `location`
- `note`
- `provenance`
- `radius_km`
- `radius_used_km`
- `vessels`

### `get_vessel` (~74 tokens)

Vessel details + 3D model

Everything about one vessel: live AIS position/track and static
    particulars, plus its 3D model (unique photo-derived model if generated,
    else the class archetype) with GLB URL (bow=+Z, up=+Y) and platform links.

Input parameters:

- `mmsi` (string, required)

Output parameters:

- `fleet_url`
- `live`
- `mmsi`
- `model`
- `model_glb_url`
- `open_url`
- `open_url_note`
- `provenance`
- `track_recent`

### `vessel_source_level` (~267 tokens)

Vessel source level

Underwater radiated-noise source level of a ship (monopole, dB re 1 uPa m, 6 m
    reference source depth): decidecade spectrum (10 Hz - 100 kHz; model bands to
    31.5 kHz, validated 20 Hz - 20 kHz) and broadband level, from the JOMOPANS-ECHO
    reference spectrum model (MacGillivray & de Jong 2021, J. Mar. Sci. Eng. 9:369),
    fitted to 1862 measured ship passes. Individual ships scatter about +/-6 dB rms per band.
    Give an MMSI (live AIS type/speed/length are used) or explicit AIS ship_type / speed /
    length. vessel_class overrides the AIS mapping (e.g. "vehicle_carrier", which has no
    AIS type). Missing speed = the class reference speed; missing length = the class
    mean length of the measured ships. The spectrum is usable directly as `sl_spectrum`.

Input parameters:

- `beam_m`
- `draft_m`
- `length_m`
- `mmsi`
- `ship_type`
- `speed_kn`
- `vessel_class`

Output parameters:

- `beam_m`
- `broadband_band_hz`
- `broadband_sl_db`
- `effective_params`
- `inputs`
- `model`
- `note`
- `notes`
- `provenance`
- `reference_source_depth_m`
- `reference_speed_kn`
- `ship_class`
- `spectrum`
- `spectrum_integrated_sl_db`
- `uncertainty_db`
- `units`
- `validated_band_hz`
- `vessel_class`

### `get_vessel_photo` (~38 tokens)

Vessel photo

Photograph of a vessel from Wikimedia Commons, with attribution.

Input parameters:

- `imo`
- `mmsi`
- `name`

Output parameters:

- `attribution`
- `page`
- `provenance`
- `source`
- `status`
- `thumb`
- `transient`

### `habitat_received_level` (~196 tokens)

Habitat received level (vessel noise)

Broadband received level (dB re 1 uPa) at a fixed site — a fish farm,
    reef, hydrophone or marine protected area — from the ships around it,
    power-summed. Each vessel's source level comes from its AIS class, speed
    and size; transmission loss is a fast broadband model, so this is a
    screening estimate (use run_transmission_loss for exact site physics).
    hours_back = 0 uses the live snapshot; > 0 reconstructs a time series from
    the AIS archive in 10-minute bins (max/median/quiet levels). Location:
    lat/lon or `place`. Show `open_url` to the user as a clickable link.

Input parameters:

- `hours_back` (number)
- `lat`
- `lon`
- `max_range_km` (number)
- `place`
- `top` (integer)

Output parameters:

- `bins_10min`
- `contributors`
- `hours_back`
- `location`
- `max_range_km`
- `method`
- `mode`
- `n_vessels_in_range`
- `open_url`
- `open_url_note`
- `provenance`
- `received_level_db`
- `series`
- `site`
- `stats`
- `vessels_seen`

### `about` (~22 tokens)

About Clairwave

What Clairwave provides, which models/data back each tool, and limits.

Output parameters:

- `data`
- `limits`
- `models`
- `open_source`
- `platform`
- `reproducibility`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/clairwave-clairwave/www#diagnostics

## Score history

- 2026-10-03: 79
- 2026-10-02: 79
- 2026-10-01: 78
- 2026-09-30: 78
- 2026-09-29: 77
- 2026-09-28: 77
- 2026-09-27: 77
- 2026-09-26: 76
- 2026-09-25: 76
- 2026-09-24: 75
- 2026-09-23: 76
- 2026-09-22: 75
- 2026-09-21: 75
- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 74
- 2026-09-17: 73
- 2026-09-16: 73
- 2026-09-15: 72
- 2026-09-14: 72
- 2026-09-13: 71
- 2026-09-12: 71
- 2026-09-11: 70
- 2026-09-10: 70
- 2026-09-09: 69
- 2026-09-08: 69
- 2026-09-07: 68
- 2026-09-06: 68
- 2026-09-05: 67
- 2026-09-04: 67

## Common questions

### What is the Clairwave MCP server?

Clairwave is an MCP server listed in the public MCP registry as io.github.clairwave/clairwave. Ocean acoustics: propagation models, bathymetry, sound speed, vessel noise, live AIS. Open. This page covers its hosted endpoint (https://www.clairwave.com/mcp).

### Is the Clairwave MCP server safe to use?

Clairwave scores 79 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 Clairwave MCP server expose?

Clairwave exposes 13 tools: resolve_place, get_bathymetry, get_sound_speed_profile, run_transmission_loss, estimate_detection_range, and 8 more. Their descriptions and schemas cost roughly 2,260 tokens of context every time the server is loaded.

### Does the Clairwave MCP server require authentication?

No. We connected to Clairwave without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Clairwave MCP server still maintained?

Clairwave is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.clairwave.com/mcp
- Repository: https://github.com/clairwave/clairwave-mcp
- Website: https://www.clairwave.com/
- Changelog RSS feed: https://verifymcp.io/servers/clairwave-clairwave/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/clairwave-clairwave/www.json
- HTML version of this page: https://verifymcp.io/servers/clairwave-clairwave/www