# Rynda Crewing (remote · crewing.rynda.io)

Open seafarer vacancies on Rynda Crewing: pay, contract, joining date, vessel and pay per rank.

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

## Components

- remote · `crewing.rynda.io`: 73/100 (this document), [markdown](https://verifymcp.io/servers/ryndaglobal-vacancies/crewing.md), [page](https://verifymcp.io/servers/ryndaglobal-vacancies/crewing)

## Channel facts

- Endpoint: `https://crewing.rynda.io/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-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 895 tokens (~223/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Rynda Crewing MCP server?

Rynda Crewing is a hosted endpoint at https://crewing.rynda.io/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 ryndaglobal-vacancies 'https://crewing.rynda.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ryndaglobal-vacancies": {
      "url": "https://crewing.rynda.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ryndaglobal-vacancies": {
      "type": "http",
      "url": "https://crewing.rynda.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ryndaglobal-vacancies]
url = "https://crewing.rynda.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ryndaglobal-vacancies": {
      "type": "remote",
      "url": "https://crewing.rynda.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ryndaglobal-vacancies --url 'https://crewing.rynda.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ryndaglobal-vacancies:
    url: "https://crewing.rynda.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ryndaglobal-vacancies": {
      "Transport": "http",
      "Url": "https://crewing.rynda.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ryndaglobal-vacancies -t streamable-http -u 'https://crewing.rynda.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ryndaglobal-vacancies": {
      "type": "http",
      "url": "https://crewing.rynda.io/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-11-20 (score 73, +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-11-17 (score 72, +1)

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

### 2026-11-15 (score 71, +1)

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

### 2026-11-13 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 69)

First indexed and scored.

## MCP tools (4)

### `search_vacancies` (~517 tokens)

Search seafarer vacancies

Search open vacancies for seafarers on Rynda Crewing. The order is the same for every employer and does not depend on paid plans. Filter by rank, vessel type and minimum monthly salary in USD. Returns up to 20 vacancies per call with pay, contract, joining date and port, vessel, employer and the url of the vacancy page, where the seafarer applies, plus the total number found; use page for more.

Input parameters:

- `limit` (integer): Vacancies per page, 1 to 20.
- `min_salary_usd` (number): Minimum monthly salary in USD. Vacancies without a stated salary are left out when this is set.
- `page` (integer): Page of results, from 1.
- `rank` (string): Rank (position) as people say it, e.g. "Chief Engineer", "Master", "2nd Officer", "AB", "Bosun", "Cook". Omit to search all ranks.
- `vessel_type` (string): Vessel type code. A group code (e.g. tanker) includes all its subtypes. tanker = Tankers; tanker_oil = Tankers: Crude oil; tanker_product = Tankers: Product; tanker_chemical = Tankers: Chemical; tank…

### `get_vacancy` (~95 tokens)

Vacancy details

Full public details of one vacancy: description, requirements (sea service, languages, certificates, visas), vessel particulars, benefits, contract and pay, the employer and how to apply. Accepts the id or the url returned by search_vacancies. A vacancy that is closed is reported as not found.

Input parameters:

- `id` (string, required): Vacancy id ("1234" or "ext-5678") or the vacancy url.

### `get_salary_by_rank` (~120 tokens)

Salary by rank

What employers offer a rank in vacancies on Rynda Crewing: median monthly pay in USD and the middle half of the range (25th to 75th percentile), each with the number of vacancies and companies behind it, the typical contract, the report period, and how many vacancies of the rank are open now. These are employer offers, not seafarer expectations.

Input parameters:

- `rank` (string, required): Rank (position), e.g. "Chief Engineer", "Master", "2nd Officer", "AB", "Bosun", "Cook".

### `list_ranks` (~54 tokens)

Ranks with open vacancies

Ranks that have open vacancies on Rynda Crewing right now, how many each, with the page that lists them. Use it to answer what jobs are available or to pick a rank name for search_vacancies.

## Diagnostics

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

## Score history

- 2026-11-21: 73
- 2026-11-20: 73
- 2026-11-19: 72
- 2026-11-18: 72
- 2026-11-17: 72
- 2026-11-16: 71
- 2026-11-15: 71
- 2026-11-14: 70
- 2026-11-13: 70
- 2026-11-12: 69

## Common questions

### What is the Rynda Crewing MCP server?

Rynda Crewing is an MCP server listed in the public MCP registry as io.github.RyndaGlobal/vacancies. Open seafarer vacancies on Rynda Crewing: pay, contract, joining date, vessel and pay per rank. This page covers its hosted endpoint (https://crewing.rynda.io/mcp).

### Is the Rynda Crewing MCP server safe to use?

Rynda Crewing scores 73 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 Rynda Crewing MCP server expose?

Rynda Crewing exposes 4 tools: search_vacancies, get_vacancy, get_salary_by_rank, list_ranks. Their descriptions and schemas cost roughly 786 tokens of context every time the server is loaded.

### Does the Rynda Crewing MCP server require authentication?

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

### Is the Rynda Crewing MCP server still maintained?

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

### What did VerifyMCP test on the Rynda Crewing MCP server?

VerifyMCP ran 13 checks on Rynda Crewing, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://crewing.rynda.io/mcp
- Website: https://crewing.rynda.io/en/help#general-ai-assistants
- Changelog RSS feed: https://verifymcp.io/servers/ryndaglobal-vacancies/crewing.xml
- Changelog JSON feed: https://verifymcp.io/servers/ryndaglobal-vacancies/crewing/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ryndaglobal-vacancies/crewing.json
- HTML version of this page: https://verifymcp.io/servers/ryndaglobal-vacancies/crewing
