ALUZZA MARINE: Japan boat trade and tide tables
REMOTE · MARINE.ALUZZA.JP
Japan boat trade 2011-2025, tide tables for 239 ports and past monthly weather near ports (JMA).
Available components
Last scanned (7 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1604 tokens (~200/item across 8 items; 8 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 Management37
- Stability observed for 11 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 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.
- 28 Oct 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.
- 26 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 25 Oct 26 60
First indexed and scored.
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 5 Nov 2026 · Probed https://marine.aluzza.jp/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=marine.aluzza.jp | CN=YE1,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5155808397db6bfe3c789f049db22d58783 |
| SANs: marine.aluzza.jp | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 marine.aluzza.jp. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| jp. | present | 33631 | 8 | Verified |
| aluzza.jp. | absent | 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 |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://marine.aluzza.jp/mcp/ | Verified | 200 | |
| http (plaintext) | http://marine.aluzza.jp/mcp/ | Inconclusive | 405 |
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 →
get_tide ~239
ある地点・ある日の満潮と干潮の時刻と潮位（cm・潮位表基準面から）、月齢、潮回り（大潮・中潮・小潮・長潮・若潮）、その日の月相を返す（2026-01-01〜2027-12-31）。days で 7 日まで続けて。include_hourly で 1 時間ごとの潮位も。気象庁の天文潮の推算で、予報ではない。
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | 日付（YYYY-MM-DD・日本の日付） |
| days | integer | – | 何日分（省くと 1） |
| include_hourly | boolean | – | 1 時間ごと（0〜23 時）の潮位も返すか（省くと false） |
| station | string | yes | 地点の名前（例：東京・釧路）か地点記号（例：TK）。同じ名前の候補が複数あるときは候補を返す |
No output schema declared.
No examples provided.
get_trade ~202
ある年・流れ・品目の、国ごとの数量と金額（円）を返す。partner を書けばその国だけ。partner に「世界の合計」と書けば全体。
| Name | Type | Req | Description |
|---|---|---|---|
| flow | string | yes | import＝日本の輸入・export＝日本の輸出 |
| hs | string | yes | 品目の番号。例：8903（船の合計）・890332（モーターボート 7.5〜24m）・890322（セールボート 7.5〜24m）・840721（船外機）・8902（漁船）。一覧は list_codes |
| partner | string | – | 相手の国の日本語名（例：アメリカ・フランス・中国・韓国・タイ）。省くと全部の国 |
| year | integer | yes | 年（2011〜2025） |
No output schema declared.
No examples provided.
list_codes ~47
使える品目の番号と名前（日本語と英語）、データの注意を返す。最初にこれを呼ぶと間違えにくい。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tide_stations ~131
潮見表の地点（気象庁の潮位表の 239 か所）を探す。query に地名（例：釧路・東京・横浜・博多）、region に地方（例：北海道東部・関東地方・伊豆諸島）。どちらも省くと地方の一覧と地点の数。
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | 地点の名前の一部か、2 文字の地点記号（例：TK） |
| region | string | – | 地方の名前の一部 |
No output schema declared.
No examples provided.
next_tide ~164
いま（日本の時刻）から見た、次の満潮と次の干潮の時刻・潮位・あと何分か、いまの潮位のおよその値と上げ潮か下げ潮か、潮回りを返す。読み上げ用の短い文（speech_ja）つき。at で別の時刻も。気象庁の天文潮の推算で、予報ではない。
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | 日本の時刻 YYYY-MM-DDTHH:MM（省くといま） |
| station | string | yes | 地点の名前（例：東京・釧路）か地点記号（例：TK） |
No output schema declared.
No examples provided.
past_weather ~172
港（潮見表の地点）のいちばん近い気象台・測候所（40 km 以内）の、過去の月ごとの平均気温・平均風速・降水量（1991 年から・気象庁の観測）。year だけならその年の 12 か月、month だけなら毎年のその月、両方なら一つの月、どちらも省くと最新の 12 か月。過去の観測で、予報ではない。
| Name | Type | Req | Description |
|---|---|---|---|
| month | integer | – | 月 |
| station | string | yes | 港の名前か地点記号（例：釧路・東京・TK）、または気象台の名前 |
| year | integer | – | 年 |
No output schema declared.
No examples provided.
top_partners ~226
年の範囲・流れ・品目で、相手の国を数量か金額の大きい順に並べる。1 つあたりの平均の値段（円）も付ける。
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | quantity＝数量の順・value＝金額の順（省くと quantity） |
| flow | string | yes | import＝日本の輸入・export＝日本の輸出 |
| hs | string | yes | 品目の番号。例：8903（船の合計）・890332（モーターボート 7.5〜24m）・890322（セールボート 7.5〜24m）・840721（船外機）・8902（漁船）。一覧は list_codes |
| limit | integer | – | 何か国まで（省くと 10） |
| year_from | integer | – | 年（2011〜2025） |
| year_to | integer | – | 年（2011〜2025） |
No output schema declared.
No examples provided.
yearly_series ~170
流れ・品目・相手の国の、2011〜2025 年の年ごとの数量と金額（円）を返す。partner を省くと世界の合計。
| Name | Type | Req | Description |
|---|---|---|---|
| flow | string | yes | import＝日本の輸入・export＝日本の輸出 |
| hs | string | yes | 品目の番号。例：8903（船の合計）・890332（モーターボート 7.5〜24m）・890322（セールボート 7.5〜24m）・840721（船外機）・8902（漁船）。一覧は list_codes |
| partner | string | – | 相手の国の日本語名。省くと世界の合計 |
No output schema declared.
No examples provided.
How do I install the ALUZZA MARINE: Japan boat trade and tide tables MCP server?
ALUZZA MARINE: Japan boat trade and tide tables is a hosted endpoint at https://marine.aluzza.jp/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 · marine.aluzza.jp
claude mcp add --transport http jp-aluzza-marine 'https://marine.aluzza.jp/mcp/'
What is the ALUZZA MARINE: Japan boat trade and tide tables MCP server?
ALUZZA MARINE: Japan boat trade and tide tables is an MCP server listed in the public MCP registry as jp.aluzza/marine. Japan boat trade 2011-2025, tide tables for 239 ports and past monthly weather near ports (JMA). This page covers its hosted endpoint (https://marine.aluzza.jp/mcp/).
Is the ALUZZA MARINE: Japan boat trade and tide tables MCP server safe to use?
ALUZZA MARINE: Japan boat trade and tide tables scores 65 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 ALUZZA MARINE: Japan boat trade and tide tables MCP server expose?
ALUZZA MARINE: Japan boat trade and tide tables exposes 8 tools: list_codes, get_trade, top_partners, yearly_series, list_tide_stations, and 3 more. Their descriptions and schemas cost roughly 1,351 tokens of context every time the server is loaded.
Does the ALUZZA MARINE: Japan boat trade and tide tables MCP server require authentication?
No. We connected to ALUZZA MARINE: Japan boat trade and tide tables without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ALUZZA MARINE: Japan boat trade and tide tables MCP server still maintained?
ALUZZA MARINE: Japan boat trade and tide tables is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.