# YachtFinder (remote · mcp.yachtfinder.co)

Search about 20,000 yachts for sale, charter and sold, with where AIS last placed each one.

- Trust score: 86/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.yachtfinder.co`: 86/100 (this document), [markdown](https://verifymcp.io/servers/co-yachtfinder-yachtfinder/mcp.md), [page](https://verifymcp.io/servers/co-yachtfinder-yachtfinder/mcp)

## Channel facts

- Endpoint: `https://mcp.yachtfinder.co/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**: 77/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 is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1544 tokens (~308/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% 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 6 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).
  - Supports UI / widget rendering.

## Install

### How do I install the YachtFinder MCP server?

YachtFinder is a hosted endpoint at https://mcp.yachtfinder.co/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 co-yachtfinder-yachtfinder 'https://mcp.yachtfinder.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-yachtfinder-yachtfinder": {
      "url": "https://mcp.yachtfinder.co/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-yachtfinder-yachtfinder": {
      "type": "http",
      "url": "https://mcp.yachtfinder.co/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-yachtfinder-yachtfinder]
url = "https://mcp.yachtfinder.co/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add co-yachtfinder-yachtfinder --url 'https://mcp.yachtfinder.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-yachtfinder-yachtfinder:
    url: "https://mcp.yachtfinder.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-yachtfinder-yachtfinder": {
      "Transport": "http",
      "Url": "https://mcp.yachtfinder.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-yachtfinder-yachtfinder -t streamable-http -u 'https://mcp.yachtfinder.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-yachtfinder-yachtfinder": {
      "type": "http",
      "url": "https://mcp.yachtfinder.co/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-10-29 (score 86, +1)

- [security] Stability: 0.97 → pass

### 2026-10-27 (score 85, +1)

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

### 2026-10-25 (score 84, +1)

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

### 2026-10-23 (score 83, +1)

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

### 2026-10-21 (score 82, +1)

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

### 2026-10-19 (score 81, +1)

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

### 2026-10-17 (score 80, 0)

- [cosmetic] “find_yachts” reworded the description of “near”
- [cosmetic] “yachts_near” reworded the description of “place”

### 2026-10-16 (score 80, +1)

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

## MCP tools (4)

### `find_yachts` (~518 tokens)

Find yachts

Search YachtFinder's catalog of more than 20,000 yachts by builder, length, asking price, build year, status (for sale, for charter, reported sold, not for sale) and place. Returns up to 25 yachts, longest first by default, each with her status, the broker's asking price, YachtFinder's estimate where her page shows one, and a link to her page on yachtfinder.co. `near` keeps yachts whose AIS position, as the site publishes it, lies within `radius_km` of a named harbor or anchorage; `listed_in` matches the town or country the broker's listing states. A yacht listed by more than one brokerage is one result, as on yachtfinder.co, with the others in also_listed_by.

Input parameters:

- `builder` (string): Shipyard, e.g. "Benetti", "Feadship", "Lürssen". Case and accents are ignored.
- `limit` (integer)
- `listed_in` (string): Town or country named in the broker's listing, e.g. "Fort Lauderdale", "Italy". This is where the listing says she is, not an AIS position.
- `max_length_m` (number): Maximum length overall, meters.
- `max_price_usd` (number): Maximum asking price in whole US dollars.
- `max_year` (integer): Latest build year.
- `min_length_m` (number): Minimum length overall, meters.
- `min_price_usd` (number): Minimum asking price in whole US dollars (20000000 = $20M). Only yachts with a published asking price are compared.
- `min_year` (integer): Earliest build year.
- `name_contains` (string): Part of the yacht's name.
- `near` (string): A harbor, harbor town or anchorage by name, e.g. "Port Hercule", "Antibes", "Fort Lauderdale", "Off Monaco". A boat show by its name, "FLIBS" or "the show", is the yachts its page lists at its marina…
- `radius_km` (number): With near: the radius. Default 2 km for a harbor, 3 km for an anchorage.
- `seen_within_hours` (integer): With near: only AIS positions this recent. Default: any position the site publishes (up to 120 days).
- `sort` (string)
- `status` (string): Default for_sale. for_charter includes yachts offered for both.

Output parameters:

- `data_as_of`: When YachtFinder last rebuilt the catalog this answer was read from (ISO 8601).
- `notes` (array)
- `results` (array)
- `source` (object)
- `summary` (string)
- `total_matches` (integer)

### `yachts_near` (~299 tokens)

Yachts near a place

List the yachts whose latest AIS position, as yachtfinder.co publishes it, lies within a radius of a named harbor or anchorage (e.g. "Port Hercule", "Antibes", "Off Monaco") or of a latitude and longitude. By default only positions from the last 24 hours. Each yacht comes with the time of her fix, her distance from the place, whether the harbor's page counts her in port, and a link to her page. A yacht whose position the site does not publish is never listed. Each yacht is listed once, however many brokerages list her.

Input parameters:

- `latitude` (number): Latitude of the place to search (a harbor, an anchorage or a position at sea), in decimal degrees. Not the user's own location.
- `limit` (integer)
- `longitude` (number): Longitude of the place to search, in decimal degrees. Not the user's own location.
- `place` (string): A harbor, harbor town or anchorage by name, or a boat show ("FLIBS", "the show": the yachts its page lists at its marinas now). Give this, or latitude and longitude.
- `radius_km` (number): Default 2 km for a harbor, 3 km for an anchorage, 10 km for a coordinate.
- `seen_within_hours` (integer): Only positions this recent. Default 24.
- `status` (string)

Output parameters:

- `data_as_of`: When YachtFinder last rebuilt the catalog this answer was read from (ISO 8601).
- `notes` (array)
- `place` (object)
- `results` (array)
- `source` (object)
- `summary` (string)
- `total_matches` (integer)

### `yacht_facts` (~195 tokens)

One yacht's facts

One yacht's facts from YachtFinder: builder, year, length, status, the broker's asking price (never a sale price), YachtFinder's estimate where her page shows one, her published AIS position with its time, where her listing says she is, and her page on yachtfinder.co, with the source and date of each fact. Takes her name (add builder or length_m when several yachts share it) or her yachtfinder.co/y/ link. A yacht several brokerages list is one yacht, with each other brokerage's listing, its status and its page.

Input parameters:

- `builder` (string): Her builder, to choose between yachts of the same name.
- `length_m` (number): Her length in meters, to choose between yachts of the same name.
- `yacht` (string, required): Her name, e.g. "Lady Lara", or her yachtfinder.co/y/ link or the id from another answer.

Output parameters:

- `data_as_of`: When YachtFinder last rebuilt the catalog this answer was read from (ISO 8601).
- `found` (string)
- `matches` (array)
- `notes` (array)
- `source` (object)
- `summary` (string)
- `yacht` (object)

### `prepare_inquiry` (~276 tokens)

Prepare an inquiry (never sends)

Prepare a request about one yacht for the person to review and send themselves on yachtfinder.co. This tool never sends anything: it saves a draft (the yacht, optional dates and up to 5 short questions) and returns one link. Give the person the link and tell them plainly that nothing has been sent: on that page they read and edit the draft, sign in, add their own details, and only their tap on Send sends it, under the usual inquiry limits. Take `yacht` from the `id` of a find_yachts, yachts_near or yacht_facts answer; a name is not searched. Questions are shown as plain text: links, markup and line breaks are removed. Do not put names, email addresses or phone numbers in them. The draft expires after 24 hours.

Input parameters:

- `date_from` (string): First day of interest, YYYY-MM-DD: today or later, at most 12 months ahead.
- `date_to` (string): Last day of interest, YYYY-MM-DD, with date_from.
- `questions` (array): Up to 5 questions for the listing broker, each at most 300 characters, in the person's words.
- `yacht` (string, required): The yacht's id from another answer (its `id` field). Not a name and not a link.

Output parameters:

- `data_as_of`: When YachtFinder last rebuilt the catalog this answer was read from (ISO 8601).
- `expires_at` (string)
- `notes` (array)
- `questions_kept` (integer)
- `sent` (boolean): Always false: this tool never sends.
- `source` (object)
- `summary` (string)
- `url` (string): The page where the person reviews, edits and sends the draft.
- `yacht` (object)

## Diagnostics

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

## Score history

- 2026-11-05: 86
- 2026-11-04: 86
- 2026-11-03: 86
- 2026-11-02: 86
- 2026-11-01: 86
- 2026-10-31: 86
- 2026-10-30: 86
- 2026-10-29: 86
- 2026-10-28: 85
- 2026-10-27: 85
- 2026-10-26: 84
- 2026-10-25: 84
- 2026-10-24: 83
- 2026-10-23: 83
- 2026-10-22: 82
- 2026-10-21: 82
- 2026-10-20: 81
- 2026-10-19: 81
- 2026-10-18: 80
- 2026-10-17: 80
- 2026-10-16: 80
- 2026-10-15: 79
- 2026-10-14: 79
- 2026-10-13: 78
- 2026-10-12: 78
- 2026-10-10: 77
- 2026-10-07: 76
- 2026-10-04: 74
- 2026-10-03: 74
- 2026-10-02: 73

## Common questions

### What is the YachtFinder MCP server?

YachtFinder is an MCP server listed in the public MCP registry as co.yachtfinder/yachtfinder. Search about 20,000 yachts for sale, charter and sold, with where AIS last placed each one. This page covers its hosted endpoint (https://mcp.yachtfinder.co/mcp).

### Is the YachtFinder MCP server safe to use?

YachtFinder scores 86 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 YachtFinder MCP server expose?

YachtFinder exposes 4 tools: find_yachts, yachts_near, yacht_facts, prepare_inquiry. Their descriptions and schemas cost roughly 1,288 tokens of context every time the server is loaded.

### Does the YachtFinder MCP server require authentication?

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

### Is the YachtFinder MCP server still maintained?

YachtFinder 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 YachtFinder MCP server?

VerifyMCP ran 14 checks on YachtFinder, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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://mcp.yachtfinder.co/mcp
- Website: https://yachtfinder.co/
- Changelog RSS feed: https://verifymcp.io/servers/co-yachtfinder-yachtfinder/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-yachtfinder-yachtfinder/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/co-yachtfinder-yachtfinder/mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-yachtfinder-yachtfinder/mcp