Nausika MCP server
app.nausika/mcpnausika.appstreamable-httpv0.1.3Scanned
Mediterranean marine, nautical, sailing: forecasts, tides, sea routes, anchorages, POIs for AI.
19 tools: 4 can delete or cancel things, 6 change things and 9 only read.
- Reads private data · 1
- Reads text others write · 4
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here can delete or cancel 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 Nausika MCP server can do
The Nausika MCP server is published by nausika.app, a domain the MCP Registry verified. It has 19 tools. It can delete or cancel things (4 tools: nausika_manage_boat_profile, nausika_manage_favorite, nausika_manage_rating and nausika_manage_route) and create or change data (6 tools: nausika_marine_forecast, nausika_tides, nausika_sea_route, nausika_calculator and 2 more). 9 tools only read.
1 tool reads private data (nausika_get_favorites); 4 tools bring in text other people can write (nausika_marine_forecast, nausika_seasonal_forecast, nausika_tides and 1 more).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 0.1.3.
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.
19 tools
Deletes or cancels 4Claude Code: deny
nausika_manage_boat_profileManage boat profile (multi-boat per account, keyed by name).No 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 destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
nausika_manage_favoriteAdd or remove a place from your favorites list.No findings
Why it is in this group
- The description's first verb is "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
nausika_manage_ratingRate a place (1-5 stars) with an optional private comment.No 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 destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
nausika_manage_routeSave a sailing route or multi-day itinerary; legs may link to places.No findings
Why it is in this group
- The description's first verb is "save": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Changes things 6Claude Code: ask
nausika_calculatorEvaluate a math expression and return the numeric result.1 finding
Why it is in this group
- The description's first verb is "evaluate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "nausika_calculator" 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":false}; The description's first verb is "evaluate": a word for a change.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nausika_convert_coordinatesConvert nautical coordinates between decimal degrees, DMS, and DM.1 finding
Why it is in this group
- The name "nausika_convert_coordinates" says "convert": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "nausika_convert_coordinates" 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":false}; The name "nausika_convert_coordinates" says "convert": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nausika_is_waterCheck whether a coordinate (latitude, longitude in decimal degrees) is on water or land, and how far it is from the coast.No 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.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nausika_marine_forecastMarine + atmospheric forecast at (latitude, longitude in decimal degrees).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 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
nausika_sea_routeMaritime routing via pgRouting Dijkstra on the MARNET sea-lane graph (detailed coastal routing in the curated areas — Mediterranean, European Atlantic + Canaries, Caribbean, South-…No 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.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nausika_tidesTide predictions or station discovery at a coordinate (latitude, longitude).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 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 9Show 9 read-only tools
nausika_describe_place_schemaReturns the expected attributes for a given place 'type' (the only input parameter: marina, port, bay, fuel_station, city, island, etc.).No findings
Why it is in this group
- The name "nausika_describe_place_schema" says "describe": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nausika_geocodeResolve a place 'query' to coordinates (forward) or find nearest places to 'latitude'+'longitude' (reverse).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "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 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
nausika_get_boat_profileGet your saved boat profile(s).No findings
Why it is in this group
- The name "nausika_get_boat_profile" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nausika_get_favoritesList your favorite places with details and personal notes.Reads private dataNo findings
Why it is in this group
- The name "nausika_get_favorites" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "note": it reads notes.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nausika_get_placeFetch full detail for a single place given its 'id'.No findings
Why it is in this group
- The name "nausika_get_place" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nausika_get_ratingsView ratings for a place (aggregate + your own) or list all your ratings.No findings
Why it is in this group
- The name "nausika_get_ratings" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nausika_get_routesLook up your saved sailing-route library: direct fetch by id, or paginated search by name fragment via query, with limit and offset for pagination.No findings
Why it is in this group
- The name "nausika_get_routes" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nausika_search_placesNautical place search by proximity in the curated areas (Mediterranean, European Atlantic + Canaries, Caribbean, South-East Asia).No findings
Why it is in this group
- The name "nausika_search_places" says "search": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nausika_seasonal_forecastFetch 1-7 month ECMWF SEAS5 seasonal forecast for one point, anywhere in the world.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "fetch": 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 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.
Annotations the server declares
- 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 outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- 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, 18:29 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
- 10
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.nausika.app/.well-known/oauth-protected-resource
- Authorization servers
- https://mcp.nausika.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 10 tools that change things (4 destructive, 6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.nausika.app: tools/list returned 19 tools to an anonymous client, including nausika_manage_boat_profile (destructive), nausika_manage_favorite (destructive), nausika_manage_rating (destructive), nausika_manage_route (destructive), nausika_marine_forecast (write) and 5 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "nausika_calculator" 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":false}; The description's first verb is "evaluate": a word for a change.
The server marks "nausika_convert_coordinates" 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":false}; The name "nausika_convert_coordinates" says "convert": a word for a change.
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.1.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http nausika https://mcp.nausika.appclaude mcp add --transport http nausika https://mcp.nausika.appRun 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__nausika__nausika_seasonal_forecast",
"mcp__nausika__nausika_search_places",
"mcp__nausika__nausika_get_place",
"mcp__nausika__nausika_geocode",
"mcp__nausika__nausika_describe_place_schema",
"mcp__nausika__nausika_get_boat_profile",
"mcp__nausika__nausika_get_favorites",
"mcp__nausika__nausika_get_ratings",
"mcp__nausika__nausika_get_routes"
],
"ask": [
"mcp__nausika__nausika_marine_forecast",
"mcp__nausika__nausika_tides",
"mcp__nausika__nausika_sea_route",
"mcp__nausika__nausika_calculator",
"mcp__nausika__nausika_is_water",
"mcp__nausika__nausika_convert_coordinates"
],
"deny": [
"mcp__nausika__nausika_manage_boat_profile",
"mcp__nausika__nausika_manage_favorite",
"mcp__nausika__nausika_manage_rating",
"mcp__nausika__nausika_manage_route"
]
}
}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 nausika. Review it before you use it.
Capability tags behind 5 rules
- mcp__nausika__nausika_marine_forecast untrusted-input
- mcp__nausika__nausika_seasonal_forecast untrusted-input
- mcp__nausika__nausika_tides untrusted-input
- mcp__nausika__nausika_geocode untrusted-input
- mcp__nausika__nausika_get_favorites private-data
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/app.nausika/mcp/verify?hash=b8698ceb754add9f24437f029e02ccb11a5aa499554ee197d0254faf70e5faf6" | jq -e '.changed == false'Pinned hash b8698ceb754a, from Nov 10, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.nausika/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.nausika/mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:44 UTC.
Nausika MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Nausika MCP server safe?
- No scan can promise that. What its definitions show: 19 tools, 10 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 Nausika MCP server delete data?
- Yes. 4 tools can delete, cancel or revoke something: nausika_manage_boat_profile, nausika_manage_favorite, nausika_manage_rating and nausika_manage_route.
Can the Nausika 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 Nausika MCP server have?
- 19 tools: 4 destructive, 6 write, 9 read. nausika_manage_boat_profile, nausika_manage_favorite, nausika_manage_rating, nausika_manage_route, nausika_marine_forecast, nausika_tides, nausika_sea_route, nausika_calculator and 11 more.
Does the Nausika MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Nausika MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Nausika MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.