Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Ocean acoustics: propagation models, bathymetry, sound speed, vessel noise, live AIS. Open.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://www.clairwave.com/mcpRun this in your terminal
claude mcp add --transport http clairwave https://www.clairwave.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"clairwave": {
"url": "https://www.clairwave.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"clairwave": {
"type": "http",
"url": "https://www.clairwave.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://www.clairwave.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account clairwave, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Dechonet MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
An open MCP server that gives AI assistants physically grounded ocean acoustics.
Clairwave runs validated propagation models (Bellhop, RAM/parabolic equation) on global bathymetry and seasonal sound-speed profiles, tracks live AIS vessels, and serves 3D hull models for them (shipshape). This server exposes that to Claude, ChatGPT, Gemini and any other MCP client — so an assistant reasoning about the ocean can *run the physics* instead of guessing.
Every result carries provenance (model, data source, run_id) and an open_url that opens the exact result in the platform. Simulation results include the bathymetry, sound-speed profile and bottom parameters that were used, so a researcher can replicate the run in MATLAB, Python or anything else.
Endpoint (no auth, no key): https://www.clairwave.com/mcp — Streamable HTTP.
claude mcp add --transport http clairwave https://www.clairwave.com/mcp| Tool | What it does |
|---|---|
get_bathymetry | Depth at a point, or a transect profile along a bearing |
get_sound_speed_profile | Seasonal c(z) for a month + seabed parameters (cp, cs, density, attenuation, sediment) |
run_transmission_loss | RAM parabolic-equation TL along a bearing; bathymetry/SSP/seabed fetched automatically; replication bundle included |
estimate_detection_range | Sonar equation on a RAM run: continuous and furthest detection range, signal excess vs range |
run_bellhop_volume | 3D Bellhop TL volume stored under a run id (uint8 cube + JSON sidecar links) |
vessel_source_level | Ship radiated noise: broadband + third-octave spectrum + mechanism breakdown |
search_vessels / vessels_near | Live AIS by name/MMSI, or within a radius of a point |
get_vessel | Live position/track, particulars, and the 3D model (GLB, bow=+Z) with platform links |
get_vessel_photo | Wikimedia Commons photo with attribution |
resolve_place | Place name (port, strait, sea, 'off Halifax') → water coordinates; gazetteer + OpenStreetMap, snapped seaward off land |
habitat_received_level | Power-summed vessel noise at a fixed site (fish farm, reef, hydrophone): live snapshot or 10-minute history series; top contributors |
about | Models, data sources, limits |
Typical latency against the live platform: bathymetry 0.5 s, SSP 6 s first time per 0.1° cell then cached, RAM transmission loss 1–3 s, detection range 1–3 s.
pip install "mcp[cli]<2" httpx
python server.py # streamable HTTP on :8890 (/mcp) python server.py --stdio # stdio for local clients python tests/smoke_client.py
Environment: CLAIRWAVE_API, CLAIRWAVE_FLEET, CLAIRWAVE_SITE, MCP_PORT.
io.github.clairwave/clairwave (https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.clairwave/clairwave)https://www.clairwave.com/mcp, no auth.{"type": "mcp", "server_url": "https://www.clairwave.com/mcp", "server_label": "clairwave"}.Every location tool takes either lat/lon or a place string. Names go through a maritime gazetteer first (ports resolve to their approaches, straits and seas to a representative water point; ~120 entries in gazetteer.py), then OpenStreetMap Nominatim. If the point is on land or shallower than 10 m it is walked seaward until it is deep enough, and the response's location block reports the original point, the snap distance and bearing, and the depth used. resolve_place exposes the same logic directly, with offshore_km to push a point further out.
MIT. Data: AIS via the AISHub peer network (Clairwave contributes receivers); vessel photos CC-licensed with attribution; bathymetry and SSP sources cited in each response.