Clairwave
REMOTE · WWW.CLAIRWAVE.COM · SCANNED OCT 3
Ocean acoustics: propagation models, bathymetry, sound speed, vessel noise, live AIS. Open.
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 Security74
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability58
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
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.
remote · www.clairwave.com
claude mcp add --transport http clairwave-clairwave 'https://www.clairwave.com/mcp'
{
"mcpServers": {
"clairwave-clairwave": {
"url": "https://www.clairwave.com/mcp"
}
}
} {
"servers": {
"clairwave-clairwave": {
"type": "http",
"url": "https://www.clairwave.com/mcp"
}
}
} [mcp_servers.clairwave-clairwave] url = "https://www.clairwave.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"clairwave-clairwave": {
"type": "remote",
"url": "https://www.clairwave.com/mcp",
"enabled": true
}
}
} openclaw mcp add clairwave-clairwave --url 'https://www.clairwave.com/mcp' --transport streamable-http
mcp_servers:
clairwave-clairwave:
url: "https://www.clairwave.com/mcp" {
"McpServers": {
"clairwave-clairwave": {
"Transport": "http",
"Url": "https://www.clairwave.com/mcp"
}
}
} assistant mcp add clairwave-clairwave -t streamable-http -u 'https://www.clairwave.com/mcp'
{
"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.
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.
- 2 Oct 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.
- 30 Sept 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.
- 28 Sept 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
- 27 Sept 26 +1
- 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 security
- “vessel_source_level” added an optional parameter “vessel_class” cosmetic
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −1
- Tool “estimate_detection_range” rewrote its description, which is the text the model reads security
- Schema quality: 140 → 180 ▼ functional
- “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) cosmetic
- 23 Sept 26 +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.
- 21 Sept 26 +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.
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 3 Oct 2026 · Probed https://www.clairwave.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=clairwave.com | CN=WE1,O=Google Trust Services,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 82bb6d5e8e86983e0e9634744a63056c |
| SANs: clairwave.com, *.clairwave.com | ||||||
| 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 www.clairwave.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| clairwave.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.clairwave.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.clairwave.com/mcp | HTTPS enforced | 301 | https://www.clairwave.com/mcp |
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 →
about About Clairwave ~22
What Clairwave provides, which models/data back each tool, and limits.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| limits | – | – | – |
| models | – | – | – |
| open_source | – | – | – |
| platform | – | – | – |
| reproducibility | – | – | – |
No examples provided.
estimate_detection_range Detection range (sonar equation, passive or active) ~760
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…
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – | – |
No examples provided.
get_bathymetry Bathymetry ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bearing_deg | – | – | – |
| lat | – | – | – |
| lon | – | – | – |
| n_points | integer | – | – |
| place | – | – | – |
| range_km | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| bearing_deg | – | – | – |
| depth_m | – | – | – |
| lat | – | – | – |
| location | – | – | – |
| lon | – | – | – |
| max_depth_m | – | – | – |
| min_depth_m | – | – | – |
| profile | – | – | – |
| provenance | – | – | – |
| range_km | – | – | – |
No examples provided.
get_sound_speed_profile Sound speed profile ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | – | – | – |
| lon | – | – | – |
| month | integer | yes | – |
| place | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| bottom | – | – | – |
| bottom_params_raw | – | – | – |
| files | – | – | – |
| lat | – | – | – |
| location | – | – | – |
| lon | – | – | – |
| max_depth_m | – | – | – |
| month | – | – | – |
| open_url | – | – | – |
| open_url_note | – | – | – |
| provenance | – | – | – |
| run_id | – | – | – |
| ssp | – | – | – |
No examples provided.
get_vessel Vessel details + 3D model ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mmsi | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| fleet_url | – | – | – |
| live | – | – | – |
| mmsi | – | – | – |
| model | – | – | – |
| model_glb_url | – | – | – |
| open_url | – | – | – |
| open_url_note | – | – | – |
| provenance | – | – | – |
| track_recent | – | – | – |
No examples provided.
get_vessel_photo Vessel photo ~38
Photograph of a vessel from Wikimedia Commons, with attribution.
| Name | Type | Req | Description |
|---|---|---|---|
| imo | – | – | – |
| mmsi | – | – | – |
| name | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | – | – | – |
| page | – | – | – |
| provenance | – | – | – |
| source | – | – | – |
| status | – | – | – |
| thumb | – | – | – |
| transient | – | – | – |
No examples provided.
habitat_received_level Habitat received level (vessel noise) ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hours_back | number | – | – |
| lat | – | – | – |
| lon | – | – | – |
| max_range_km | number | – | – |
| place | – | – | – |
| top | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – | – |
No examples provided.
resolve_place Resolve place name ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| min_depth_m | number | – | – |
| offshore_km | – | – | – |
| place | string | yes | – |
| seaward_bearing_deg | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| depth_m | – | – | – |
| lat | – | – | – |
| lon | – | – | – |
| matched | – | – | – |
| offshore_km | – | – | – |
| original | – | – | – |
| provenance | – | – | – |
| query | – | – | – |
| seaward_bearing_deg | – | – | – |
| snap | – | – | – |
| snapped_to_water | – | – | – |
| source | – | – | – |
No examples provided.
run_bellhop_volume Bellhop 3D TL volume (stored run) ~172
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).
| Name | Type | Req | Description |
|---|---|---|---|
| frequency_hz | number | – | – |
| lat | – | – | – |
| lon | – | – | – |
| month | integer | – | – |
| place | – | – | – |
| radius_km | number | – | – |
| source_depth_m | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| decode | – | – | – |
| files | – | – | – |
| location | – | – | – |
| metadata | – | – | – |
| open_url | – | – | – |
| open_url_note | – | – | – |
| provenance | – | – | – |
| run_id | – | – | – |
| ssp | – | – | – |
No examples provided.
run_transmission_loss Transmission loss (RAM PE) ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bearing_deg | number | yes | – |
| frequency_hz | number | yes | – |
| lat | – | – | – |
| lon | – | – | – |
| month | integer | – | – |
| place | – | – | – |
| range_km | number | – | – |
| receiver_depths_m | – | – | – |
| source_depth_m | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| grid | – | – | – |
| inputs | – | – | – |
| location | – | – | – |
| method | – | – | – |
| open_url | – | – | – |
| open_url_note | – | – | – |
| provenance | – | – | – |
| replication | – | – | – |
| solver_meta | – | – | – |
| stats | – | – | – |
| tl_vs_range | – | – | – |
No examples provided.
search_vessels Search vessels (AIS) ~38
Search live AIS vessels by name or MMSI prefix (global feed).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| provenance | – | – | – |
| results | – | – | – |
No examples provided.
vessel_source_level Vessel source level ~267
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| beam_m | – | – | – |
| draft_m | – | – | – |
| length_m | – | – | – |
| mmsi | – | – | – |
| ship_type | – | – | – |
| speed_kn | – | – | – |
| vessel_class | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – | – |
No examples provided.
vessels_near Vessels near a point (AIS) ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | – | – | – |
| limit | integer | – | – |
| lon | – | – | – |
| place | – | – | – |
| radius_km | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| center | – | – | – |
| count | – | – | – |
| location | – | – | – |
| note | – | – | – |
| provenance | – | – | – |
| radius_km | – | – | – |
| radius_used_km | – | – | – |
| vessels | – | – | – |
No examples provided.
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.