Remote MCP · Endpoint
Sedna Genesis MCP server
No. Sedna Genesis answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mcp.sednasystem.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.sednasystem/genesis
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 251 ms
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 66.7% from 18 checks
- Described by its publisher as
- Customer-facing yacht search and charter request MCP server by Sedna System.
- Repository
- https://github.com/eitsedna/genesis
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 251 ms |
| 1 day ago | Handshake completed | 327 ms |
| 2 days ago | Handshake completed | 263 ms |
| 3 days ago | Handshake completed | 517 ms |
| 4 days ago | Handshake completed | 538 ms |
| 5 days ago | Handshake completed | 254 ms |
| 7 days ago | Handshake completed | 252 ms |
| 9 days ago | Handshake completed | 252 ms |
| 12 days ago | Handshake completed | 288 ms |
| 14 days ago | Handshake completed | 250 ms |
| 16 days ago | Handshake completed | 1.14 s |
| 18 days ago | Handshake completed | 255 ms |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 22 days ago | Failed - the server returned an HTTP error | — |
| 24 days ago | Failed - the server returned an HTTP error | — |
| 26 days ago | Failed - the server returned an HTTP error | — |
| 27 days ago | Failed - the server returned an HTTP error | — |
| 29 days ago | Failed - the server returned an HTTP error | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 22 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with Sedna Genesis and makes no claim about it beyond what these checks measured.