Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
ALUZZA MARINE: Japan boat trade and tide tables 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.
96/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
Japan boat trade 2011-2025, tide tables for 239 ports and past monthly weather near ports (JMA).
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http aluzza-marine-japan-boat-trade-and-tide-table-mcp https://marine.aluzza.jp/mcp/
# 2 — ask your agent for something these tools do
# list_codes, get_trade, top_partners and 5 more
ALUZZA MARINE: Japan boat trade and tide tables costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ALAll 1 server
aluzza1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 aluzza-marine-japan-boat-trade-and-tide-table-mcp https://marine.aluzza.jp/mcp/Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
8 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.
使える品目の番号と名前（日本語と英語）、データの注意を返す。最初にこれを呼ぶと間違えにくい。
No parameter schema on file.
ある年・流れ・品目の、国ごとの数量と金額（円）を返す。partner を書けばその国だけ。partner に「世界の合計」と書けば全体。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | yes | 年（2011〜2025） |
| flow | string | yes | import＝日本の輸入・export＝日本の輸出 |
| hs | string | yes | 品目の番号。例：8903（船の合計）・890332（モーターボート 7.5〜24m）・890322（セールボート 7.5〜24m）・840721（船外機）・8902（漁船）。一覧は list_codes |
| partner | string | no | 相手の国の日本語名（例：アメリカ・フランス・中国・韓国・タイ）。省くと全部の国 |
年の範囲・流れ・品目で、相手の国を数量か金額の大きい順に並べる。1 つあたりの平均の値段（円）も付ける。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| flow | string | yes | import＝日本の輸入・export＝日本の輸出 |
| hs | string | yes | 品目の番号。例：8903（船の合計）・890332（モーターボート 7.5〜24m）・890322（セールボート 7.5〜24m）・840721（船外機）・8902（漁船）。一覧は list_codes |
| year_from | integer | no | 年（2011〜2025） |
| year_to | integer | no | 年（2011〜2025） |
| by | string | no | quantity＝数量の順・value＝金額の順（省くと quantity） |
| limit | integer | no | 何か国まで（省くと 10） |
流れ・品目・相手の国の、2011〜2025 年の年ごとの数量と金額（円）を返す。partner を省くと世界の合計。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| flow | string | yes | import＝日本の輸入・export＝日本の輸出 |
| hs | string | yes | 品目の番号。例：8903（船の合計）・890332（モーターボート 7.5〜24m）・890322（セールボート 7.5〜24m）・840721（船外機）・8902（漁船）。一覧は list_codes |
| partner | string | no | 相手の国の日本語名。省くと世界の合計 |
潮見表の地点（気象庁の潮位表の 239 か所）を探す。query に地名（例：釧路・東京・横浜・博多）、region に地方（例：北海道東部・関東地方・伊豆諸島）。どちらも省くと地方の一覧と地点の数。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | 地点の名前の一部か、2 文字の地点記号（例：TK） |
| region | string | no | 地方の名前の一部 |
ある地点・ある日の満潮と干潮の時刻と潮位（cm・潮位表基準面から）、月齢、潮回り（大潮・中潮・小潮・長潮・若潮）、その日の月相を返す（2026-01-01〜2027-12-31）。days で 7 日まで続けて。include_hourly で 1 時間ごとの潮位も。気象庁の天文潮の推算で、予報ではない。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| station | string | yes | 地点の名前（例：東京・釧路）か地点記号（例：TK）。同じ名前の候補が複数あるときは候補を返す |
| date | string | yes | 日付（YYYY-MM-DD・日本の日付） |
| days | integer | no | 何日分（省くと 1） |
| include_hourly | boolean | no | 1 時間ごと（0〜23 時）の潮位も返すか（省くと false） |
いま（日本の時刻）から見た、次の満潮と次の干潮の時刻・潮位・あと何分か、いまの潮位のおよその値と上げ潮か下げ潮か、潮回りを返す。読み上げ用の短い文（speech_ja）つき。at で別の時刻も。気象庁の天文潮の推算で、予報ではない。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| station | string | yes | 地点の名前（例：東京・釧路）か地点記号（例：TK） |
| at | string | no | 日本の時刻 YYYY-MM-DDTHH:MM（省くといま） |
港（潮見表の地点）のいちばん近い気象台・測候所（40 km 以内）の、過去の月ごとの平均気温・平均風速・降水量（1991 年から・気象庁の観測）。year だけならその年の 12 か月、month だけなら毎年のその月、両方なら一つの月、どちらも省くと最新の 12 か月。過去の観測で、予報ではない。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| station | string | yes | 港の名前か地点記号（例：釧路・東京・TK）、または気象台の名前 |
| year | integer | no | 年 |
| month | integer | no | 月 |
Free
$0 forever
- 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 ALUZZA MARINE: Japan boat trade and tide tables or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.3.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestbeadf6288c8288b0f19a32066fd22e19d773a478f26ad1a8ed4a67dec3755da4
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_codes | no tags | |
| get_trade | no tags | |
| top_partners | no tags | |
| yearly_series | no tags | |
| list_tide_stations | no tags | |
| get_tide | no tags | |
| next_tide | no tags | |
| past_weather | 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
Integrityfirst-seen
Surface digestbeadf6288c8288b0
Scanned2026-10-28
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 0.3.0.
0.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish ALUZZA MARINE: Japan boat trade and tide tables can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.