nausika
Marine, maritime, nautical and sailing data for AI assistants and chatbots. Mediterranean marine forecast: wind, wave, swell, gust. Tide tables and tidal predictions. Sea routing and passage planning on a coastline-aware maritime graph. Curated POIs: marinas, ports, harbors, anchorages, moorings, fuel. Real data, cited sources, never invented.
https://nausika--nausika.run.tools
How to connect
-
Smithery (hosted)
1. Open https://smithery.ai/servers/nausika/nausika 2. Click Connect and complete OAuth in your MCP client (Claude, Cursor, VS Code, etc.) 3. MCP endpoint: https://nausika--nausika.run.tools
Tools (19)
-
nausika_marine_forecastMarine + atmospheric weather forecast for a coordinate (latitude, longitude in decimal degrees) at sea or on a coast. Provides marine variables (waves, swell, currents, SST, sea level) together with atmospheric variables (wind, gusts, pressure, weather code, visibility, precipitation, temperature, UV, sunrise/sunset). All directions are reported FROM in degrees and 16-sector compass labels in the text content. PRESETS (default = tactical): - now: current snapshot only. - today: 24h hourly_1 +
-
nausika_seasonal_forecastSeasonal weather outlook for a coordinate (latitude, longitude in decimal degrees), sourced from ECMWF SEAS5 (1–7 month horizon) via Open-Meteo. USE CASE: planning a sailing trip 1–7 months ahead — "what does August in Sardegna typically look like?" Returns ENSEMBLE-MEAN absolute values (NOT anomalies). For deterministic short-term (≤16 days) use nausika_marine_forecast instead. GRANULARITY: response carries both DAILY arrays (one entry per day in the requested range) and MONTHLY arrays (one e
-
nausika_tidesGet tide predictions or discover tide stations near any location. By default, finds the nearest station and returns tide predictions. Use stations_only: true to discover nearby stations without fetching predictions. Coverage: official tide stations cover US coasts and territories. Outside that area the tool falls back to a global modeled-tide source. Examples: - "Tides near San Francisco" -> latitude=37.77, longitude=-122.42 -> finds nearest station, returns predictions - "What tide statio
-
nausika_search_placesSearch for nautical places and points of interest by proximity. Supports text search, type/category filters, and promoted attribute filters (shelter, bottom type, coverage score). Coverage: the curated Nausika dataset focuses on the Mediterranean basin. Searches outside the Mediterranean typically return zero or sparse results until coverage is expanded upstream. Returns places with name, type, category, coordinates, distance, ratings, and relevant attributes including i18n names/descriptions,
-
nausika_get_placeFetch full detail for a single place by ID. 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.
-
nausika_sea_routeCalculate the maritime route between two points, avoiding land. Routes have enhanced precision near Nausika places (marinas, anchorages, etc.). Coverage: routing graph is centered on the Mediterranean basin and adjacent waters. Outside that area the tool returns an explicit error rather than a misleading partial result. Returns: Distance, estimated duration, and waypoint count. Full GeoJSON route available in structured output. Use include_waypoints: false for quick distance/duration without
-
nausika_calculatorEvaluate a math expression and return the numeric result. Useful for fuel consumption, range/autonomy estimates, unit conversions, and any ad-hoc arithmetic the user needs. Supported (exhaustive): +, -, *, /, ^, %, parentheses, sqrt(), abs(), ceil(), floor(), round(), sin(), cos(), tan(), log(), exp(), min(), max(), PI, E. Anything else (atan2, pow, log10, hypot, if, comparisons, factorial, …) is rejected. Examples: - "How much fuel for 120 nm at 8.5 L/h and 6 kn?" -> expression: "(120 / 6)
-
nausika_geocodeResolve place names to coordinates or find places near coordinates. Two modes: - Forward: provide 'query' to search by place name. Searches the curated marine database first; if no confident match, falls back to a global place-name source. - Reverse: provide 'latitude' + 'longitude' to find nearest curated places. Coverage: the curated database is Mediterranean-focused (marine POIs). The global fallback covers forward queries outside the Mediterranean. Reverse geocoding returns empty resul
-
nausika_describe_place_schemaReturns the expected attributes and their types for a given place type. Useful to understand what fields are available on places of a given type.
-
nausika_is_waterCheck 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.
-
nausika_convert_coordinatesConvert coordinates between decimal degrees, degrees-minutes-seconds (DMS), and degrees-decimal minutes (DM). Accepts any mix of formats as input and returns all three representations. Input formats: - Decimal: 41.0289 or "41.0289" - DMS: "41°01′44.04″N" or "41°01'44.04\"N" - DM: "41°01.7340′N" or "41°01.7340'N" Examples: - Decimal to DMS: latitude=41.0289, longitude=9.545 → 41°01′44.04″N, 009°32′42.00″E - DMS to decimal: latitude="41°01′44.04″N", longitude="009°32′42.00″E" → 41.028
-
nausika_manage_boat_profileCreate, update, delete, or set default boat profile. Multiple boats per account, identified by name. Examples: - Create: action="upsert", name="Freya", type="sail", loa_m=12.5, draft_m=1.8 - Update draft: action="upsert", name="Freya", draft_m=2.0 - Delete: action="delete", name="Freya" - Set default: action="set_default", name="Freya" Tip: saved boat parameters (speed, consumption) enrich nausika_sea_route duration estimates.
-
nausika_get_boat_profileGet 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.
-
nausika_manage_favoriteAdd or remove a place from your favorites list. Examples: - Add: action="add", place_id="<uuid>", note="Great anchorage for overnight" - Remove: action="remove", place_id="<uuid>" Tip: find places first with nausika_search_places, then bookmark by place_id.
-
nausika_get_favoritesList your favorite places with details and personal notes. Ordered by most recently added. Tip: use place coordinates with nausika_sea_route or nausika_marine_forecast for trip planning.
-
nausika_manage_ratingRate a place (1-5 stars) with an optional private comment. One rating per user per place. Examples: - Rate: action="upsert", place_id="<uuid>", score=4, comment="Clean facilities" - Delete: action="delete", place_id="<uuid>" Tip: find places first with nausika_search_places, then rate by place_id.
-
nausika_get_ratingsView ratings for a place (aggregate + your own) or list all your ratings. Examples: - Place ratings: place_id="<uuid>" - My ratings: my_only=true Tip: ratings are visible in nausika_search_places results to help other sailors.
-
nausika_manage_routeSave a route or compose a multi-day itinerary. A route has one or more legs, each optionally linked to places. Typical flow: calculate legs with nausika_sea_route, then save results here. Examples: - Save single route: action="upsert", name="Genova to Bastia", route_type="single", legs=[{...}] - Create itinerary: action="upsert", name="Corsica Trip", route_type="itinerary", legs=[{leg_order:1,...}, {leg_order:2,...}] - Delete: action="delete", id="<route-uuid>" Tip: calculate legs with
-
nausika_get_routesList and search your saved routes and itineraries. Examples: - List all: (no params) - Single route detail: id="<route-uuid>" - Only itineraries: route_type="itinerary" Tip: use leg coordinates with nausika_marine_forecast or nausika_tides to check conditions along the route.