Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Rynda Crewing

REMOTE · CREWING.RYNDA.IO

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

Available components

+3 this week 73 Trust /100

Last scanned (19 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 13 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 69

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://crewing.rynda.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=crewing.rynda.io CN=YE2,O=Let's Encrypt,C=US 27 Oct 2026 25 Jan 2027 ECDSA 256 ECDSA-SHA384 6f84f64fdec0fff4bf4abc40b5f83a110fe
SANs: crewing.rynda.io, www.crewing.rynda.io
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of crewing.rynda.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
rynda.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://analytics.rynda.io https://js.stripe.com https://*.js.stripe.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://*.google-analytics.com https://*.googletagmanager.com https://analytics.rynda.io https://*.stripe.com https://*.link.com; connect-src 'self' https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://www.google.com https://analytics.rynda.io https://api.stripe.com https://checkout.stripe.com https://merchant-ui-api.stripe.com https://link.com https://*.link.com https://fonts.googleapis.com; frame-src 'self' https://js.stripe.com https://*.js.stripe.com https://checkout.stripe.com https://hooks.stripe.com https://link.com https://*.link.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://crewing.rynda.io/mcp Verified 200
http (plaintext) http://crewing.rynda.io/mcp HTTPS enforced 301 https://crewing.rynda.io/mcp
MCP tools · 4 exposed · ~786 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_salary_by_rank ~120

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.

NameTypeReqDescription
rankstringyesRank (position), e.g. "Chief Engineer", "Master", "2nd Officer", "AB", "Bosun", "Cook".

No output schema declared.

No examples provided.

get_vacancy ~95

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.

NameTypeReqDescription
idstringyesVacancy id ("1234" or "ext-5678") or the vacancy url.

No output schema declared.

No examples provided.

list_ranks ~54

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_vacancies ~517

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.

NameTypeReqDescription
limitinteger–Vacancies per page, 1 to 20.
min_salary_usdnumber–Minimum monthly salary in USD. Vacancies without a stated salary are left out when this is set.
pageinteger–Page of results, from 1.
rankstring–Rank (position) as people say it, e.g. "Chief Engineer", "Master", "2nd Officer", "AB", "Bosun", "Cook". Omit to search all ranks.
vessel_typestring–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…

No output schema declared.

No examples provided.

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.

remote · crewing.rynda.io

# add to Claude Code
claude mcp add --transport http ryndaglobal-vacancies 'https://crewing.rynda.io/mcp'
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.