# SeaReady (remote · seaready.net)

Ship inspection readiness: SIRE 2.0 prep questions, PSC checklists, upcoming vetting changes.

- Trust score: 68/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `seaready.net`: 68/100 (this document), [markdown](https://verifymcp.io/servers/net-seaready-seaready/seaready.md), [page](https://verifymcp.io/servers/net-seaready-seaready/seaready)

## Channel facts

- Endpoint: `https://seaready.net/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-10-18.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 81/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 402 tokens (~134/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the SeaReady MCP server?

SeaReady is a hosted endpoint at https://seaready.net/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 net-seaready-seaready 'https://seaready.net/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "net-seaready-seaready": {
      "url": "https://seaready.net/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "net-seaready-seaready": {
      "type": "http",
      "url": "https://seaready.net/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.net-seaready-seaready]
url = "https://seaready.net/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add net-seaready-seaready --url 'https://seaready.net/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  net-seaready-seaready:
    url: "https://seaready.net/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "net-seaready-seaready": {
      "Transport": "http",
      "Url": "https://seaready.net/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-seaready-seaready -t streamable-http -u 'https://seaready.net/mcp'
```

### Other

```json
{
  "mcpServers": {
    "net-seaready-seaready": {
      "type": "http",
      "url": "https://seaready.net/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-10-16 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 66, +5)

- [security improvement] HTTPS: unverified → pass

### 2026-10-12 (score 61, +1)

- [security] Tool “psc_checklist” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail

### 2026-10-09 (score 60)

First indexed and scored.

## MCP tools (3)

### `sire_question_lookup` (~126 tokens)

SIRE 2.0 preparation question lookup

Search SeaReady's original-wording SIRE 2.0 preparation question bank (12 chapters). Returns what good looks like, the evidence an inspector expects and common negative grounds. Not OCIMF text — for preparation only.

Input parameters:

- `chapter` (integer): Optional SIRE 2.0 chapter number to limit the search.
- `limit` (integer): Maximum results (default 5).
- `query` (string, required): Words to search for, e.g. "mooring", "enclosed space", "passage plan". Or a question id like "9.2".

### `psc_checklist` (~143 tokens)

Port State Control preparation checklist

Port State Control preparation items for one deficiency area (an area id such as "cert", "crew", "fire", "lsa", "nav", "mach", "pol1", "ism", "isps" — or words from the area title such as "certificates" or "fire safety"). Call without "area" to list the 24 areas. Items flagged detainableHint are commonly a ground for detention; items marked demonstrate are tests the PSC officer asks the crew to run; items with a pack apply only to the ship types listed.

Input parameters:

- `area` (string): Area id or words from its title. Omit to list areas.

### `inspection_deadlines` (~62 tokens)

Upcoming inspection-regime changes

Known upcoming dates in vetting and PSC regimes (e.g. concentrated inspection campaigns, RightShip rule changes) with days remaining, plus when SeaReady last verified each module.

Input parameters:

- `within_days` (integer): Only changes within this many days (default 365).

## Diagnostics

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

## Score history

- 2026-10-18: 68
- 2026-10-17: 68
- 2026-10-16: 68
- 2026-10-15: 67
- 2026-10-14: 67
- 2026-10-13: 66
- 2026-10-12: 61
- 2026-10-10: 60
- 2026-10-09: 60

## Common questions

### What is the SeaReady MCP server?

SeaReady is an MCP server listed in the public MCP registry as net.seaready/seaready. Ship inspection readiness: SIRE 2.0 prep questions, PSC checklists, upcoming vetting changes. This page covers its hosted endpoint (https://seaready.net/mcp).

### Is the SeaReady MCP server safe to use?

SeaReady scores 68 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 SeaReady MCP server expose?

SeaReady exposes 3 tools: sire_question_lookup, psc_checklist, inspection_deadlines. Their descriptions and schemas cost roughly 331 tokens of context every time the server is loaded.

### Does the SeaReady MCP server require authentication?

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

### Is the SeaReady MCP server still maintained?

SeaReady is still listed as active in the MCP registry. We last reached this channel on 18 October 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://seaready.net/mcp
- Website: https://seaready.net/
- Changelog RSS feed: https://verifymcp.io/servers/net-seaready-seaready/seaready.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-seaready-seaready/seaready.json
- HTML version of this page: https://verifymcp.io/servers/net-seaready-seaready/seaready