aquaview-mcp server
org.aquaview/aquaview-mcpaquaview.orgstreamable-httpv0.2.0Scanned
AQUAVIEW MCP Server - Search and access global oceanographic and environmental datasets.
6 tools: 1 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- 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 aquaview-mcp server can do
The aquaview-mcp server is published by aquaview.org, a domain the MCP Registry verified. It has 6 tools. It can create or change data (1 tool: aggregate), but cannot delete data. 5 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 3 findings (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 0.2.0.
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.
6 tools
Changes things 1Claude Code: ask
aggregateRun aggregation queries on the AQUAVIEW catalog — get counts, spatial distributions, temporal distributions, and per-collection breakdowns without fetching individual items.1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
Findings
- Info
The description is 2,415 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...th `name`, `data_type`, and `value`/`buckets` for each requested aggregation."
Description, as the server wrote it Run aggregation queries on the AQUAVIEW catalog — get counts, spatial distributions, temporal distributions, and per-collection breakdowns without fetching individual items. Args: aggregations: Comma-separated aggregation types (required). Valid types: total_count, datetime_max, datetime_min, datetime_frequency, collection_frequency, geometry_geohash_grid_frequency, geometry_geotile_grid_frequency. collections: Comma-separated collection IDs to scope the aggregation (e.g., "NOAA,NDBC"). exclude_collections: Comma-separated collection IDs to omit from the aggregation (e.g., "INCIDENT_NEWS"). Applied as a CQL2 NOT filter, so it composes with `filter`. bbox: Bounding box as "west,south,east,north". datetime: Temporal filter (same format as search_datasets). q: Free-text search to scope the aggregation. Multi-word queries are tokenised on whitespace and OR-combined to mirror search_datasets semantics (aggregate compiles q to CQL2 LIKE clauses on title/description; a raw %multi word% substring match would return 0 for most queries). filter: CQL2-JSON filter as an object or JSON-encoded string. Flat example: {"op": "=", "args": [{"property": "aquaview:institution"}, "NOAA"]}. Nested example: {"op": "<=", "args": [{"property": "aquaview:column_stats_summary.variables.Pressure.min"}, 10]}. license: Comma-separated SPDX license id(s) to scope the aggregation (e.g., "CC-BY-4.0,CC0-1.0"), or one of "public-domain", "proprietary", "various", "unknown". Matched against `aquaview:license`. precision: Grid precision for geo aggregations (1-12, higher = finer grid). Applied to whichever geo aggregation type is requested. datetime_frequency_interval: Interval for datetime_frequency (e.g., "month", "year", "day"). output_format: "csv" (default, sectioned CSV — ~50% fewer tokens than TOON for bucket responses), "json" (structured STAC API response), or "toon". Use "json" for deterministic/structured consumers. Returns: Aggregation results. In CSV mode: one `## <name>` section per aggregation; scalars render on a single line; bucket aggregations render as CSV with a `# rows: N` header, a `# key=value` line for columns that are constant across all rows, and a conventional CSV table of the varying columns. In JSON/TOON mode: the raw SFEOS response with `name`, `data_type`, and `value`/`buckets` for each requested aggregation.
Only reads 5Show 5 read-only tools
get_dataPull actual observation rows from an AQUAVIEW data source — not catalog metadata.1 finding
Why it is in this group
- The name "get_data" says "get": a word for reading.
Findings
- Info
The description is 4,721 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...slightly faster. output_format: 'csv' (compact, default), 'json', or 'toon'."
Description, as the server wrote it Pull actual observation rows from an AQUAVIEW data source — not catalog metadata. Use this whenever the question needs the measurements themselves (temperature profiles, float positions, buoy readings), rather than which datasets exist. Call list_data_sources first for a source's canonical variable names, its `qc_modes`, and its `engine` (gridded "xarray" sources have no rows to pull). READ 'returned' FIRST. It is one of three values: - 'complete': 'rows' holds EVERY matching row (or your whole 'limit'). Safe to compute anything from. - 'head': 'rows' holds the FIRST rows in the source's natural order (see 'head.order'), out of 'head.of' total. These are not a random sample — later rows differ systematically — so never average or take a maximum from them. To get more, set 'limit' up to 'head.max_inline'; beyond that, narrow the request or fetch 'download_url'. - 'none': no rows. 'refusal.reason' says why. 'unscoped_query' means add a bbox/datetime/depth/filter. 'no_natural_order' means the source has no column to order a partial read by, so no partial set can be given honestly — narrow until it fits, or use 'stats'. The rest are transient; retry. OTHER FIELDS: - 'stats': exact minimum, maximum, mean and spread computed over EVERY matching row. Use these for any numeric claim — exact at any data size. - 'stats_basis': what shaped those numbers. If 'qc' is null the values are UNSCREENED and may include implausible outliers from bad sensor readings; say so, or re-run with a quality filter. When a mode was applied, 'qc_screened' lists the variables it actually checked — a variable not in it was NOT flag-checked, and an empty list means nothing was screened despite 'qc' naming a mode. 'qc_note', when present, explains that the screen drops whole rows, so it shapes every variable's figures. - 'structure': how many distinct floats/stations/profiles matched — often the real answer ("16 profiles from 5 floats"), which no row count gives. - 'sample': a genuinely random sample, included only when rows were withheld. For seeing what the data looks like — do NOT compute from it. - 'download_url': the full result as a file, in 'download_format'. Fetch it if you can run code; otherwise give it to the user. Absent for restricted sources and for matches too large to stage synchronously. - 'schema': each column's real type. Needed when reading the CSV download, which stores no types — without it a reader infers them and can get them wrong (an id column read as a number loses leading zeros). - 'omitted': names any part that could not be computed. An absent field is unknown, NOT zero. Args: source: Source id from list_data_sources (e.g. "gadr", "wod", "ndbc"). variables: Comma-separated canonical variable names (e.g. "temperature,salinity,depth"). bbox: Bounding box "west,south,east,north" (e.g. "-161,18,-154,23"). datetime: ISO-8601 instant or range ("2022-06-01/2022-06-30"; ".." for an open end). depth: Depth range in metres below surface, "min,max" (e.g. "0,200"). filters: JSON object of extra column filters on ordinary columns, e.g. {"data_mode": "D"}. For QUALITY screening prefer `qc` below — a source that defines modes applies them to each measurement correctly, where filtering a raw flag column yourself is easy to get wrong. qc: Named quality mode, and the right way to screen. Unfiltered ocean data contains sentinel values that make maxima and means physically implausible, so screen before any scientific claim. list_data_sources reports each source's `qc_modes`; pass one of those here. Passing a mode to a source with none is an error. A source with no modes may still expose per-measurement quality columns you can filter directly via `filters` — list_data_sources shows its variables. limit: Maximum rows to return, honored up to what fits inline. Omit for a default-sized head. When a response comes back as a head, `head.max_inline` tells you the largest limit worth asking for on that request. format: Encoding of `download_url`. Default "parquet" — it keeps every column's type, is ~5x smaller and ~2x faster, and `pd.read_parquet(url)` reads it. Choose "csv" when the link is going to a person who will open it by hand rather than into code, or when you can fetch a URL but cannot run code; then use `schema` to set the column types yourself. include_sample: Set False to skip the random sample and return slightly faster. output_format: 'csv' (compact, default), 'json', or 'toon'.
get_itemFetch a single AQUAVIEW dataset item with full details, properties, and download links (assets).No findings
Why it is in this group
- The name "get_item" says "get": a word for reading.
Description, as the server wrote it Fetch a single AQUAVIEW dataset item with full details, properties, and download links (assets). STAC items embed assets inline — each asset includes an href (download URL) and media type, so there is no need for a separate "files" call. Args: collection: The collection ID the item belongs to (e.g., "NOAA", "NDBC", "WOD"). Available from search results or list_collections. item_id: The unique item identifier (e.g., "wod_xbt_ZZ144579"). Available from search results. output_format: "toon" (default) or "json". Returns: Full STAC item with geometry, properties (title, description, datetime, institution, variables, per-variable descriptions under aquaview:variable_descriptions when available, etc.), and assets (download links with media types).
list_collectionsList all available AQUAVIEW data collections (sources).No findings
Why it is in this group
- The name "list_collections" says "list": a word for reading.
Description, as the server wrote it List all available AQUAVIEW data collections (sources). Returns a summary of each collection with ID, title, description, spatial/temporal extent, and keywords. Use collection IDs to filter searches. These are CATALOG collections. Several are also queryable row by row — see list_data_sources for the sources get_data can pull observations from. A collection's bbox and temporal range are OUTER BOUNDS, not a promise of coverage. They are the envelope around everything in the collection, so most of the box usually holds no data at all — an Argo collection spans the global ocean, a partner collection with one point either side of the date line spans the whole planet. An empty result for a point or window inside the extent is the normal answer, not a failure: report "no data there", not "the query did not work", and do not widen a search on the strength of a bbox alone. Args: tag: Only collections with this tag, e.g. "uxs" for uncrewed systems. Pass the returned IDs as `collections` to search_datasets to search only those. output_format: "csv" (default, sectioned CSV — ~20% fewer tokens than TOON for this tabular response), "json", or "toon". Use "json" for deterministic/structured consumers. Returns: List of collections with count. CSV mode emits a single `## collections` section with columns id,title,bbox,temporal,keywords,description; bbox is rendered as "west,south,east,north"; temporal as "min|max"; keywords ";"-joined.
list_data_sourcesList the AQUAVIEW data sources you can pull actual rows from, or describe one in detail.No findings
Why it is in this group
- The name "list_data_sources" says "list": a word for reading.
Description, as the server wrote it List the AQUAVIEW data sources you can pull actual rows from, or describe one in detail. Call this BEFORE get_data on a source you have not used. Variable names are canonical per source and cannot be guessed — this is where they come from. With an API key, sources your account is entitled to appear here too. Args: source_id: Omit to list every visible source. Give one (e.g. "gadr") to get its full detail: canonical variable names, units, row limits, and filterable columns. output_format: 'csv' (compact, default), 'json', or 'toon'.
search_datasetsSearch the AQUAVIEW catalog — a comprehensive collection of 268K+ global oceanographic, atmospheric, and marine datasets from 15 sources (NOAA, NDBC, IOOS, WOD, CoastWatch, etc.), …1 finding
Why it is in this group
- The name "search_datasets" says "search": a word for reading.
Findings
- Info
The description is 3,777 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...feature shape, with the `assets` dict present only when include_assets=True."
Description, as the server wrote it Search the AQUAVIEW catalog — a comprehensive collection of 268K+ global oceanographic, atmospheric, and marine datasets from 15 sources (NOAA, NDBC, IOOS, WOD, CoastWatch, etc.), intended for scientific research, data analysis, and environmental monitoring. This searches METADATA — which datasets exist. To pull the actual observations (temperature profiles, buoy readings, float positions), use get_data instead; list_data_sources shows which sources support it. You must provide at least one of: q, bbox, datetime, collections, filter, or token. Hint: When the user asks for a region, prefer the 'bbox' parameter over including region name in 'q'. Use the geo_hints resource for common bounding boxes. Args: q: Free-text search across title, description, and keywords (e.g., "sea surface temperature"). Case-insensitive, OR logic across terms. bbox: Bounding box as "west,south,east,north" (e.g., "-98,24,-80,31" for Gulf of Mexico). datetime: Temporal filter. Single datetime, range ("2020-01-01T00:00:00Z/2024-12-31T23:59:59Z"), or open-ended ("../2024-01-01T00:00:00Z" or "2020-01-01T00:00:00Z/.."). collections: Comma-separated collection IDs to search within (e.g., "NOAA,NDBC,WOD"). Use list_collections to see available IDs. exclude_collections: Comma-separated collection IDs to omit from results (e.g., "INCIDENT_NEWS" to drop oil-spill reports from free-text searches). Applied as a CQL2 NOT filter, so it composes with `filter`. filter: CQL2-JSON filter as an object or JSON-encoded string. Supports flat and nested property paths. Flat example: {"op": "=", "args": [{"property": "aquaview:institution"}, "NOAA/NCEI"]}. Nested example (filter by per-variable stats summary): {"op": "<=", "args": [{"property": "aquaview:column_stats_summary.variables.Pressure.min"}, 10]}. Supported operators: =, <>, <, >, <=, >=, like, between, in, and, or, not. license: Comma-separated SPDX license id(s) to match exactly (e.g., "CC-BY-4.0,CC0-1.0"). Also accepts the controlled extra values "public-domain", "proprietary", "various", "unknown". Matched against `aquaview:license`, which is normalized on every item regardless of source. sortby: Sort specification as "+field,-field" (e.g., "+properties.datetime,-id"). + = ascending, - = descending. limit: Number of results to return, 1-100. Defaults to 10. token: Pagination token from a previous response's 'next_token' field. Pass this to get the next page of results. fields: Comma-separated list of fields to include in results (e.g., "id,geometry,properties.title"). Reduces response size. When set in CSV mode, emits projected columns (no canonical columns, no asset_keys, no `## assets` section). include_assets: If False (default), asset download records are omitted to save ~60-70% of response tokens; CSV mode still emits a capped `asset_keys` hint column (e.g. `column_stats;overview;gdac_prof;+[N]`) so an agent can see what kinds of assets exist. To get full URLs, call `get_item(collection, item_id)` for the specific id. If True, assets are included inline (full dict for JSON/TOON; `## assets` section with item_id,key,href,type,title rows for CSV). output_format: "csv" (default, sectioned CSV — canonical columns including asset_keys hint), "json", or "toon". Returns: Search results with metadata (total matched, returned, next_token) and items. CSV mode emits `## metadata` + `## items` sections and a `## assets` section when include_assets=True; columns are id,collection,bbox,datetime,title,institution, platform_type,cdm_data_type,variables,keywords,source_url,description, column_stats_summary,geometry,asset_keys. JSON/TOON return the STAC feature shape, with the `assets` dict present only when include_assets=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 private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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, 19:17 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
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- yes
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.aquaview.org/mcp: tools/list returned 6 tools to an anonymous client, including aggregate (write)
Findings
Matches of fixed checks, with the text they matched.
- Infosearch_datasets
The description is 3,777 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...feature shape, with the `assets` dict present only when include_assets=True."
- Infoaggregate
The description is 2,415 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...th `name`, `data_type`, and `value`/`buckets` for each requested aggregation."
- Infoget_data
The description is 4,721 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...slightly faster. output_format: 'csv' (compact, default), 'json', or 'toon'."
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.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http aquaview https://mcp.aquaview.org/mcpclaude mcp add --transport http aquaview https://mcp.aquaview.org/mcpRun 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__aquaview__search_datasets",
"mcp__aquaview__get_item",
"mcp__aquaview__list_collections",
"mcp__aquaview__list_data_sources",
"mcp__aquaview__get_data"
],
"ask": [
"mcp__aquaview__aggregate"
],
"deny": []
}
}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 aquaview. Review it before you use it.
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/org.aquaview/aquaview-mcp/verify?hash=0d62cbff4d2fdb55033f84abb61b927160c508a499c599959d1c3a4d4e092afd" | jq -e '.changed == false'Pinned hash 0d62cbff4d2f, from Nov 19, 2026, 00:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/org.aquaview/aquaview-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/org.aquaview/aquaview-mcp)Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.
aquaview-mcp server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the aquaview-mcp server safe?
- No scan can promise that. What its definitions show: 6 tools, 1 of which can change, send or delete something, and 3 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 aquaview-mcp server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the aquaview-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 aquaview-mcp server have?
- 6 tools: 1 write, 5 read. aggregate, search_datasets, get_item, list_collections, list_data_sources and get_data.
Does the aquaview-mcp server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the aquaview-mcp server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the aquaview-mcp server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.