Yamagishi Sync Lab MCP server
Which MCP servers are Yamagishi Sync Lab's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-29
- Registry namejp.aluzza/marineverified in the MCP registry
The registry name sits under aluzza.jp. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-29
- Tools8
- Server calls itselfaluzza-marine
- Server version0.3.0
- Protocol version2025-06-18
On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 607 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 5 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
- Answeredmeasuring5 of the 7 daily checks it takes to print a share
- Median first answer513 ms
- Space in an agent's context≈ 927 tokensthe definitions of all its tools (8), which an agent carries on every turn
- Tool definitionsB · 83 of 100
- Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once
- Not saying whether it only reads or can destroy: 8 of 8
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
list_codes使える品目の番号と名前(日本語と英語)、データの注意を返す。最初にこれを呼ぶと間違えにくい。
get_tradeある年・流れ・品目の、国ごとの数量と金額(円)を返す。partner を書けばその国だけ。partner に「世界の合計」と書けば全体。
top_partners年の範囲・流れ・品目で、相手の国を数量か金額の大きい順に並べる。1 つあたりの平均の値段(円)も付ける。
yearly_series流れ・品目・相手の国の、2011〜2025 年の年ごとの数量と金額(円)を返す。partner を省くと世界の合計。
list_tide_stations潮見表の地点(気象庁の潮位表の 239 か所)を探す。query に地名(例:釧路・東京・横浜・博多)、region に地方(例:北海道東部・関東地方・伊豆諸島)。どちらも省くと地方の一覧と地点の数。
get_tideある地点・ある日の満潮と干潮の時刻と潮位(cm・潮位表基準面から)、月齢、潮回り(大潮・中潮・小潮・長潮・若潮)、その日の月相を返す(2026-01-01〜2027-12-31)。days で 7 日まで続けて。include_hourly で 1 時間ごとの潮位も。気象庁の天文潮の推算で、予報ではない。
next_tideいま(日本の時刻)から見た、次の満潮と次の干潮の時刻・潮位・あと何分か、いまの潮位のおよその値と上げ潮か下げ潮か、潮回りを返す。読み上げ用の短い文(speech_ja)つき。at で別の時刻も。気象庁の天文潮の推算で、予報ではない。
past_weather港(潮見表の地点)のいちばん近い気象台・測候所(40 km 以内)の、過去の月ごとの平均気温・平均風速・降水量(1991 年から・気象庁の観測)。year だけならその年の 12 か月、month だけなら毎年のその月、両方なら一つの月、どちらも省くと最新の 12 か月。過去の観測で、予報ではない。
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"marine": {
"type": "http",
"url": "https://marine.aluzza.jp/mcp/"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http aluzza https://marine.aluzza.jp/mcp/claude.ai, ChatGPT and other clients: add https://marine.aluzza.jp/mcp/ as a custom connector in the settings.
- jp.aluzza/wages-riskanswers, 6 toolsverified in the MCP registry
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.