Editorial Standards & WebMCP Specifications

At wiki.yachts, we believe that high-end maritime documentation requires absolute precision. Information on superyachts can often be thin, contradictory, or sensationalized. We combat this by implementing rigorous editorial standards aligned with Google's search metrics for E-E-A-T (Experience, Expertise, Authoritativeness, and Trustworthiness).

1. Data Collection & Verification

Every yacht profile in our registry undergoes a meticulous verification process. We cross-reference statistics (LOA, beam, draft, gross tonnage) using official builder specifications (e.g. Lürssen, Blohm+Voss, Perini Navi, Oceanco), classification society records (Lloyd’s Register, RINA, ABS), and verified registry entries. When discrepancies arise, our team consults veteran captains and marine surveyors.

2. Experienced Authorship

Our content is authored and reviewed exclusively by marine professionals. Capt. William Sterling, a former master of motor yachts over 120 meters, reviews and signs off on every structural and operational specification record. By ensuring that content is reviewed by individuals with real-world maritime captaincy experience, we guarantee authoritative reporting.

3. Commercial Transparency & Value Integrity

We provide fair market valuations and weekly charter pricing trends based on real-time brokerage reports (e.g., Burgess, Y.CO, Fraser). We maintain strict separation between editorial listings and broker sponsorships to preserve database neutrality and trust.

We believe the future of the web is collaborative. AI agents should be able to browse, evaluate, and interact with our database as effectively as a human visitor. To achieve this, wiki.yachts natively supports the emerging WebMCP (Web Model Context Protocol) browser-native standard.

When an AI agent (such as an LLM running with browser execution plugins) lands on our page, it does not need to parse raw HTML classes or click buttons. Instead, it checks the navigator.modelContext object and discovers structured JavaScript tools with JSON Schemas. It can execute these tools in the page context, utilizing the client's current session and cookies.

How Agents Discover Our Tools

Visiting agents can review the declarative manifest file at /webmcp.json to inspect available endpoints. Imperatively, the website registers these tools on window load:

// Check and register WebMCP tools natively
if ('modelContext' in navigator) {
  navigator.modelContext.registerTool({
    name: "getYachtDetails",
    description: "Retrieves complete specifications and history for a yacht by ID",
    inputSchema: {
      type: "object",
      properties: {
        id: { type: "string", description: "Yacht unique identifier" }
      },
      required: ["id"]
    },
    execute: async (params) => {
      // Exposes the local database directly to the LLM agent
      const yacht = YACHTS_DATA.find(y => y.id === params.id);
      return yacht ? { success: true, yacht } : { success: false };
    }
  });
}

Our exposed WebMCP API includes tools to list all yachts, perform complex text searches, compare hulls side-by-side, and submit booking inquiry leads securely to our advisory desk.

To see WebMCP in action on your screen, click the gold compass icon in the bottom-right corner of your browser. This floating console shows the active tool configurations and displays a real-time console log of AI agent executions on this page.