Home / MCP registry index / app.nausika/mcp
Nausika
app.nausika/mcp in the official MCP registry.
Endpoint https://mcp.nausika.app/. Source: github.com/nausika-app/nausika-feedback.
The registry describes it as: Mediterranean marine, nautical, sailing: forecasts, tides, sea routes, anchorages, POIs for AI.
We read its 19 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
nausika_marine_forecast nausika_seasonal_forecast nausika_tides nausika_search_places nausika_get_place nausika_sea_route nausika_calculator nausika_geocode nausika_describe_place_schema nausika_is_water nausika_convert_coordinates nausika_manage_boat_profile nausika_get_boat_profile nausika_manage_favorite nausika_get_favorites nausika_manage_rating nausika_get_ratings nausika_manage_route nausika_get_routes
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-nausika-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.