Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Nausika

REMOTE · MCP.NAUSIKA.APP

Mediterranean marine, nautical, sailing: forecasts, tides, sea routes, anchorages, POIs for AI.

Available components

0 this week 82 Trust /100

Last scanned (18 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security66
Transport & Reachability100
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5719 tokens (~301/item across 19 items; 19 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • 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 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 28 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 13 Oct 26 0
    • “nausika_search_places” reworded the description of “type” cosmetic
    • “nausika_search_places” reworded the description of “types” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 12 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “nausika_geocode” rewrote its description, which is the text the model reads security
    • Tool “nausika_sea_route” rewrote its description, which is the text the model reads security
    • Tool “nausika_search_places” rewrote its description, which is the text the model reads security
    • Tool “nausika_seasonal_forecast” rewrote its description, which is the text the model reads security
  • 4 Oct 26 0
    • Tool “nausika_geocode” rewrote its description, which is the text the model reads security
    • “nausika_geocode” added an optional parameter “near_latitude” cosmetic
    • “nausika_geocode” added an optional parameter “near_longitude” cosmetic
  • 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
Diagnostics

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 21 Nov 2026 · Probed https://mcp.nausika.app

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=nausika.app CN=YE1,O=Let's Encrypt,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA384 6011fd9439c5b97be06e340ab5b9e2dfe1b
SANs: *.nausika.app, nausika.app
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.nausika.app. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
nausika.app. DS published 2371 13 Verified
mcp.nausika.app. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; img-src 'self' data: blob: https://*.tile.openstreetmap.org https://*.openstreetmap.org https://*.basemaps.cartocdn.com https://api.mapbox.com https://server.arcgisonline.com https://tiles.openseamap.org https://*.googleusercontent.com https://avatars.githubusercontent.com; style-src 'self' 'unsafe-inline' https://unpkg.com; font-src 'self' data:; script-src 'self' 'unsafe-inline' https://unpkg.com; connect-src 'self' ws: wss: https://unpkg.com; worker-src 'self' blob:; frame-ancestors 'self'; base-uri 'self'; form-action 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.nausika.app Verified 200
http (plaintext) http://mcp.nausika.app HTTPS enforced 301 https://mcp.nausika.app/
MCP tools · 19 exposed · ~5,353 tokens

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 →

Tool Tokens
nausika_calculator ~176

Evaluate a math expression and return the numeric result. Useful for fuel, range/autonomy, unit conversions, and ad-hoc arithmetic. Supported (exhaustive): +, -, *, /, ^, %, parentheses, sqrt(), abs(), ceil(), floor(), round(), sin(), cos(), tan(), log(), exp(), min(), max(), PI, E. Anything else (atan2, pow, log10, hypot, if, factorial, comparisons) is rejected. Examples: "(120 / 6) * 8.5" (fuel for 120 nm at 8.5 L/h, 6 kn); "45 * 1.852" (nm to km).

NameTypeReqDescription
expressionstringyesMath expression to evaluate
precisioninteger–Decimal places in the result (default 4)
NameTypeReqDescription
expressionstringyes–
precisionintegeryes–
resultnumberyes–

No examples provided.

nausika_convert_coordinates ~164

Convert nautical coordinates between decimal degrees, DMS, and DM. Inputs: latitude, longitude — each accepts decimal (44.4), DMS ("44°24'00\"N"), or DM ("44°24.0'N"). Returns all three formats plus input_format (detected per-axis). Examples: latitude="44°24'N", longitude="9°02'E" → 44.4, 9.03; latitude="41°01'44.04\"N", longitude="009°32'42.00\"E" → 41.0289, 9.545.

NameTypeReqDescription
latitude–yesLatitude as decimal degrees or DMS/DM string
longitude–yesLongitude as decimal degrees or DMS/DM string
NameTypeReqDescription
decimalobjectyes–
dmobjectyes–
dmsobjectyes–
input_formatobjectyes–

No examples provided.

nausika_describe_place_schema ~86

Returns the expected attributes for a given place 'type' (the only input parameter: marina, port, bay, fuel_station, city, island, etc.). Useful to understand what fields are available on places of that type.

NameTypeReqDescription
typestringyesPlace type to describe. See nausika_describe_place_schema response 'Valid place types' for the full enum.
NameTypeReqDescription
agentRuleNotesobjectyes–
agentRulesarrayyes–
attributesarrayyes–
imageFieldsarrayyes–
imageRulesobjectyes–
promotedColumnsarrayyes–
requestedTypestringyes–
typestringyes–
universalRulesarrayyes–

No examples provided.

nausika_geocode ~384

Resolve a place 'query' to coordinates (forward) or find nearest places to 'latitude'+'longitude' (reverse). Curated DB of the covered sea areas (Mediterranean, European Atlantic + Canaries, Caribbean, South-East Asia); forward falls back to OSM/Nominatim globally. Each result carries a 'source' discriminator ('local' for the curated marine DB, 'osm' for the global fallback). Returns name, type, coords, source, plus similarity (forward) or distance_m (reverse). Example forward: query="Portofino". Example reverse: latitude=44.3, longitude=9.21, radius_m=50000. When the same name exists in several seas (e.g. "Salerno port": Italy and Florida), results carry a 'region' and the best of each sea is included — pick by the user's context, or pass near_latitude/near_longitude (boat position, departure port) to put that sea first. Chain into nausika_marine_forecast, nausika_tides, nausika_search_places, or nausika_sea_route using the returned coords.

NameTypeReqDescription
latitudenumber–Latitude for reverse geocoding
limitinteger–Max results, default 3, max 10
longitudenumber–Longitude for reverse geocoding
near_latitudenumber–Optional, forward only: latitude of where the user is (boat position, port of departure). When the same name exists in several seas, results from that sea come first.
near_longitudenumber–Optional, forward only: longitude paired with near_latitude.
querystring–Place name to search, forward geocoding
radius_minteger–Search radius for reverse geocoding in meters, default 50000
NameTypeReqDescription
_attributionarrayyes–
countnumberyes–
latitudenumber––
longitudenumber––
modestringyes–
querystring––
resultsarrayyes–
sourcestring––

No examples provided.

nausika_get_boat_profile ~84

Get your saved boat profile(s). Omit name for the default boat, or use name="*" to list all boats. Tip: use boat speed/consumption with nausika_sea_route and nausika_calculator for trip planning.

NameTypeReqDescription
namestring–Boat name. Omit to get the default boat, or use '*' to list all.
NameTypeReqDescription
boatsarray––
foundboolean––
idstring––
is_defaultboolean––
namestring––
typestring––

No examples provided.

nausika_get_favorites ~78

List your favorite places with details and personal notes. Ordered by most recently added. Inputs: limit, offset. Tip: use place coordinates with nausika_sea_route or nausika_marine_forecast for trip planning.

NameTypeReqDescription
limitinteger–Max results (default 20)
offsetinteger–Offset for pagination
NameTypeReqDescription
favoritesarrayyes–
limitintegeryes–
offsetintegeryes–

No examples provided.

nausika_get_place ~162

Fetch full detail for a single place given its 'id'. Accepts either a full UUID or the 8-char [xxxxxxxx] short-id shown by nausika_search_places. Returns canonical attributes (name/coords/category/type), localized i18n names+descriptions, wiki image URLs, ratings aggregates, plus extras only this tool provides: the raw OpenStreetMap tags of the primary OSM feature, and direct links to OSM, Wikidata, and Wikipedia. Use this after nausika_search_places returns a result you want to drill into. For proximity / text search, use nausika_search_places.

NameTypeReqDescription
idstringyesPlace id — full UUID or 8+ char hex prefix (the [xxxxxxxx] shown by nausika_search_places).
NameTypeReqDescription
_attributionarrayyes–
avg_rating–yes–
bottom_typearray––
categorystringyes–
coverage_scorenumberyes–
data_origin_unverifiedboolean––
descriptionstring––
distance_kmnumber––
elevation_m–––
emailstring––
i18nobject––
idstringyes–
imagesarrayyes–
is_favoritedboolean––
latitudenumberyes–
linksobjectyes–
longitudenumberyes–
max_loa_m–––
namestringyes–
name_canonicalstring––
opening_hoursstring––
osm_primary_id–––
osm_primary_type–––
own_rating–––
phonestring––
port_of_entry–––
rating_countnumberyes–
raw_osm_tags–yes–
shelter_fromarray––
sourcesarrayyes–
typestringyes–
vhf_channelstring––
websitestring––
wiki_imagesarrayyes–
wikidata_id–––
wikipedia–––

No examples provided.

nausika_get_ratings ~154

View ratings for a place (aggregate + your own) or list all your ratings. Inputs: place_id, my_only, limit, offset. Examples: - Place ratings: place_id="a1b2c3d4" (8-char short-id or full UUID) - My ratings: my_only=true Tip: ratings are visible in nausika_search_places results to help other sailors.

NameTypeReqDescription
limitinteger–Max results
my_onlyboolean–List only your own ratings
offsetinteger–Offset for pagination
place_idstring–Get ratings for a specific place — full UUID or 8+ char hex prefix from nausika_search_places
NameTypeReqDescription
aggregateobject––
limitinteger––
my_rating–––
offsetinteger––
ratingsarray––

No examples provided.

nausika_get_routes ~214

Look up your saved sailing-route library: direct fetch by id, or paginated search by name fragment via query, with limit and offset for pagination. Examples: - List all (defaults limit=20, offset=0): (no params) - Detail by id: id="a1b2c3d4" (8-char short-id or full UUID) - Search: query="Corsica", limit=10, offset=0 - Only itineraries: route_type="itinerary" Tip: feed leg coordinates into nausika_marine_forecast or nausika_tides to check conditions along the route.

NameTypeReqDescription
idstring–Fetch single route — full UUID or 8+ char hex prefix from nausika_get_routes
limitinteger–Max results, 1–50
offsetinteger–Offset for pagination
querystring–Search by name fragment, case-insensitive
route_typestring–Filter by type
NameTypeReqDescription
idstring––
legsarray––
limitinteger––
namestring––
offsetinteger––
route_typestring––
routesarray––

No examples provided.

nausika_is_water ~154

Check whether a coordinate (latitude, longitude in decimal degrees) is on water or land, and how far it is from the coast. Returns: - is_water: boolean (true if over sea, false if over land) - distance_to_coast_m: meters to the nearest coastline boundary; meaningful on either side (sea → distance to shore, inland → distance to sea, e.g. Rome ≈ 25 km). - source: detection source Useful to verify waypoints in route planning, or to gauge how coastal/inland a point is.

NameTypeReqDescription
latitudenumberyesLatitude in decimal degrees (-90 to 90)
longitudenumberyesLongitude in decimal degrees (-180 to 180)
NameTypeReqDescription
_attributionarrayyes–
distance_to_coast_mnumberyes–
is_waterbooleanyes–
latitudenumberyes–
longitudenumberyes–
sourcestringyes–

No examples provided.

nausika_manage_boat_profile ~358

Manage boat profile (multi-boat per account, keyed by name). Inputs: action, name, type, loa_m, beam_m, draft_m, displacement_kg, engine_type, engine_hp, fuel_capacity_l, motor_consumption_l_per_h, water_capacity_l, cruising_speed_kts, max_speed_kts, safety_equipment, certifications. Examples: action="upsert", name="Freya", type="sail", loa_m=12.5; action="delete", name="Freya"; action="set_default", name="Freya". Tip: speed/consumption enrich nausika_sea_route ETA.

NameTypeReqDescription
actionstringyesCreate/update, delete, or set a boat as default
beam_mnumber–Maximum beam in meters
certificationsstring–Certifications
cruising_speed_ktsnumber–Cruising speed in knots
displacement_kginteger–Displacement in kg
draft_mnumber–Draft in meters
engine_hpinteger–Engine power in HP
engine_typestring–Engine type
fuel_capacity_linteger–Fuel tank capacity in liters
loa_mnumber–Length overall in meters
max_speed_ktsnumber–Maximum speed in knots
motor_consumption_l_per_hnumber–Average motor fuel consumption at cruising RPM, in litres per hour
namestring–Boat name (required for create, identifies boat for update/delete)
safety_equipmentstring–Safety equipment description
typestring–Boat type
water_capacity_linteger–Water tank capacity in liters
NameTypeReqDescription
actionstringyes–
idstring––
namestring––

No examples provided.

nausika_manage_favorite ~160

Add or remove a place from your favorites list. Examples: - Add: action="add", place_id="a1b2c3d4", note="Great anchorage for overnight" - Remove: action="remove", place_id="a1b2c3d4" place_id accepts the 8-char [xxxxxxxx] shown by nausika_search_places, or a full UUID. Find places first with nausika_search_places, then bookmark by place_id.

NameTypeReqDescription
actionstringyesAdd or remove a favorite
notestring–Personal note (only for add)
place_idstringyesPlace id — full UUID or 8+ char hex prefix from nausika_search_places ([xxxxxxxx])
NameTypeReqDescription
actionstringyes–
created_atstring––
idstring––
note–––
place–––
place_idstringyes–
user_idstring––

No examples provided.

nausika_manage_rating ~192

Rate a place (1-5 stars) with an optional private comment. One rating per user per place. Examples: - Rate: action="upsert", place_id="a1b2c3d4", score=4, comment="Clean facilities" - Delete: action="delete", place_id="a1b2c3d4" place_id accepts the 8-char [xxxxxxxx] shown by nausika_search_places, or a full UUID. Find places first with nausika_search_places, then rate by place_id.

NameTypeReqDescription
actionstringyesCreate/update or delete your rating
commentstring–Private comment (only visible to you)
place_idstringyesPlace id — full UUID or 8+ char hex prefix from nausika_search_places ([xxxxxxxx])
scoreinteger–Rating 1-5 (required for upsert)
NameTypeReqDescription
actionstringyes–
aggregateobject––
place_idstringyes–
ratingobject––

No examples provided.

nausika_manage_route ~262

Save a sailing route or multi-day itinerary; legs may link to places. Typical flow: compute legs with nausika_sea_route, then save here. Examples: - Single: action="upsert", name="Genova → Bastia", route_type="single", legs=[{...}] - Itinerary: action="upsert", name="Corsica Trip", route_type="itinerary", legs=[{leg_order:1,...,pois:[{place_id:"a1b2c3d4",role:"overnight"}]}] - Delete: action="delete", id="a1b2c3d4" id and leg pois[].place_id accept either the 8-char [xxxxxxxx] short-id (from nausika_get_routes / nausika_search_places) or a full UUID.

NameTypeReqDescription
actionstringyesCreate/update or delete
descriptionstring–Route description
idstring–Route id for update/delete — full UUID or 8+ char hex prefix from nausika_get_routes
legsarray–Route legs, replaces all existing on update
namestring–Route name
route_typestring–single leg or multi-leg itinerary
NameTypeReqDescription
actionstring––
idstring––

No examples provided.

nausika_marine_forecast ~899

Marine + atmospheric forecast at (latitude, longitude in decimal degrees). Returns waves, swell, currents, SST, wind, gusts, pressure, weather_code, visibility, precipitation, temperature, UV. Directions FROM. Presets: now, today, tactical (default 3d), planning (8d), extended (14d), none. Windows: start_hour/end_hour, start_date/end_date, forecast_hours, forecast_days. Extra via variables[]. Covers only a rolling window near today (~16 days ahead for atmospheric data, ~8 days for marine/wave data) — for dates further out, use nausika_seasonal_forecast (1-7 month outlook) instead. Pass include_percentiles=true to also fetch the ECMWF IFS-ENS 50-member ensemble and expose <var>_p10/_p50/_p90 series for atmospheric variables (precipitation, wind, gusts, pressure, temperature, etc.) alongside the deterministic forecast. Use it when forecast uncertainty matters — convective setups, planning/extended horizons, or any time the deterministic precip total looks inconsistent with the precipitation_probability. Waves/swell/currents/SST remain deterministic (no public ensemble). Default false to keep payload small. Example: latitude=41.39, longitude=9.16, preset="today". Chain nausika_geocode for place→coords.

NameTypeReqDescription
end_datestring–Window end date YYYY-MM-DD. Used with start_date. Defaults to preset. Same ~16-day (forecast) / ~8-day (marine) window limit as start_date — use nausika_seasonal_forecast beyond that.
end_hourstring–Window end ISO YYYY-MM-DDThh:mm. Used with start_hour. Defaults to preset.
forecast_daysinteger–Override preset days (1-16). Forecast endpoint caps at 16, Marine at 8. Defaults to preset.
forecast_hoursinteger–Override with an hourly window. Wins over forecast_days. Defaults to preset.
include_percentilesboolean–When true, ALSO fetch the Open-Meteo ECMWF IFS-ENS ensemble (50 perturbed members) and expose `<var>_p10/_p50/_p90` percentile series alongside the deterministic forecast for atmospheric variables (p…
latitudenumberyesLatitude in decimal degrees (WGS84, -90 to 90)
longitudenumberyesLongitude in decimal degrees (WGS84, -180 to 180)
presetstring–High-level mode. now=current snapshot, today=24h hourly+daily, tactical=3d hourly_3+daily (default), planning=8d daily, extended=14d daily, none=3d hourly_3+daily but with NO core variables (caller s…
start_datestring–Window start date YYYY-MM-DD. Used with end_date. Wins over forecast_hours/forecast_days. Defaults to preset. Must fall within the rolling forecast window (~16 days ahead for atmospheric data, ~8 day…
start_hourstring–Window start ISO YYYY-MM-DDThh:mm. Used with end_hour. Most specific override (wins over date and hour-count windows). Defaults to preset.
temporal_resolutionstring–Override hourly granularity. hourly_1=every hour, hourly_3=every 3h, hourly_6=every 6h. Defaults to the preset's resolution.
variablesarray–Extra variables added to the preset core (additive). Each is routed to its endpoint automatically. Required (non-empty) when preset='none'. Examples: swell_wave_height/swell_wave_direction/swell_wave…
NameTypeReqDescription
_attributionarray––
_disclaimerstring––
coordinates_requestedobjectyes–
currentobject––
dailyobject––
forecast_resolved–yes–
forecast_unavailable_reason–yes–
hourlyobject––
marine_resolved–yes–
marine_unavailable_reason–yes–
presetstringyes–
timezonestringyes–
unitsobjectyes–

No examples provided.

nausika_sea_route ~421

Maritime routing via pgRouting Dijkstra on the MARNET sea-lane graph (detailed coastal routing in the curated areas — Mediterranean, European Atlantic + Canaries, Caribbean, South-East Asia; main ocean lanes elsewhere; errors when an endpoint is far from any lane), 6 kn sailing-yacht default, snaps land coordinates to the nearest marina/anchorage/port. Returns distance, ETA, waypoint count, GeoJSON. Examples: - Genova → Bastia: origin_lat=44.4, origin_lon=8.93, dest_lat=42.7, dest_lon=9.45 - Distance-only: same coords with include_waypoints=false Tip: chain nausika_geocode → here → nausika_calculator.

NameTypeReqDescription
dest_latnumberyesDestination latitude
dest_lonnumberyesDestination longitude
include_waypointsboolean–Set to false for distance-only mode (no waypoints or GeoJSON)
optimizationstring–Waypoint smoothing level. 'fast' (default): light smoothing, milliseconds. 'precise': highest-quality smoothing, slower (up to a few seconds). 'off': raw waypoints, unsmoothed.
origin_latnumberyesOrigin latitude
origin_lonnumberyesOrigin longitude
snap_to_waterboolean–If origin or destination falls on land (e.g. a city centroid from nausika_geocode like Lisbon → 38.71, -9.14), automatically snap to the nearest known marine place (marina, anchorage, port) within a…
speed_knotsnumber–Vessel speed in knots for ETA calculation. Omit to use the caller's saved boat profile speed if one exists, else 6 kn (typical sailing yacht). An explicit value always wins over the boat profile.
unitsstring–Distance units (default: nauticalmiles)
NameTypeReqDescription
_attributionarrayyes–
_disclaimerstring––
dest_snap_distance_nm–––
dest_snap_nmnumber––
dest_snapped_fromobject––
dest_snapped_toobject––
destinationobjectyes–
direct_distance_nmnumber––
distancenumberyes–
estimated_duration_hoursnumberyes–
optimizationstring––
optimization_failedboolean––
optimization_usedstring––
originobjectyes–
origin_snap_distance_nm–––
origin_snap_nmnumber––
origin_snapped_fromobject––
origin_snapped_toobject––
route_geojsonobject––
shorter_than_directboolean––
snap_warningboolean––
speed_knotsnumberyes–
unitsstringyes–
waypoints_countnumber––

No examples provided.

nausika_search_places ~556

Nautical place search by proximity in the curated areas (Mediterranean, European Atlantic + Canaries, Caribbean, South-East Asia). latitude+longitude are ALWAYS required — this is not a standalone text search. 'query' is only a name filter applied within that radius; to find a place by name without known coordinates, call nausika_geocode first. Returns name, coords, distance_km, ratings, i18n names, wiki/OSM links. Each result is prefixed with an 8-char [xxxxxxxx] short-id usable as place_id in nausika_get_place / nausika_manage_favorite / nausika_manage_rating / nausika_manage_route legs[].pois[]. Inputs: latitude, longitude, radius_km, query, type, types, category, shelter_from, bottom_type, names_lang, min_coverage_score, max_coverage_score, limit, offset. Example: latitude=44.3, longitude=9.21, radius_km=50, query="marina genova", category="poi". Chain nausika_geocode → nausika_search_places → nausika_get_place(short-id).

NameTypeReqDescription
bottom_typestring–Bottom type filter (e.g. 'sand')
categorystring–Filter by category
latitudenumber–Center latitude for proximity search
limitinteger–Max results, default 30, max 100
longitudenumber–Center longitude for proximity search
max_coverage_scoreinteger–Maximum coverage score 0-100 — filter to low-coverage places that need enrichment
min_coverage_scoreinteger–Minimum coverage score 0-100 — filter places by data completeness
names_langstring–ISO 639-1 lang code. When set, response `name` is replaced with attributes.i18n.names[lang] if present; canonical OSM name kept as `name_canonical`.
offsetinteger–Offset for pagination
querystring–Fuzzy text filter on place name, applied WITHIN the proximity search — requires latitude/longitude too, it is not a standalone text search. For 'find this place by name anywhere', use nausika_geocode…
radius_kmnumber–Search radius in km (default 50, max 200)
shelter_fromstring–Compass direction to filter shelter (e.g. 'NW')
typestring–Filter by place type (ignored if 'types' is provided). Anchorages are type 'bay'.
typesarray–Filter by multiple place types (takes precedence over 'type'). Anchorages are type 'bay'.
NameTypeReqDescription
_attributionarrayyes–
centerobjectyes–
countnumberyes–
placesarrayyes–
radius_kmnumberyes–

No examples provided.

nausika_seasonal_forecast ~435

Fetch 1-7 month ECMWF SEAS5 seasonal forecast for one point, anywhere in the world. Returns ensemble-mean DAILY + MONTHLY aggregates of wind, SST, temperature, precipitation, cloud cover (extend via variables[]). NO waves — chain nausika_marine_forecast for short-term wind + waves. Inputs: latitude, longitude, start_date, end_date, variables. Example: latitude=40.12, longitude=9.01, start_date="2026-08-01", end_date="2026-08-31". SEAS5 forecasts forward only: a start_date in the past is clamped to today and an end_date beyond today+210d is clamped to the horizon, both reported in the response. A window that ends in the past is rejected.

NameTypeReqDescription
end_datestringyesWindow end date (UTC, ISO YYYY-MM-DD). Must be ≥ start_date. Dates beyond the SEAS5 horizon (today + 210 days) are clamped — the response reports the adjustment.
include_membersboolean–When true, expose all 50 ECMWF SEAS5 ensemble members (`<var>_memberNN`) in the response. Default (false) collapses them into `_p10/_p50/_p90` percentile series alongside the ensemble mean — ~20× sma…
latitudenumberyesLatitude in decimal degrees (WGS84, -90 to 90)
longitudenumberyesLongitude in decimal degrees (WGS84, -180 to 180)
start_datestringyesWindow start date (UTC, ISO YYYY-MM-DD). Dates before today are clamped to today (SEAS5 forecasts forward only) — the response reports the adjustment.
variablesarray–Additional variables, additive to the core set (wind_speed_10m, wind_direction_10m, sea_surface_temperature, temperature_2m, precipitation, cloud_cover). Each is expanded server-side into the appropr…
NameTypeReqDescription
_attributionarray––
_disclaimerstring––
coordinates_requestedobjectyes–
coordinates_resolvedobjectyes–
dailyobjectyes–
modelstringyes–
monthlyobjectyes–
monthly_derivedboolean––
rangeobjectyes–
timezonestringyes–
unitsobjectyes–
window_adjustedstring––

No examples provided.

nausika_tides ~414

Tide predictions or station discovery at a coordinate (latitude, longitude). Default: predictions from the nearest NOAA station; outside US waters falls back to a global modeled-tide source (forecast horizon ~15 days — longer windows are truncated, not rejected). Set stations_only=true to discover stations (capped by limit). Tune the window with begin_date (YYYYMMDD) + range_hours, the reference with datum, and output units (metric/english). The modeled path reports range_m (peak-to-trough). Across most of the Mediterranean this is under 0.3 m, i.e. negligible for recreational navigation — the response says so explicitly, and you should not present such values as an actionable tide window. Tides matter on the Atlantic coasts, in the Gulf of Gabès, the northern Adriatic, and in the tidal streams of the Messina and Gibraltar straits. Example: latitude=37.77, longitude=-122.42. Chain nausika_geocode for place→coordinates; pair with nausika_marine_forecast.

NameTypeReqDescription
begin_datestring–Start date in YYYYMMDD format (defaults to today UTC).
datumstring–Tidal datum reference (default MLLW)
intervalstring–Interval: 'hilo' for high/low only (default), 'h' for hourly predictions
latitudenumberyesLatitude in decimal degrees (WGS84, -90 to 90)
limitinteger–Max stations to return in stations_only mode (default 5, max 10).
longitudenumberyesLongitude in decimal degrees (WGS84, -180 to 180)
range_hoursinteger–Duration in hours (default 48, max 744 = ~31 days).
stations_onlyboolean–If true, return nearby stations without fetching predictions (station discovery mode). Defaults to false.
unitsstring–Units: metric (meters) or english (feet)
NameTypeReqDescription
_attributionarrayyes–
_disclaimerstring––
centerobject––
countnumberyes–
data_sourcestring––
datumstring––
intervalstring––
locationobject––
modestringyes–
modelobject––
notestring––
predictionsarray––
range_mnumber––
stationobject––
stationsarray––
unitsstring––

No examples provided.

Install

How do I install the Nausika MCP server?

Nausika is a hosted endpoint at https://mcp.nausika.app/, 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 · mcp.nausika.app

# add to Claude Code
claude mcp add --transport http app-nausika-mcp 'https://mcp.nausika.app/'
Common questions

What is the Nausika MCP server?

Nausika is an MCP server listed in the public MCP registry as app.nausika/mcp. Mediterranean marine, nautical, sailing: forecasts, tides, sea routes, anchorages, POIs for AI. This page covers its hosted endpoint (https://mcp.nausika.app).

Is the Nausika MCP server safe to use?

Nausika scores 82 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 Nausika MCP server expose?

Nausika exposes 19 tools: nausika_marine_forecast, nausika_seasonal_forecast, nausika_tides, nausika_search_places, nausika_get_place, and 14 more. Their descriptions and schemas cost roughly 5,353 tokens of context every time the server is loaded.

Does the Nausika MCP server require authentication?

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

Is the Nausika MCP server still maintained?

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

What did VerifyMCP test on the Nausika MCP server?

VerifyMCP ran 13 checks on Nausika, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.