Skip to content

Esther - DMA Yachting MCP server

com.dmayachting/estherdmayachting.comstreamable-httpv0.1.1Scanned

Crewed yacht charter search: yachts by region, guests, budget, dates. Proposals via a DMA broker.

9 tools: 1 can delete or cancel things, 2 do something that can't be undone, 5 change things and 1 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 2 do something that can't be undone. 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 Esther - DMA Yachting MCP server can do

The Esther - DMA Yachting MCP server is published by dmayachting.com, a domain the MCP Registry verified. It has 9 tools. It can delete or cancel things (1 tool: delete_my_data), do things that cannot be undone, such as sending, paying or publishing (verify_email and verify_phone) and create or change data (5 tools: yacht_details, check_availability, confirm_email, confirm_phone and 1 more). 1 tool only reads.

2 tools can send data out of your system (verify_email and verify_phone).

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.

Last scanned Nov 8, 2026, version 0.1.1.

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.

9 tools

Deletes or cancels 1Claude Code: deny
  • delete_my_dataErase everything stored about the client.No findings

    Why it is in this group

    • The name "delete_my_data" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Erase everything stored about the client. Only call when the client explicitly asks, with confirm set to true.
Can't be undone 2Claude Code: ask
  • verify_emailSend a 6-digit code to the client's email address.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe description's first verb is "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Send a 6-digit code to the client's email address. Verifying an email raises the daily search limit to 4.
  • verify_phoneSend a code by text message to the client's phone.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe description's first verb is "send": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Send a code by text message to the client's phone. Requires a verified email first. Raises the daily search limit to 10 and enables live availability.
Changes things 5Claude Code: ask
  • check_availabilityCheck live availability of one yacht for a date range.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
    Check live availability of one yacht for a date range. Requires a verified phone number.
  • confirm_emailConfirm the email code the client received.No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    Confirm the email code the client received.
  • confirm_phoneConfirm the code the client received by text message.No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    Confirm the code the client received by text message.
  • request_proposalAsk a DMA broker to prepare a proposal for the chosen yachts.No findings

    Why it is in this group

    • The name "request_proposal" says "request": a word for a change.
    Description, as the server wrote it
    Ask a DMA broker to prepare a proposal for the chosen yachts. The broker follows up by email. Requires a verified email.
  • yacht_detailsFull details for one yacht from a previous search: more photos, description, highlights and toys.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
    Full details for one yacht from a previous search: more photos, description, highlights and toys.
Only reads 1Show 1 read-only tool
  • search_yachtsFind charter yachts matching the client's brief.No findings

    Why it is in this group

    • The name "search_yachts" says "search": a word for reading.
    Description, as the server wrote it
    Find charter yachts matching the client's brief. All fields are optional; pass what the client has told you. Returns up to a handful of boats with indicative weekly prices. The first search is free; further searches need a verified email (4 per day) or phone (10 per day).

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.

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 out2
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 15, 2026, 13:20 UTC, unchanged since Nov 8, 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
8
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
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (1 destructive, 2 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.dmayachting.com/mcp: tools/list returned 9 tools to an anonymous client, including delete_my_data (destructive), verify_email (irreversible), verify_phone (irreversible), yacht_details (write), check_availability (write) and 3 more

    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.

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.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http esther https://mcp.dmayachting.com/mcp
claude mcp add --transport http esther https://mcp.dmayachting.com/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__esther__search_yachts"
    ],
    "ask": [
      "mcp__esther__yacht_details",
      "mcp__esther__check_availability",
      "mcp__esther__verify_email",
      "mcp__esther__confirm_email",
      "mcp__esther__verify_phone",
      "mcp__esther__confirm_phone",
      "mcp__esther__request_proposal"
    ],
    "deny": [
      "mcp__esther__delete_my_data"
    ]
  }
}

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 esther. Review it before you use it.

Capability tags behind 2 rules
  • mcp__esther__verify_email outbound
  • mcp__esther__verify_phone outbound

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/com.dmayachting/esther/verify?hash=801562f0970319288bc96217f8317445b42a5cf6af8488179fe5cba3ed35c8a4" | jq -e '.changed == false'

Pinned hash 801562f09703, from Nov 8, 2026, 23:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.dmayachting/esther/changes.xml

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

Badge

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

Source: MCP Registry. Synced Nov 8, 2026, 23:17 UTC.

Esther - DMA Yachting MCP server: questions and answers

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

Is the Esther - DMA Yachting MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 8 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 Esther - DMA Yachting MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_my_data.

Can the Esther - DMA Yachting MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: verify_email and verify_phone.

What tools does the Esther - DMA Yachting MCP server have?

9 tools: 1 destructive, 2 irreversible, 5 write, 1 read. delete_my_data, verify_email, verify_phone, yacht_details, check_availability, confirm_email, confirm_phone, request_proposal and 1 more.

Does the Esther - DMA Yachting MCP server need sign-in or OAuth?

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

Does the Esther - DMA Yachting MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): verify_email and verify_phone.

Has the Esther - DMA Yachting MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.