Sedna Genesis

com.sednasystemPublished by sednasystem.comOfficial publisherv1.0.0Updated Oct 24, 2026

Customer-facing yacht search and charter request MCP server by Sedna System.

VerifiedStreamable HTTPWeb executableLocation & LifestyleBusiness & Commerce

Overview

AI-generated overview

Sedna Genesis lets an assistant search yacht charter availability, compare boats, price bookings and submit charter requests through Sedna's remote endpoint.

What you can do
  • List charter bases grouped by country and read Sedna's yacht-search guidance
  • Search yachts available for exact dates and retrieve yacht details with media links
  • Compare two to four boats on date-specific customer pricing
  • Get date-specific availability, pricing, extras and booking options for a selected yacht
  • Recalculate booking details after customer selections and submit a booking or option request
When to use it
Use it when a customer-facing assistant needs to answer yacht charter questions with real fleet, availability and price data, or to prepare and submit a charter request through Sedna.
Requirements
A remote streamable HTTP endpoint at mcp.sednasystem.com; no package, environment variables or headers are declared. Network access to the endpoint is required.
Before you install
booking_create submits a booking or option request to Sedna, so confirm customer selections before calling it. Prices must come from Sedna results rather than being calculated locally, and selections made in booking_detail_mod are not stored automatically.

Installation

In SourceWeft

  1. Open Sedna Genesis in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.sednasystem%2Fgenesis/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "sedna-genesis": {
      "type": "http",
      "url": "https://mcp.sednasystem.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

8

readme

Sedna guidance for public yacht-search conversations. 1. Yacht, fleet, availability and price facts come from Sedna tool results; do not invent them. 2. Stay neutral between fleets. Present factual differences and let the customer decide. 3. Call Base_list before search_boats so the search uses an official base. 4. Copy id_boat and id_tbf1 exactly as returned by search_boats. 5. When the customer does not state a year, clarify the date or use the current year rather than silently choosing another year. 6. When the customer asks to see yacht photos or other yacht media, call boat_details with the exact id_boat from search_boats. Display the public URLs returned in media.header, media.photos, media.plans or media.images. search_boats intentionally returns no gallery. Use booking_detail only for date-specific availability, prices, extras and booking choices. 7. A search result is available only for the requested dates reported by Sedna. Never generalize that availability to different dates.

Takes no parameters.

Base_list

Sedna yacht-search guidance and available bases. This tool lists available bases grouped by country and provides operating guidance for yacht searches. 1. Yacht, fleet, availability and price facts come from Sedna tool results; do not invent them. 2. Stay neutral between fleets and present factual differences so the customer can decide. 3. Copy `id_tbf1` and `id_boat` exactly from `search_boats` results. 4. If no year is specified, clarify the date or use the current year. 5. Call `Base_list` before `search_boats` and use the returned base name.

Takes no parameters.

boat_details

Return yacht details and CDN-backed public URLs for yacht media. This is the primary tool to call after search_boats whenever the customer asks to see yacht photos, a gallery, plans, videos or documents, or asks about layout, capacity, dimensions, equipment, description, crew or itinerary. When the client supports MCP Apps, render the attached inline Sedna gallery; otherwise display the public URLs returned under media.header, media.photos, media.plans, media.images, media.videos and media.documents. All media in this public tool comes through Sedna's CdnManager; missing CDN media is returned as an empty field and never replaced by a legacy DB URL. id_boat must be copied exactly from search_boats. This tool does not return date-specific prices, extras or availability; use booking_detail for those. Length and beam are optional fleet-supplied facts. When absent they are omitted, never returned as zero or estimated. Do not ask for either value or exclude a yacht unless the customer explicitly requires that dimension.

Parametersid_boatrequiredlanguagesheet_type

search_boats

Search Sedna for yachts available for the exact requested dates. Call Base_list first and use an official base name. Results have passed Sedna planning/block and pricing checks for start_date plus nights. If more than 30 yachts match, state the accurate count and ask for a fleet, model or year preference. If 30 or fewer match, show every result with its fleet name; never select an arbitrary subset. If none match, offer alternative bases or dates. Search results intentionally contain no yacht images. If the customer asks to see photos, a gallery, plans, videos or documents for a selected yacht, call boat_details with its exact id_boat and display the returned public media URLs. Use booking_detail for date-specific prices, extras, ports and booking choices. Length and beam are optional fleet-supplied facts. Missing values are omitted and must never exclude an otherwise matching yacht, be shown as zero, be estimated, or trigger a clarification unless the customer has explicitly made that dimension a requirement.

Parameterspaxbaserequiredpagepricenightsrequiredoptionbathroomboat_typeboat_yearboat_modelfleet_namestart_daterequired+1 more

booking_detail

Return date-specific availability, pricing, extras and booking choices. Use id_boat and id_tbf1 exactly as returned by search_boats. This tool is for a selected yacht and charter period. Do not call this tool only to see yacht photos or media; call boat_details with the exact id_boat instead. Any Images included here are supplemental booking-context images, while boat_details is the canonical source for the complete public media URLs. Show all optional extras. After the customer changes extras, passenger count, currency, ports or payment options, call booking_detail_mod and use only its server-calculated totals. When asked for the total, quote customer_cost_summary.full_customer_cost; deposits are returned separately and are not included in that amount. Finally, offer a request for an option or a request for a booking.

ParameterspaxrequireddateEndrequiredid_boatrequiredid_tbf1requireddateStartrequired

booking_detail_mod

Apply customer selections and return server-recalculated booking details. Copy id_boat and id_tbf1 from search_boats. Sedna is the only source of truth for prices: never calculate totals in the LLM. Send selected extras, passenger count, currency, ports and payment options here, then present the complete updated summary returned by the server. This is a stateless price preview and does not save the selection. If the customer proceeds, repeat the complete selected_extras list in booking_create. When the customer asks for the new total, quote customer_cost_summary.full_customer_cost. Explain payable_now and payable_at_base separately; never add them in the LLM, and keep the refundable deposit separate.

ParameterspaxrequireddateEndrequiredid_boatrequiredid_tbf1requireddateStartrequiredselected_extrasarrival_selectedcurrency_id_devisedeparture_selectedarrival_port_pay_optiondeparture_port_pay_option

booking_create

Submits a request for a booking or a request for an option. This action re-prices and submits the request. ``booking_detail_mod`` is a stateless preview: selections made there are not stored automatically. Therefore selected_extras MUST repeat every extra the customer selected, using the exact id_opt and quantity. Pass an empty list only when the customer selected no optional extras. Never report an extra as selected unless this tool's saved_extras verification confirms it. Full client details (name, email, phone) are required to submit the request. **** strong rule: AI should not guess or input customer information on its own. It must ask customers to input it on its own.

ParameterspaxrequiredmodedateEndrequiredid_boatrequiredid_tbf1requireddateStartrequiredclient_namerequiredclient_emailrequiredclient_phonerequiredselected_extrasrequiredarrival_selectedcurrency_id_devise+3 more

compare_boats

Compare 2 to 4 boats using Sedna's date-specific customer pricing. - boat_ids: list of 2..4 boat ids - pax: customer passenger count used by booking_detail pricing - currency: EUR, USD, CNY (default EUR) - start_date/end_date: optional availability window (YYYY-MM-DD) For dated comparisons, customer_cost_summary clearly separates charter price, mandatory extras, full customer cost and refundable deposit. The full customer cost comes from the same booking preview as booking_detail; the refundable deposit is always separate. Cabin fields explicitly label total, double, single and bunk cabins. Length and beam are optional fleet-supplied facts. Missing values are omitted rather than returned as zero/null or estimated, and must not make an otherwise valid yacht unavailable for comparison.

Parameterspaxrequiredboat_idsrequiredcurrencyend_datestart_date

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.