_ registry / mcp streamable-http · checked 26h ago

aluzza-marine

https://marine.aluzza.jp

Registry code: f13296c9cf253ce9

api record

日本のヨット・ボート・船外機・漁船の輸入と輸出（2011〜2025 年・国ごと・年ごと・円）と、全国 239 か所の潮見表（気象庁の潮位表・2026〜2027 年の満潮・干潮・1 時間ごとの潮位と、月齢・潮回り）、港の近くの気象台・測候所の過去の月ごとの気温・風速・降水量（1991 年から）を返します。答えに使うときは、返ってきた source（出典）を書いてください。輸出入の数には、新しい船か中古の船かの区別はありません。潮位は月と太陽の動きから計算した天文潮で、気圧や風で実際とずれます。航海には使えません（航海には海上保安庁の潮汐表を使ってください）。このサーバーは予報（天気・風・波・高潮）を返しません。

endpoint
https://marine.aluzza.jp/mcp/
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is aluzza-marine live?
Yes — it answered the hub's last check (checked 26h ago). It answered 100% of checks over the last 30 days.
Is aluzza-marine free to use?
Yes — the hub reached it with no key and no payment.
What tools does aluzza-marine have?
8 tools: top_partners, yearly_series, get_tide, get_trade, next_tide, past_weather, list_tide_stations, list_codes.
Is aluzza-marine safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,023ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
2 open 6 never probed 2 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_tide_stations open 26h ago

    潮見表の地点（気象庁の潮位表の 239 か所）を探す。query に地名（例：釧路・東京・横浜・博多）、region に地方（例：北海道東部・関東地方・伊豆諸島）。どちらも省くと地方の一覧と地点の数。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "地点の名前の一部か、2 文字の地点記号（例：TK）"
    },
    "region": {
      "type": "string",
      "description": "地方の名前の一部"
    }
  }
}
    arguments 13 lines
  • list_codes open 26h ago

    使える品目の番号と名前（日本語と英語）、データの注意を返す。最初にこれを呼ぶと間違えにくい。

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • top_partners unknown never probed

    年の範囲・流れ・品目で、相手の国を数量か金額の大きい順に並べる。1 つあたりの平均の値段（円）も付ける。

    mcp-tool

    {
  "type": "object",
  "required": [
    "flow",
    "hs"
  ],
  "properties": {
    "by": {
      "enum": [
        "quantity",
        "value"
      ],
      "type": "string",
      "description": "quantity＝数量の順・value＝金額の順（省くと quantity）"
    },
    "hs": {
      "type": "string",
      "description": "品目の番号。例：8903（船の合計）・890332（モーターボート 7.5〜24m）・890322（セールボート 7.5〜24m）・840721（船外機）・8902（漁船）。一覧は list_codes"
    },
    "flow": {
      "enum": [
        "import",
        "export"
      ],
      "type": "string",
      "description": "import＝日本の輸入・export＝日本の輸出"
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "何か国まで（省くと 10）"
    },
    "year_to": {
      "type": "integer",
      "maximum": 2025,
      "minimum": 2011,
      "description": "年（2011〜2025）"
    },
    "year_from": {
      "type": "integer",
      "maximum": 2025,
      "minimum": 2011,
      "description": "年（2011〜2025）"
    }
  }
}
    arguments 47 lines
  • yearly_series unknown never probed

    流れ・品目・相手の国の、2011〜2025 年の年ごとの数量と金額（円）を返す。partner を省くと世界の合計。

    mcp-tool

    {
  "type": "object",
  "required": [
    "flow",
    "hs"
  ],
  "properties": {
    "hs": {
      "type": "string",
      "description": "品目の番号。例：8903（船の合計）・890332（モーターボート 7.5〜24m）・890322（セールボート 7.5〜24m）・840721（船外機）・8902（漁船）。一覧は list_codes"
    },
    "flow": {
      "enum": [
        "import",
        "export"
      ],
      "type": "string",
      "description": "import＝日本の輸入・export＝日本の輸出"
    },
    "partner": {
      "type": "string",
      "description": "相手の国の日本語名。省くと世界の合計"
    }
  }
}
    arguments 25 lines
  • get_tide unknown 26h ago

    ある地点・ある日の満潮と干潮の時刻と潮位（cm・潮位表基準面から）、月齢、潮回り（大潮・中潮・小潮・長潮・若潮）、その日の月相を返す（2026-01-01〜2027-12-31）。days で 7 日まで続けて。include_hourly で 1 時間ごとの潮位も。気象庁の天文潮の推算で、予報ではない。

    mcp-tool

    {
  "type": "object",
  "required": [
    "station",
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "日付（YYYY-MM-DD・日本の日付）"
    },
    "days": {
      "type": "integer",
      "maximum": 7,
      "minimum": 1,
      "description": "何日分（省くと 1）"
    },
    "station": {
      "type": "string",
      "description": "地点の名前（例：東京・釧路）か地点記号（例：TK）。同じ名前の候補が複数あるときは候補を返す"
    },
    "include_hourly": {
      "type": "boolean",
      "description": "1 時間ごと（0〜23 時）の潮位も返すか（省くと false）"
    }
  }
}
    arguments 27 lines
  • get_trade unknown never probed

    ある年・流れ・品目の、国ごとの数量と金額（円）を返す。partner を書けばその国だけ。partner に「世界の合計」と書けば全体。

    mcp-tool

    {
  "type": "object",
  "required": [
    "year",
    "flow",
    "hs"
  ],
  "properties": {
    "hs": {
      "type": "string",
      "description": "品目の番号。例：8903（船の合計）・890332（モーターボート 7.5〜24m）・890322（セールボート 7.5〜24m）・840721（船外機）・8902（漁船）。一覧は list_codes"
    },
    "flow": {
      "enum": [
        "import",
        "export"
      ],
      "type": "string",
      "description": "import＝日本の輸入・export＝日本の輸出"
    },
    "year": {
      "type": "integer",
      "maximum": 2025,
      "minimum": 2011,
      "description": "年（2011〜2025）"
    },
    "partner": {
      "type": "string",
      "description": "相手の国の日本語名（例：アメリカ・フランス・中国・韓国・タイ）。省くと全部の国"
    }
  }
}
    arguments 32 lines
  • next_tide unknown never probed

    いま（日本の時刻）から見た、次の満潮と次の干潮の時刻・潮位・あと何分か、いまの潮位のおよその値と上げ潮か下げ潮か、潮回りを返す。読み上げ用の短い文（speech_ja）つき。at で別の時刻も。気象庁の天文潮の推算で、予報ではない。

    mcp-tool

    {
  "type": "object",
  "required": [
    "station"
  ],
  "properties": {
    "at": {
      "type": "string",
      "description": "日本の時刻 YYYY-MM-DDTHH:MM（省くといま）"
    },
    "station": {
      "type": "string",
      "description": "地点の名前（例：東京・釧路）か地点記号（例：TK）"
    }
  }
}
    arguments 16 lines
  • past_weather unknown never probed

    港（潮見表の地点）のいちばん近い気象台・測候所（40 km 以内）の、過去の月ごとの平均気温・平均風速・降水量（1991 年から・気象庁の観測）。year だけならその年の 12 か月、month だけなら毎年のその月、両方なら一つの月、どちらも省くと最新の 12 か月。過去の観測で、予報ではない。

    mcp-tool

    {
  "type": "object",
  "required": [
    "station"
  ],
  "properties": {
    "year": {
      "type": "integer",
      "maximum": 2100,
      "minimum": 1991,
      "description": "年"
    },
    "month": {
      "type": "integer",
      "maximum": 12,
      "minimum": 1,
      "description": "月"
    },
    "station": {
      "type": "string",
      "description": "港の名前か地点記号（例：釧路・東京・TK）、または気象台の名前"
    }
  }
}
    arguments 24 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f13296c9cf253ce9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f13296c9cf253ce9/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f13296c9cf253ce9/badge.svg)](https://brick.blue/agent/f13296c9cf253ce9?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on aluzza.jp 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.