Skip to content

YachtFinder MCP server

co.yachtfinder/yachtfinderyachtfinder.costreamable-httpv1.0.0Scanned

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

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 YachtFinder MCP server can do

The YachtFinder MCP server is published by yachtfinder.co, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: yacht_facts and prepare_inquiry), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.0.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.

4 tools

Changes things 2Claude Code: ask
  • prepare_inquiryPrepare a request about one yacht for the person to review and send themselves on yachtfinder.co.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.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Prepare an inquiry (never sends)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • yacht_factsOne 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 AI…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
    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. Each source's level says how much it bears, as her page labels it: verified, source-provided (as the listing states it), calculated (by YachtFinder: a conversion, or a match we made and did not verify), estimated or AI-generated.

    Annotations the server declares

    • title: One yacht's facts
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • find_yachtsSearch 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.No findings

    Why it is in this group

    • The name "find_yachts" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find yachts
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • yachts_nearList the yachts whose latest AIS position, as yachtfinder.co publishes it, lies within a radius of a named harbor or anchorage (e.g.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Yachts near a place
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:32 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
2
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
no
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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.yachtfinder.co/mcp: tools/list returned 4 tools to an anonymous client, including yacht_facts (write), prepare_inquiry (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http yachtfinder https://mcp.yachtfinder.co/mcp
claude mcp add --transport http yachtfinder https://mcp.yachtfinder.co/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__yachtfinder__find_yachts",
      "mcp__yachtfinder__yachts_near"
    ],
    "ask": [
      "mcp__yachtfinder__yacht_facts",
      "mcp__yachtfinder__prepare_inquiry"
    ],
    "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 yachtfinder. 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/co.yachtfinder/yachtfinder/verify?hash=f5316e1d1b0b3a28a88ac4d70341829dab2c589d0af0faa01d56fad107f99695" | jq -e '.changed == false'

Pinned hash f5316e1d1b0b, from Nov 12, 2026, 11:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/co.yachtfinder/yachtfinder/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for co.yachtfinder/yachtfinder
[![Anlyon Radar](https://radar.anlyon.com/badge/co.yachtfinder/yachtfinder.svg)](https://radar.anlyon.com/servers/co.yachtfinder/yachtfinder)

Source: MCP Registry. Synced Oct 21, 2026, 17:47 UTC.

YachtFinder MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the YachtFinder MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 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 YachtFinder MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

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

4 tools: 2 write, 2 read. yacht_facts, prepare_inquiry, find_yachts and yachts_near.

Does the YachtFinder MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the YachtFinder MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the YachtFinder MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.