# Sedna Genesis (remote · mcp.sednasystem.com)

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

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `mcp.sednasystem.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-sednasystem-genesis/mcp.md), [page](https://verifymcp.io/servers/com-sednasystem-genesis/mcp)

## Channel facts

- Endpoint: `https://mcp.sednasystem.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2162 tokens (~270/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 56/100
  - Stability check failed: schema churn in the 19 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
  - Structured output schemas are declared (13% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the Sedna Genesis MCP server?

Sedna Genesis is a hosted endpoint at https://mcp.sednasystem.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.

### Claude

```bash
claude mcp add --transport http com-sednasystem-genesis 'https://mcp.sednasystem.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-sednasystem-genesis": {
      "url": "https://mcp.sednasystem.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-sednasystem-genesis": {
      "type": "http",
      "url": "https://mcp.sednasystem.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-sednasystem-genesis]
url = "https://mcp.sednasystem.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-sednasystem-genesis": {
      "type": "remote",
      "url": "https://mcp.sednasystem.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-sednasystem-genesis --url 'https://mcp.sednasystem.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-sednasystem-genesis:
    url: "https://mcp.sednasystem.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-sednasystem-genesis": {
      "Transport": "http",
      "Url": "https://mcp.sednasystem.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-sednasystem-genesis -t streamable-http -u 'https://mcp.sednasystem.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 69, +1)

- [security] Tool “booking_detail” rewrote its description, which is the text the model reads
- [security] Tool “booking_detail_mod” rewrote its description, which is the text the model reads
- [security] Tool “search_boats” rewrote its description, which is the text the model reads
- [functional] Schema quality: good → excellent

### 2026-09-28 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 42 to 46.

### 2026-09-25 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 36 to 39.

### 2026-09-22 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 29 to 32.

### 2026-09-20 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 22 to 26.

### 2026-09-17 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 12 to 16.

## MCP tools (8)

### `readme` (~249 tokens)

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 base.
4\. Use id_boat and id_tbf1 exactly as returned by search_boats. Never guess IDs.
5\. When the customer does not state a year, clarify the date or use the
   current year. Never silently choose the following 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.

### `Base_list` (~196 tokens)

\**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. Let the customer decide.
4\.  **ID Accuracy:** MUST use exact `id_tbf1` and `id_boat` from `search_boats` results. NEVER guess.
5\.  **Current Year Default:** If no year is specified, use the CURRENT year, not next year.
6\.  **CHECK BASE FIRST:** ALWAYS use this tool (`Base_list`) to find the exact base name BEFORE calling `search_boats`.

### `boat_details` (~270 tokens)

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

Input parameters:

- `id_boat` (integer, required): Exact yacht ID returned by search_boats. Never guess it.
- `language` (string): ISO language code supported by Sedna, for example en or fr.
- `sheet_type` (string): bareboat or crewed. Use crewed for crew and itinerary data.

### `search_boats` (~392 tokens)

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.

Input parameters:

- `base` (string, required): Exact base name returned by Base_list.
- `bathroom`: Optional bathroom filter.
- `boat_model`: Optional yacht model.
- `boat_type`: Optional exact yacht type.
- `boat_year`: Optional build-year filter (exact, range or comparator).
- `double_cabin`: Optional double-cabin filter.
- `fleet_name`: Optional fleet preference.
- `nights` (integer, required): Number of charter nights.
- `option`: Additional supported Sedna filters.
- `page`: Result page starting at 1.
- `pax`: Optional passenger-capacity filter. A single number means at least that many guests; ranges and comparators are also supported.
- `price`: Optional price filter in the currency returned by Sedna.
- `start_date` (string, required): Future charter start date in YYYY-MM-DD format.

### `booking_detail` (~255 tokens)

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.

Input parameters:

- `dateEnd` (string, required): End date in DD/MM/YYYY format.
- `dateStart` (string, required): Start date in DD/MM/YYYY format.
- `id_boat` (integer, required): Exact yacht ID returned by search_boats.
- `id_tbf1` (integer, required): Exact pricing ID returned by search_boats.
- `pax` (integer, required): Number of passengers.

### `booking_detail_mod` (~308 tokens)

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.

Input parameters:

- `arrival_port_pay_option`: base or now.
- `arrival_selected`: Selected arrival port ID.
- `currency_id_devise`: Currency ID present in booking_detail rates.
- `dateEnd` (string, required): End date in DD/MM/YYYY format.
- `dateStart` (string, required): Start date in DD/MM/YYYY format.
- `departure_port_pay_option`: base or now.
- `departure_selected`: Selected departure port ID.
- `id_boat` (integer, required): Exact yacht ID returned by search_boats.
- `id_tbf1` (integer, required): Exact pricing ID returned by search_boats.
- `pax` (integer, required): Number of passengers.
- `selected_extras`: Selected extras with id_opt, selected and quantity.

### `booking_create` (~359 tokens)

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.

Input parameters:

- `arrival_port_pay_option`
- `arrival_selected`
- `client_email` (string, required): The client's valid email address.
- `client_name` (string, required): The client's full name.
- `client_phone` (string, required): The client's contact phone number.
- `currency_id_devise`
- `dateEnd` (string, required): The end date (DD/MM/YYYY).
- `dateStart` (string, required): The start date (DD/MM/YYYY).
- `departure_port_pay_option`
- `departure_selected`
- `id_boat` (integer, required): The unique boat identifier.
- `id_tbf1` (integer, required): The TBF1 identifier for the booking.
- `mode`: The type of creation, 'booking' or 'option' (defaults to 'booking').
- `pax` (integer, required): Number of passengers.
- `selected_extras` (array, required): Required complete selection. Example: [{"id_opt": 123, "selected": true, "quantity": 1}]. Use [] only when no optional extra was selected.

### `compare_boats` (~133 tokens)

Compare 2 to 4 boats side by side using Sedna's date-specific pricing.
\- boat_ids: list of 2..4 boat ids
\- currency: EUR, USD, CNY (default EUR)
\- start_date/end_date: optional availability window (YYYY-MM-DD)

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.

Input parameters:

- `boat_ids` (array, required)
- `currency` (string)
- `end_date`
- `start_date`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-sednasystem-genesis/mcp#diagnostics

## Score history

- 2026-09-29: 69
- 2026-09-28: 68
- 2026-09-27: 68
- 2026-09-26: 68
- 2026-09-25: 67
- 2026-09-24: 67
- 2026-09-23: 66
- 2026-09-22: 66
- 2026-09-21: 65
- 2026-09-20: 65
- 2026-09-19: 64
- 2026-09-18: 64
- 2026-09-17: 64
- 2026-09-16: 63
- 2026-09-15: 63
- 2026-09-14: 62
- 2026-09-13: 62
- 2026-09-12: 61
- 2026-09-11: 62
- 2026-09-10: 61

## Common questions

### What is the Sedna Genesis MCP server?

Sedna Genesis is an MCP server listed in the public MCP registry as com.sednasystem/genesis. Customer-facing yacht search and charter request MCP server by Sedna System. This page covers its hosted endpoint (https://mcp.sednasystem.com/mcp).

### Is the Sedna Genesis MCP server safe to use?

Sedna Genesis scores 69 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 Sedna Genesis MCP server expose?

Sedna Genesis exposes 8 tools: readme, Base_list, boat_details, search_boats, booking_detail, and 3 more. Their descriptions and schemas cost roughly 2,162 tokens of context every time the server is loaded.

### Does the Sedna Genesis MCP server require authentication?

No. We connected to Sedna Genesis without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Sedna Genesis MCP server still maintained?

Sedna Genesis is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.sednasystem.com/mcp
- Repository: https://github.com/eitsedna/genesis
- Website: https://genesis.sednasystem.com/landing
- Changelog RSS feed: https://verifymcp.io/servers/com-sednasystem-genesis/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-sednasystem-genesis/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-sednasystem-genesis/mcp