Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Esther - DMA Yachting

REMOTE · MCP.DMAYACHTING.COM

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

+3 this week 70 Trust /100

Last scanned (23 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 754 tokens (~83/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "verify_email" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 12 Nov 26 +1

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

  • 9 Nov 26 +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.

  • 8 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 7 Nov 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.dmayachting.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.dmayachting.com CN=YR2,O=Let's Encrypt,C=US 7 Nov 2026 5 Feb 2027 RSA 2048 SHA256-RSA 6d1bae95320d0536ae2d46acbd0db2b247f
SANs: mcp.dmayachting.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.dmayachting.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
dmayachting.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.dmayachting.com/mcp Verified 200
http (plaintext) http://mcp.dmayachting.com/mcp HTTPS enforced 301 https://mcp.dmayachting.com/mcp
MCP tools · 9 exposed · ~625 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_availability ~64

Check live availability of one yacht for a date range. Requires a verified phone number.

NameTypeReqDescription
fromstringyesStart date, YYYY-MM-DD
idstringyesYacht id from search results
untilstringyesEnd date, YYYY-MM-DD

No output schema declared.

No examples provided.

confirm_email ~27

Confirm the email code the client received.

NameTypeReqDescription
codestringyesCode from the email

No output schema declared.

No examples provided.

confirm_phone ~30

Confirm the code the client received by text message.

NameTypeReqDescription
codestringyesCode from the text message

No output schema declared.

No examples provided.

delete_my_data ~41

Erase everything stored about the client. Only call when the client explicitly asks, with confirm set to true.

NameTypeReqDescription
confirmbooleanyesMust be true

No output schema declared.

No examples provided.

request_proposal ~69

Ask a DMA broker to prepare a proposal for the chosen yachts. The broker follows up by email. Requires a verified email.

NameTypeReqDescription
idsarrayyesYacht ids the client is interested in
notestringyesWhat the client wants the broker to know: dates, preferences, questions

No output schema declared.

No examples provided.

search_yachts ~242

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

NameTypeReqDescription
budget_max_weekinteger–Maximum budget per week
cabinsinteger–Minimum number of cabins
crewedstring–Crewed charter or bareboat
currencystring–Currency of the budget
datesobject–Charter dates
guestsinteger–Number of guests
length_max_mnumber–Maximum length in metres
length_min_mnumber–Minimum length in metres
regionstring–Cruising area or destination, e.g. Greece, Croatia, BVI, Caribbean
textstring–Any other free-text wishes
toysarray–Must-have water toys and amenities, e.g. jacuzzi, seabob
typestring–Yacht style
year_mininteger–Oldest acceptable build or refit year

No output schema declared.

No examples provided.

verify_email ~43

Send a 6-digit code to the client's email address. Verifying an email raises the daily search limit to 4.

NameTypeReqDescription
emailstringyesClient email address

No output schema declared.

No examples provided.

verify_phone ~61

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.

NameTypeReqDescription
phonestringyesPhone number in E.164 format, e.g. +14155550123

No output schema declared.

No examples provided.

yacht_details ~48

Full details for one yacht from a previous search: more photos, description, highlights and toys.

NameTypeReqDescription
idstringyesYacht id from search results (e_ followed by 12 hex characters)

No output schema declared.

No examples provided.

Install

How do I install the Esther - DMA Yachting MCP server?

Esther - DMA Yachting is a hosted endpoint at https://mcp.dmayachting.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.

remote · mcp.dmayachting.com

# add to Claude Code
claude mcp add --transport http com-dmayachting-esther 'https://mcp.dmayachting.com/mcp'
Common questions

What is the Esther - DMA Yachting MCP server?

Esther - DMA Yachting is an MCP server listed in the public MCP registry as com.dmayachting/esther. Crewed yacht charter search: yachts by region, guests, budget, dates. Proposals via a DMA broker. This page covers its hosted endpoint (https://mcp.dmayachting.com/mcp).

Is the Esther - DMA Yachting MCP server safe to use?

Esther - DMA Yachting scores 70 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 Esther - DMA Yachting MCP server expose?

Esther - DMA Yachting exposes 9 tools: search_yachts, yacht_details, check_availability, verify_email, confirm_email, and 4 more. Their descriptions and schemas cost roughly 625 tokens of context every time the server is loaded.

Does the Esther - DMA Yachting MCP server require authentication?

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

Is the Esther - DMA Yachting MCP server still maintained?

Esther - DMA Yachting is still listed as active in the MCP registry. We last reached this channel on 21 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 Esther - DMA Yachting MCP server?

VerifyMCP ran 12 checks on Esther - DMA Yachting, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Esther - DMA Yachting: Authorization. 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.