MCP servers › jp.aluzza › marine
MCP server · registry snapshot 2026-10-26 · last tested 2026-10-26
jp.aluzza/marine
ALUZZA MARINE: Japan boat trade and tide tables — the publisher's title
by aluzza.jp · domain (the registry's namespace rule)Website ↗
Japan boat trade 2011-2025, tide tables for 239 ports and past monthly weather near ports (JMA). — the publisher's description
Summary
jp.aluzza/marine is a remote MCP server listed in the official MCP registry at version 0.3.0, under the namespace of the domain aluzza.jp. On 2026-10-26 ProtocolProbe connected to it in read-only mode and read its inventory: 8 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Tools
- 8
- Last tested
- 2026-10-26
Tool list size
2,640 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (8 tools). Counted with Anthropic's token counter on 2026-10-26, from the tool list we read on 2026-10-26. Median across 23,424 counted servers: 2,725 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-10-26 (marine.aluzza.jp), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (0.3.0).
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-26
- Mode
- read-only (no tool calls)
- Latest version
- 0.3.0, published 2026-10-25 (registry, as of the 2026-10-26 snapshot)
- First listed version
- 2026-10-25 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, all on 2026-10-25; 2 in the 90 days before the 2026-10-26 snapshot.(versions still listed in the registry only)
Most recent 2 versions
0.3.0· 2026-10-250.2.0· 2026-10-25
- Registry data
- snapshot 2026-10-26
- Package and repository
- checked 2026-10-26
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-10-24, listed on 2026-10-26 with version 0.3.0 (published 2026-10-25).
Source: the official MCP Registry list on 2026-10-24 and on 2026-10-26.
What it is
What does this server offer?
Observed inventoryNone of its 8 tools are described as changing anything. For 8 the reading was uncertain, so no mark is shown.
- list_codeson 2 other servers
“使える品目の番号と名前(日本語と英語)、データの注意を返す。最初にこれを呼ぶと間違えにくい。”
Takes no inputs.
- get_tradeon 1 other server
“ある年・流れ・品目の、国ごとの数量と金額(円)を返す。partner を書けばその国だけ。partner に「世界の合計」と書けば全体。”
4 inputs, 3 required
yearintegerrequired“年(2011〜2025)”flowstringrequired“import=日本の輸入・export=日本の輸出”hsstringrequired“品目の番号。例:8903(船の合計)・890332(モーターボート 7.5〜24m)・890322(セールボート 7.5〜24m)・840721(船外機)・8902(漁船)。一覧は list_codes”partnerstring“相手の国の日本語名(例:アメリカ・フランス・中国・韓国・タイ)。省くと全部の国”
- top_partners
“年の範囲・流れ・品目で、相手の国を数量か金額の大きい順に並べる。1 つあたりの平均の値段(円)も付ける。”
6 inputs, 2 required
flowstringrequired“import=日本の輸入・export=日本の輸出”hsstringrequired“品目の番号。例:8903(船の合計)・890332(モーターボート 7.5〜24m)・890322(セールボート 7.5〜24m)・840721(船外機)・8902(漁船)。一覧は list_codes”year_frominteger“年(2011〜2025)”year_tointeger“年(2011〜2025)”bystring“quantity=数量の順・value=金額の順(省くと quantity)”limitinteger“何か国まで(省くと 10)”
- yearly_series
“流れ・品目・相手の国の、2011〜2025 年の年ごとの数量と金額(円)を返す。partner を省くと世界の合計。”
3 inputs, 2 required
flowstringrequired“import=日本の輸入・export=日本の輸出”hsstringrequired“品目の番号。例:8903(船の合計)・890332(モーターボート 7.5〜24m)・890322(セールボート 7.5〜24m)・840721(船外機)・8902(漁船)。一覧は list_codes”partnerstring“相手の国の日本語名。省くと世界の合計”
- list_tide_stations
“潮見表の地点(気象庁の潮位表の 239 か所)を探す。query に地名(例:釧路・東京・横浜・博多)、region に地方(例:北海道東部・関東地方・伊豆諸島)。どちらも省くと地方の一覧と地点の数。”
2 inputs
querystring“地点の名前の一部か、2 文字の地点記号(例:TK)”regionstring“地方の名前の一部”
- get_tideon 1 other server
“ある地点・ある日の満潮と干潮の時刻と潮位(cm・潮位表基準面から)、月齢、潮回り(大潮・中潮・小潮・長潮・若潮)、その日の月相を返す(2026-01-01〜2027-12-31)。days で 7 日まで続けて。include_hourly で 1 時間ごとの潮位も。気象庁の天文潮の推算で、予報ではない。”
4 inputs, 2 required
stationstringrequired“地点の名前(例:東京・釧路)か地点記号(例:TK)。同じ名前の候補が複数あるときは候補を返す”datestringrequired“日付(YYYY-MM-DD・日本の日付)”daysinteger“何日分(省くと 1)”include_hourlyboolean“1 時間ごと(0〜23 時)の潮位も返すか(省くと false)”
- next_tide
“いま(日本の時刻)から見た、次の満潮と次の干潮の時刻・潮位・あと何分か、いまの潮位のおよその値と上げ潮か下げ潮か、潮回りを返す。読み上げ用の短い文(speech_ja)つき。at で別の時刻も。気象庁の天文潮の推算で、予報ではない。”
2 inputs, 1 required
stationstringrequired“地点の名前(例:東京・釧路)か地点記号(例:TK)”atstring“日本の時刻 YYYY-MM-DDTHH:MM(省くといま)”
- past_weather
“港(潮見表の地点)のいちばん近い気象台・測候所(40 km 以内)の、過去の月ごとの平均気温・平均風速・降水量(1991 年から・気象庁の観測)。year だけならその年の 12 か月、month だけなら毎年のその月、両方なら一つの月、どちらも省くと最新の 12 か月。過去の観測で、予報ではない。”
3 inputs, 1 required
stationstringrequired“港の名前か地点記号(例:釧路・東京・TK)、または気象台の名前”yearinteger“年”monthinteger“月”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-26.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 100% of 24
- Tools with a description
- 100% of 8
- Typical description length
- 93 characters
The tool set
Counted from the listing
- Tools
- 8
- Size of the list
- about 925 tokens for an agent to load (characters ÷ 4)
- Naming
- 8 of 8 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 8 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-26 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://marine.aluzza.jp/mcp/
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"marine": {
"url": "https://marine.aluzza.jp/mcp/"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"marine": {
"type": "http",
"url": "https://marine.aluzza.jp/mcp/"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"marine","type":"http","url":"https://marine.aluzza.jp/mcp/"}'Claude Code
claude mcp add --transport http marine https://marine.aluzza.jp/mcp/
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"marine": {
"type": "streamableHttp",
"url": "https://marine.aluzza.jp/mcp/",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"marine": {
"httpUrl": "https://marine.aluzza.jp/mcp/"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.marine] url = "https://marine.aluzza.jp/mcp/"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"marine": {
"url": "https://marine.aluzza.jp/mcp/"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://marine.aluzza.jp/mcp/ --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint marine.aluzza.jp/mcp/ | Session opened | matches | our test · 2026-10-26 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-26 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-26. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about jp.aluzza/marine
Answered from the data aboveWho publishes jp.aluzza/marine?
The registry ties the namespace jp.aluzza to the domain aluzza.jp; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Does jp.aluzza/marine need an API key or sign-in?
It opened a session without any credential on 2026-10-26. The registry entry declares no required credential; no declaration is not a guarantee.
Has jp.aluzza/marine been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (we call no server's tools)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-10-26, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,658 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 8 tools, 0 resources, 0 prompts.
- 4,264 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “jp.aluzza/marine: MCP server record.” Data checked 2026-10-26. https://protocolprobe.com/mcp/servers/jp.aluzza/marine
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/jp.aluzza/marine)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology