Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Sedna Genesis is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Customer-facing yacht search and charter request MCP server by Sedna System.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http sedna-genesis-mcp https://mcp.sednasystem.com/mcp
# 2 — ask your agent for something these tools do
# readme, Base_list, boat_details and 5 more
Sedna Genesis costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http sedna-genesis-mcp https://mcp.sednasystem.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Official Sedna rules for every public yacht-search conversation. 1. Use only information returned by Sedna tools. Do not supplement yacht, fleet, availability or price data with an internet search. 2. Stay neutral between fleets. Present factual differences and let the customer decide; never promote one fleet as the best. 3. Call Base_list before search_boats so the search uses an official
No parameter schema on file.
Sedna System Rules & Available Bases This tool provides the OFFICIAL rules and the COMPLETE list of available bases grouped by country for boat searching. AI GUIDELINES (MUST FOLLOW): 1. Sedna-Only Data: Use ONLY data from Sedna tools. NO internet searches. 2. Fleet Neutrality: Remain 100% neutral. DO NOT favor any fleet. 3. Customer-Led Decision: Present facts objectively
No parameter schema on file.
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 UR
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id_boat | integer | yes | Exact yacht ID returned by search_boats. Never guess it. |
| sheet_type | string | no | bareboat or crewed. Use crewed for crew and itinerary data. |
| language | string | no | ISO language code supported by Sedna, for example en or fr. |
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 subse
| Parameter | Type | Required | Notes |
|---|---|---|---|
| base | string | yes | Exact base name returned by Base_list. |
| start_date | string | yes | Future charter start date in YYYY-MM-DD format. |
| nights | integer | yes | Number of charter nights. |
| boat_type | no | Optional exact yacht type. | |
| boat_model | no | Optional yacht brand, partial model or complete model. For example, "Lagoon" matches Lagoon 380, Lagoon 40 and Lagoon 42; "Lagoon 42" also matches directly. | |
| fleet_name | no | Optional fleet preference. | |
| pax | no | Optional passenger-capacity filter. A single number means at least that many guests; ranges and comparators are also supported. | |
| boat_year | no | Optional build-year filter (exact, range or comparator). | |
| double_cabin | no | Optional double-cabin filter. | |
| bathroom | no | Optional bathroom filter. | |
| price | no | Optional price filter in the currency returned by Sedna. | |
| option | no | Additional supported Sedna filters. | |
| page | no | Result page starting at 1. |
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 sou
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id_tbf1 | integer | yes | Exact pricing ID returned by search_boats. |
| id_boat | integer | yes | Exact yacht ID returned by search_boats. |
| dateStart | string | yes | Start date in DD/MM/YYYY format. |
| dateEnd | string | yes | End date in DD/MM/YYYY format. |
| pax | integer | yes | Number of passengers. |
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id_tbf1 | integer | yes | Exact pricing ID returned by search_boats. |
| id_boat | integer | yes | Exact yacht ID returned by search_boats. |
| dateStart | string | yes | Start date in DD/MM/YYYY format. |
| dateEnd | string | yes | End date in DD/MM/YYYY format. |
| pax | integer | yes | Number of passengers. |
| selected_extras | no | Selected extras with id_opt, selected and quantity. | |
| currency_id_devise | no | Currency ID present in booking_detail rates. | |
| departure_selected | no | Selected departure port ID. | |
| arrival_selected | no | Selected arrival port ID. | |
| departure_port_pay_option | no | base or now. | |
| arrival_port_pay_option | no | base or now. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_name | string | yes | The client's full name. |
| client_email | string | yes | The client's valid email address. |
| client_phone | string | yes | The client's contact phone number. |
| id_tbf1 | integer | yes | The TBF1 identifier for the booking. |
| id_boat | integer | yes | The unique boat identifier. |
| dateStart | string | yes | The start date (DD/MM/YYYY). |
| dateEnd | string | yes | The end date (DD/MM/YYYY). |
| pax | integer | yes | Number of passengers. |
| selected_extras | array | yes | Required complete selection. Example: [{"id_opt": 123, "selected": true, "quantity": 1}]. Use [] only when no optional extra was selected. |
| mode | no | The type of creation, 'booking' or 'option' (defaults to 'booking'). | |
| currency_id_devise | no | — | |
| departure_selected | no | — | |
| arrival_selected | no | — | |
| departure_port_pay_option | no | — | |
| arrival_port_pay_option | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| boat_ids | array | yes | — |
| pax | integer | yes | — |
| currency | string | no | — |
| start_date | no | — | |
| end_date | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Sedna Genesis or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Sedna Genesis can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.