Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Krew Guru is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Maritime vacancies for seafarers and CV import into a Krew Guru profile.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http krew-guru-mcp https://api.krew.guru/mcp
# 2 — ask your agent for something these tools do
# search_maritime_jobs, get_maritime_job, create_seafarer_profile_draft and 1 more
Krew Guru costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http krew-guru-mcp https://api.krew.guru/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search open vacancies for seafarers on Krew Guru by rank, vessel type and boarding date. Use this when a seafarer asks which jobs are open, for example "2/E jobs on bulk carriers joining in November" or "AB vacancies on tankers". Returns up to 20 published vacancies with a boarding date that has not passed, salary range in USD per month (net), contract length in months and a vacancy_url to open th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rank | string | no | Rank (position on board). Use the full name or a short code, for example: Master; Chief Officer (CO, C/O); Second Officer (2O, 2/O); Chief Engineer (CE, C/E); Second Engineer (2E, 2/E); Third Engineer |
| ship_type | string | no | Vessel type, for example: Bulk carrier, Container ship, Oil tanker, Product tanker, Chemical tanker, LNG carrier, LPG carrier, General cargo vessel, Car carrier, AHTS (anchor handling tug supply), PSV |
| date_of_boarding | string | no | Planned joining date, YYYY-MM-DD. Matches vacancies boarding within one week of this date. |
| limit | integer | no | How many vacancies to return (1-20). |
| offset | integer | no | Skip this many vacancies (paging). |
Get the details of one Krew Guru vacancy by its vac_id: rank, vessel type and size, salary range in USD per month (net), contract length, boarding date and port, requirements (citizenship, English level, certificates, visas) and a vacancy_url to open it on krew.guru. Use this when the seafarer wants more about a vacancy returned by search_maritime_jobs or by create_seafarer_profile_draft (matched_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vac_id | string | yes | Vacancy id (vac_id) from search_maritime_jobs or matched_vacancies. |
Turn a seafarer CV (plain text the seafarer pasted or shared: sea service records, ranks, vessels, certificates) into a Krew Guru profile draft. Sends a sign-in code and link to the email in the CV (or to the email argument if the CV has none); the seafarer opens the email and enters the code on krew.guru to save the profile; no tool accepts that code. Returns the same result as the Krew Guru webs
| Parameter | Type | Required | Notes |
|---|---|---|---|
| raw_cv_text | string | yes | Full CV text as provided by the seafarer, 40-48,000 characters, any language. Keep sea service records (vessel name, IMO, type, rank, dates). |
| string | no | The seafarer's own email. Only needed after status email_required; an email found in the CV is used first. |
Check a Krew Guru profile draft by its draft_token from create_seafarer_profile_draft: status (verification_sent or email_required), masked email, CV preview without contacts, handoff_url and matched_vacancies. Use this when the seafarer comes back later and asks about the draft or the matched vacancies. An unknown or expired token returns an error; then create a new draft. Do not use for signing
| Parameter | Type | Required | Notes |
|---|---|---|---|
| draft_token | string | yes | draft_token returned by create_seafarer_profile_draft (64 hex characters). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Krew Guru or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_maritime_jobs | no tags | |
| get_maritime_job | no tags | |
| create_seafarer_profile_draft | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_profile_draft_status | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Krew Guru can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.