Clairwave MCP server
io.github.clairwave/clairwaveclairwavestreamable-httpv0.4.0Scanned
Ocean acoustics: propagation models, bathymetry, sound speed, vessel noise, live AIS. Open.
13 tools: 7 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 13
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
7 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Clairwave MCP server can do
The Clairwave MCP server is published by the GitHub account clairwave. It has 13 tools. It can create or change data (7 tools: run_transmission_loss, estimate_detection_range, run_bellhop_volume, vessels_near and 3 more), but cannot delete data. 6 tools only read.
13 tools bring in text other people can write (resolve_place, get_bathymetry, get_sound_speed_profile and 10 more).
The fixed checks matched 2 findings (annotation-conflict and long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 0.4.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Changes things 7Claude Code: ask
aboutWhat Clairwave provides, which models/data back each tool, and limits.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it What Clairwave provides, which models/data back each tool, and limits.
Annotations the server declares
- title: About Clairwave
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
estimate_detection_rangeSonar detection range along a bearing from a location (lat/lon or `place`).Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,095 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...her), moderate shipping, in the analysis band. Units: dB re 1 µPa (SL @ 1 m)."
Description, as the server wrote it 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 (large underwater object, 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 (Clairwave weather), moderate shipping, in the analysis band. Units: dB re 1 µPa (SL @ 1 m).
Annotations the server declares
- title: Detection range (sonar equation, passive or active)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
habitat_received_levelBroadband 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.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Habitat received level (vessel noise)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
run_bellhop_volumeFull 3D transmission-loss volume around a source (lat/lon or `place`) with Bellhop (all bearings), stored on the platform under a run id.Reads text others writeNo findings
Why it is in this group
- The name "run_bellhop_volume" says "run": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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).
Annotations the server declares
- title: Bellhop 3D TL volume (stored run)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
run_transmission_lossRun a physically grounded transmission-loss simulation (RAM parabolic equation) from a source at (lat, lon or `place`, depth) along a compass bearing.Reads text others write1 finding
Why it is in this group
- The name "run_transmission_loss" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "run_transmission_loss" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "run_transmission_loss" says "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Transmission loss (RAM PE)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
vessel_source_levelUnderwater 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 …Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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`.
Annotations the server declares
- title: Vessel source level
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
vessels_nearLive AIS vessels within radius_km of a point (lat/lon or `place`), nearest first, with position, course/speed, type, dimensions and last-update time.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Vessels near a point (AIS)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 6Show 6 read-only tools
get_bathymetrySeafloor depth from Clairwave-served global bathymetry (~450 m resolution).Reads text others writeNo findings
Why it is in this group
- The name "get_bathymetry" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Bathymetry
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_sound_speed_profileSeasonal sound-speed profile c(z) at a location (lat/lon or `place` name, e.g.Reads text others writeNo findings
Why it is in this group
- The name "get_sound_speed_profile" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Sound speed profile
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_vesselEverything 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…Reads text others writeNo findings
Why it is in this group
- The name "get_vessel" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Vessel details + 3D model
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_vessel_photoPhotograph of a vessel from Wikimedia Commons, with attribution.Reads text others writeNo findings
Why it is in this group
- The name "get_vessel_photo" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Photograph of a vessel from Wikimedia Commons, with attribution.
Annotations the server declares
- title: Vessel photo
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
resolve_placeTurn a place name ('outside Halifax', 'Strait of Hormuz', 'Bergen, Norway') into water coordinates.Reads text others writeNo findings
Why it is in this group
- The name "resolve_place" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Resolve place name
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
search_vesselsSearch live AIS vessels by name or MMSI prefix (global feed).Reads text others writeNo findings
Why it is in this group
- The name "search_vessels" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Search live AIS vessels by name or MMSI prefix (global feed).
Annotations the server declares
- title: Search vessels (AIS)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write13
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:03 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.clairwave.com/mcp: tools/list returned 13 tools to an anonymous client, including run_transmission_loss (write), estimate_detection_range (write), run_bellhop_volume (write), vessels_near (write), vessel_source_level (write) and 2 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "run_transmission_loss" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "run_transmission_loss" says "run": a word for a change.
The description is 2,095 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...her), moderate shipping, in the analysis band. Units: dB re 1 µPa (SL @ 1 m)."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http clairwave https://www.clairwave.com/mcpclaude mcp add --transport http clairwave https://www.clairwave.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__clairwave__resolve_place",
"mcp__clairwave__get_bathymetry",
"mcp__clairwave__get_sound_speed_profile",
"mcp__clairwave__search_vessels",
"mcp__clairwave__get_vessel",
"mcp__clairwave__get_vessel_photo"
],
"ask": [
"mcp__clairwave__run_transmission_loss",
"mcp__clairwave__estimate_detection_range",
"mcp__clairwave__run_bellhop_volume",
"mcp__clairwave__vessels_near",
"mcp__clairwave__vessel_source_level",
"mcp__clairwave__habitat_received_level",
"mcp__clairwave__about"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as clairwave. Review it before you use it.
Capability tags behind 13 rules
- mcp__clairwave__resolve_place untrusted-input
- mcp__clairwave__get_bathymetry untrusted-input
- mcp__clairwave__get_sound_speed_profile untrusted-input
- mcp__clairwave__run_transmission_loss untrusted-input
- mcp__clairwave__estimate_detection_range untrusted-input
- mcp__clairwave__run_bellhop_volume untrusted-input
- mcp__clairwave__search_vessels untrusted-input
- mcp__clairwave__vessels_near untrusted-input
- mcp__clairwave__get_vessel untrusted-input
- mcp__clairwave__vessel_source_level untrusted-input
- mcp__clairwave__get_vessel_photo untrusted-input
- mcp__clairwave__habitat_received_level untrusted-input
- mcp__clairwave__about untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.clairwave/clairwave/verify?hash=e3178b3522092630680baba5d1b24e5c67c22fb5059aa85a91960ca18c4187d4" | jq -e '.changed == false'Pinned hash e3178b352209, from Nov 16, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.clairwave/clairwave/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.clairwave/clairwave)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:27 UTC.
Clairwave MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Clairwave MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 7 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Clairwave MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Clairwave MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Clairwave MCP server have?
- 13 tools: 7 write, 6 read. run_transmission_loss, estimate_detection_range, run_bellhop_volume, vessels_near, vessel_source_level, habitat_received_level, about, resolve_place and 5 more.
Does the Clairwave MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Clairwave MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Clairwave MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.