Clairwave MCP Server

by clairwave Your server? Claim it

answering

Clairwave is answering right now. Last checked 8 min ago. It exposes 13 tools. Last commit 27 Sep 2026.

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

Uptime history 67 days of history · worst day 93%

67 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

117 ms

Response time

average over 24h

Stars

last commit 27 Sep 2026

What changed 20

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 4 September 2026. No other catalogue keeps this.

4 Sep 7 tool descriptions were rewritten12 times that day estimate_detection_range, get_bathymetry, get_sound_speed_profile and 4 more

4 Sep 6 tools changed the parameters they ask for estimate_detection_range, get_bathymetry, get_sound_speed_profile and 3 more

4 Sep 2 tools appeared habitat_received_level, resolve_place

and 5 more, back to 4 September 2026

Nothing serious here today

Today is the operative word: we check Clairwave every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://www.clairwave.com/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

vessel

get_vessel

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.

get_vessel_photo

Photograph of a vessel from Wikimedia Commons, with attribution.

vessel_source_level

Radiated-noise source level of a ship (dB re 1 uPa @ 1 m): broadband, third-octave spectrum (ISO centres 10 Hz - 100 kHz) and the mechanism breakdown (cavitation, machinery, flow, blade-rate tonals), from Clairwave's class-based ship-noise model (cavitation spectrum + machinery + flow + tonals). Give an MMSI (live AIS particulars are used) or explicit type / speed / dimensions. The spectrum is usable directly as `sl_spectrum` input.

vessels

search_vessels

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

vessels_near

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.

about

about

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

bathymetry

get_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.

bellhop

run_bellhop_volume

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).

estimate

estimate_detection_range

Location: lat/lon or `place` name. Passive sonar detection range along a bearing: runs a RAM transmission loss simulation for the location/season and applies the sonar equation SE = SL - TL - NL (- DT) at the receiver depth. Returns the first range where detection is lost, the furthest range still detectable (convergence zones), and the excess-vs-range curve. Units: dB re 1 uPa (SL @1 m, NL in the analysis band).

habitat

habitat_received_level

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.

resolve

resolve_place

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.

sound

get_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.

transmission

run_transmission_loss

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.

Endpoints

URL	Transport	State	Latency	Checked
https://www.clairwave.com/mcp	streamable-http	needs auth	116 ms	8 min ago

Alternatives to Clairwave

same job, measured the same way

Datalastic

by pipeworx-io

Datalastic MCP — live AIS vessel positions (datalastic.com)

135 installs/wk 46 tools answering

Open Waters AIS

by openwaters

Live AIS vessel positions by MMSI, name, area, or radius, plus coverage. No sign-in, no key.

6 tools answering

Notematics

by notematics

Maths lessons on an online whiteboard: solutions, worksheets, graphs and geometry, opened by a link

6 tools answering

Synap

by linkrra

Open AI models through one OpenAI-compatible API: chat, live model list, prices and cost estimates.

4 tools answering

Ionis MCP

by qso-graph

HF propagation analytics. 175M WSPR/RBN signatures, band openings, solar correlation.

856 installs/wk local only

Ionis MCP

by ionis-ai

HF propagation analytics. 175M WSPR/RBN signatures, band openings, solar correlation.

local only

OceanToken

by oceantoken

500+ AI models in one account: find and price models, make images, video, speech and text.

answering

Digitraffic Ais

by pipeworx-io

Digitraffic AIS MCP — live vessel positions in Finnish and Baltic Sea waters.

294 installs/wk 47 tools answering

Clairwave — questions

Answers built from our own checks of this server.

What can Clairwave do?

It exposes 13 tools, read directly from the server on our last check. Among them: about, estimate_detection_range, get_bathymetry, get_sound_speed_profile, get_vessel, get_vessel_photo and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Clairwave mostly used for?

Its tools cluster around vessel and vessels. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Clairwave working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 117 ms. The bar chart above shows every period we have measured.

How do I connect Clairwave?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Clairwave need an API key?

Yes. Every time we knock, Clairwave answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Clairwave?

It answers our handshake in 117 ms on average, which is faster than 89% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Clairwave open source?

We cannot say either way: written in Python and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.