rynda-crewing
Registry code: d9a6180f479dd7f1
Rynda Crewing is a hiring platform for seafarers, shipowners and crewing agencies. These tools return live public data: open vacancies with pay, contract, joining date and vessel, and what employers offer per rank. Each vacancy comes with the url of its public page, where the seafarer reads the full vacancy and applies. Pay is per month; a figure marked ≈ was converted from another currency. Vacancies open and close every day, and the tools return their state at the moment of the call.
- endpoint
- https://crewing.rynda.io/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is rynda-crewing live?
- Yes — it answered the hub's last check (checked 14h ago). It answered 100% of checks over the last 30 days.
- Is rynda-crewing free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does rynda-crewing have?
- 4 tools: get_vacancy, get_salary_by_rank, search_vacancies, list_ranks.
- Is rynda-crewing safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
search_vacancies open 14h ago
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.
{ "type": "object", "properties": { "page": { "type": "integer", "default": 1, "maximum": 100, "minimum": 1, "description": "Page of results, from 1." }, "rank": { "type": "string", "description": "Rank (position) as people say it, e.g. \"Chief Engineer\", \"Master\", \"2nd Officer\", \"AB\", \"Bosun\", \"Cook\". Omit to search all ranks." }, "limit": { "type": "integer", "default": 10, "maximum": 20, "minimum": 1, "description": "Vacancies per page, 1 to 20." }, "vessel_type": { "enum": [ "tanker", "tanker_oil", "tanker_product", "tanker_chemical", "tanker_bunker", "gas", "dry", "dry_bulk", "dry_general", "dry_heavy_lift", "dry_cement", "container", "reefer", "roro", "passenger", "passenger_cruise", "passenger_ferry", "offshore", "offshore_supply", "offshore_construction", "offshore_drilling", "offshore_crew_boat", "offshore_survey", "tug", "tug_towing", "tug_pusher", "dredging", "fishing", "research", "icebreaker", "service" ], "type": "string", "description": "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; tanker_bunker = Tankers: Bunkering; gas = Gas carriers; dry = Dry cargo ships; dry_bulk = Dry cargo ships: Bulk carriers; dry_general = Dry cargo ships: General cargo and MPP; dry_heavy_lift = Dry cargo ships: Heavy-lift; dry_cement = Dry cargo ships: Cement carriers; container = Container ships; reefer = Reefers; roro = Ro-Ro and car carriers; passenger = Passenger ships and ferries; passenger_cruise = Passenger ships and ferries: Cruise; passenger_ferry = Passenger ships and ferries: Ferries and Ro-Pax; offshore = Offshore; offshore_supply = Offshore: PSV and AHTS; offshore_construction = Offshore: Construction and DSV; offshore_drilling = Offshore: Drilling and FPSO; offshore_crew_boat = Offshore: Crew boats; offshore_survey = Offshore: Survey; tug = Tugs and pushers; tug_towing = Tugs and pushers: Tugs; tug_pusher = Tugs and pushers: Pushers; dredging = Dredgers and technical fleet; fishing = Fishing vessels; research = Research vessels; icebreaker = Icebreakers; service = Service vessels." }, "min_salary_usd": { "type": "number", "minimum": 0, "description": "Minimum monthly salary in USD. Vacancies without a stated salary are left out when this is set." } } }arguments 65 lineslist_ranks open 14h ago
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.
{ "type": "object", "properties": {} }arguments 4 linesget_vacancy unknown 14h ago
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.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Vacancy id (\"1234\" or \"ext-5678\") or the vacancy url." } } }arguments 12 linesget_salary_by_rank unknown 41h ago
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.
{ "type": "object", "required": [ "rank" ], "properties": { "rank": { "type": "string", "description": "Rank (position), e.g. \"Chief Engineer\", \"Master\", \"2nd Officer\", \"AB\", \"Bosun\", \"Cook\"." } } }arguments 12 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idd9a6180f479dd7f1.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d9a6180f479dd7f1/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d9a6180f479dd7f1?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.