# Where Boats Anchor (remote · whereboatsanchor.com)

Where boats stayed the night, and in what wind, at anchorages worldwide, with tonight's forecast.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `whereboatsanchor.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-whereboatsanchor-anchorages/whereboatsanchor.md), [page](https://verifymcp.io/servers/com-whereboatsanchor-anchorages/whereboatsanchor)

## Channel facts

- Endpoint: `https://whereboatsanchor.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1133 tokens (~283/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Where Boats Anchor MCP server?

Where Boats Anchor is a hosted endpoint at https://whereboatsanchor.com/mcp, 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.

### Claude

```bash
claude mcp add --transport http com-whereboatsanchor-anchorages 'https://whereboatsanchor.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-whereboatsanchor-anchorages": {
      "url": "https://whereboatsanchor.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-whereboatsanchor-anchorages": {
      "type": "http",
      "url": "https://whereboatsanchor.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-whereboatsanchor-anchorages]
url = "https://whereboatsanchor.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-whereboatsanchor-anchorages": {
      "type": "remote",
      "url": "https://whereboatsanchor.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-whereboatsanchor-anchorages --url 'https://whereboatsanchor.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-whereboatsanchor-anchorages:
    url: "https://whereboatsanchor.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-whereboatsanchor-anchorages": {
      "Transport": "http",
      "Url": "https://whereboatsanchor.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-whereboatsanchor-anchorages -t streamable-http -u 'https://whereboatsanchor.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-whereboatsanchor-anchorages": {
      "type": "http",
      "url": "https://whereboatsanchor.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 70, 0)

- [security] Tool “find_anchorages” rewrote its description, which is the text the model reads

### 2026-11-02 (score 70, +1)

- [security] Tool “find_anchorages” rewrote its description, which is the text the model reads

### 2026-11-01 (score 69, 0)

- [security] Tool “find_anchorages” rewrote its description, which is the text the model reads
- [cosmetic] “find_anchorages” reworded the description of “wind_kn”

### 2026-10-31 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 68)

First indexed and scored.

## MCP tools (4)

### `find_anchorages` (~563 tokens)

Find anchorages near a position, tonight or in a wind

Lists the places near a position where boats stopped, overnight or by day, with where boats stayed in tonight's forecast there or in a given wind. For tonight, call it without wind_from and wind_kn: the answer then carries tonight's forecast at the position and each place's nights in each of tonight's winds, as the site's Tonight does. Give a wind only to ask about that wind. Each place comes with how far and which way it lies from the position (e.g. 0.5 NM SW), its nights, where it is, its page and its place on the map. With a wind, each place gets its nights in that wind, split by strength, with the gusts on those nights (kt), and the list is sorted by those nights. A wind is counted as the site counts it: its compass point at 10 or 20 kt or more, as the forecast's band (e.g. wind_kn 15 counts E 10 kt or more). wind_from alone counts the direction at any strength. Under 3 kt (wind_kn in whole knots) the wind has no settled direction, so every night counts. A night counts once, in the wind it blew from most. Tonight is counted as the site's Tonight counts it: tonight's forecast times that are night there, each counted in its compass point at 10 or 20 kt or more, as its band (every night under 3 kt), and each place's fewest nights in any one of them. Where a place faces open water and tonight's swell there is 0.5 m or more, the nights of that count that also had that swell are given beside it, as on the site. The swell never changes the count. Places with a night in every one of tonight's winds come first, by those fewest nights, then the rest. Without a forecast, by distance. Positions are WGS84 decimal degrees.

Input parameters:

- `lat` (number, required): Latitude of the centre, WGS84 decimal degrees.
- `limit` (integer): Most places to list, 10 when left out, at most 25.
- `lon` (number, required): Longitude of the centre, WGS84 decimal degrees.
- `radius_nm` (number): Radius of the circle in nautical miles, 15 when left out, at most 50.
- `wind_from`: Direction the wind blows from: degrees true (0 to 360) or a point of the 16-point compass (N, NNE, NE ... NNW).
- `wind_kn` (number): Mean wind speed in knots (kt). Needs wind_from. Under 3 kt as whole knots the direction counts for nothing, as on the site: every night counts.

Output parameters:

- `center` (object)
- `note` (string|null)
- `places` (array)
- `places_in_radius` (integer)
- `radius_nm` (number)
- `source` (object)
- `tonight`: Tonight's forecast at the position, null when it isn't available.
- `wind`

### `get_bay_evidence` (~270 tokens)

Get what boats did at one place

What boats did at one place, as its page on the site shows it. Its nights. Its nights by the eight compass points the wind blew from, split under 10, 10 to 20 and 20 kt or more, with the different boats and the windiest night of each. Its boats by length and type (cells under 3 boats null), its day stops by wind, its nights by swell direction where its page shows them, and the places nearby with how far and which way. It carries tonight's forecast at the place: the night's strongest forecast wind and the place's nights in that wind, as its page's Tonight shows it. Give bay_id, or name with near (WGS84 decimal degrees) to rank places of one name. Several places of one name come back as candidates.

Input parameters:

- `bay_id` (string): The place's id, as find_anchorages and list results give it (the page address's last part, e.g. cane-garden-bay).
- `name` (string): The place's name, when bay_id isn't known. Several places of one name are listed as candidates, never guessed.
- `near` (object): A position to rank places of the same name by nearness, WGS84 decimal degrees.

Output parameters:

- `bay`
- `candidates` (array)
- `note` (string|null)
- `source` (object)
- `tonight`: Tonight at this place, null when the forecast isn't available or for candidates.

### `get_climatology` (~143 tokens)

Get the wind through the year at a place

Wind through the year at a place, as its page shows it: for each month, the nights whose strongest hour reached 20 kt and 30 kt, each year's fewest and most of them, the commonest directions of the nights of 20 kt or more, and the strongest gust, over ten years, for the area round the place. The first call for an area can answer preparing, then ready a few minutes later.

Input parameters:

- `bay_id` (string, required): The place's id, as find_anchorages gives it.
- `month` (integer): One month, 1 (January) to 12 (December). Every month when left out.

Output parameters:

- `bay_id` (string)
- `months` (array)
- `name` (string|null)
- `note` (string|null)
- `source` (object)
- `status` (string)
- `years`: How many years the wind through the year covers.

### `list_regions` (~93 tokens)

List countries, regions and cruising areas

The site's directory of places where boats stayed the night. Without a country: each country with its number of places. With a country (directory slug or ISO code): its regions and cruising areas with their number of places. Each with the address of its directory page.

Input parameters:

- `country` (string): A country's directory slug (new-zealand) or ISO 3166 two-letter code (NZ). Every country when left out.

Output parameters:

- `areas` (array)
- `countries` (array)
- `country`
- `note` (string|null)
- `regions` (array)
- `source` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-whereboatsanchor-anchorages/whereboatsanchor#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 68
- 2026-10-29: 68

## Common questions

### What is the Where Boats Anchor MCP server?

Where Boats Anchor is an MCP server listed in the public MCP registry as com.whereboatsanchor/anchorages. Where boats stayed the night, and in what wind, at anchorages worldwide, with tonight's forecast. This page covers its hosted endpoint (https://whereboatsanchor.com/mcp).

### Is the Where Boats Anchor MCP server safe to use?

Where Boats Anchor scores 71 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 Where Boats Anchor MCP server expose?

Where Boats Anchor exposes 4 tools: find_anchorages, get_bay_evidence, get_climatology, list_regions. Their descriptions and schemas cost roughly 1,069 tokens of context every time the server is loaded.

### Does the Where Boats Anchor MCP server require authentication?

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

### Is the Where Boats Anchor MCP server still maintained?

Where Boats Anchor is still listed as active in the MCP registry. We last reached this channel on 5 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 Where Boats Anchor MCP server?

VerifyMCP ran 13 checks on Where Boats Anchor, 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.

## Links

- Remote endpoint: https://whereboatsanchor.com/mcp
- Website: https://whereboatsanchor.com/connect
- Changelog RSS feed: https://verifymcp.io/servers/com-whereboatsanchor-anchorages/whereboatsanchor.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-whereboatsanchor-anchorages/whereboatsanchor/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-whereboatsanchor-anchorages/whereboatsanchor.json
- HTML version of this page: https://verifymcp.io/servers/com-whereboatsanchor-anchorages/whereboatsanchor