Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Japan Agent API 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.
What it does
Japan JMA warnings, typhoons, volcano levels and municipality code history in English; x402 checks
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http japan-agent-api-mcp https://japan-agent-api-production.mk-career-planning.workers.dev/mcp
# 2 — ask your agent for something these tools do
# catalog, jp_warnings, jp_typhoons and 5 more
Japan Agent API costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 japan-agent-api-mcp https://japan-agent-api-production.mk-career-planning.workers.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
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.
List the tools of this server with prices, data sources, licensing, daily limits and data freshness.
No parameter schema on file.
Current Japan Meteorological Agency (JMA) weather emergency warnings, warnings and advisories for one prefecture, as structured JSON in English and Japanese (type, level, status, areas with JMA's English names, issued_at, source URL). Relay only; no independent forecast.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prefecture | string | yes | Japanese prefecture: English name (e.g. "Tokyo", "Osaka", "Hokkaido"; "Tokyo-to" and "Osaka Prefecture" also work), Japanese name in kanji, or JIS code "01".."47". |
| include_municipalities | boolean | no | Also list every municipality (Japanese and English names) per warning. Default false. |
Typhoons JMA is currently issuing bulletins for: number, name, center position, central pressure, maximum wind, issue time, and forecast-circle centers, radii and times, relayed as structured JSON from JMA bulletins (VPTW60-65). No independent forecast, interpolation or track extension.
No parameter schema on file.
Current JMA Volcanic Alert Levels (1-5) or warning kinds for volcanoes without levels, for all JMA-monitored volcanoes or one (name in English or Japanese, or 3-digit JMA code): JMA English and Japanese names, level, previous level and change, issue time, prefectures named in JMA bulletins, source URL and freshness receipt. Relay only; no forecast or interpretation. Volcanoes with no bulletin seen
| Parameter | Type | Required | Notes |
|---|---|---|---|
| volcano | string | no | Optional. JMA volcano name in English (e.g. "Sakurajima", "Asamayama") or Japanese (e.g. "桜島"), or the 3-digit JMA volcano code (e.g. "506"). Omit to list all volcanoes. |
Look up one Japanese municipality code as of a date (default today): give a 5/6-digit code, or prefecture and name (old names OK). Returns status mapped / split_candidates / unknown / invalid, the valid code with English and Japanese names, change type and date (merger, incorporation, division, designated city, name change), confirmed JMA warning areas only, and J-LIS convenience-store certificate
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | no | Municipality code: 5 digits, or 6 digits including the check digit (e.g. 22131 or 221317). |
| prefecture | string | no | Japanese prefecture: English name (e.g. "Tokyo", "Osaka", "Hokkaido"; "Tokyo-to" and "Osaka Prefecture" also work), Japanese name in kanji, or JIS code "01".."47". Use with name. |
| name | string | no | Municipality or ward name in Japanese (old names accepted; a ward may be prefixed with its city) or its e-Stat English name (e.g. "Naka-ku", "Hamamatsu-shi"). Use with prefecture. |
| as_of | string | no | YYYY-MM-DD. The date the answer is for (default: today in Japan time). |
Re-fetch the stored result of a settled paid call (e.g. jp_trip_impact_check) by its receipt_id, for when the response was lost after payment. Free. Unknown or unsettled receipt ids return RECEIPT_NOT_FOUND. Results are kept for 90 days after settlement.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| receipt_id | string | yes | The receipt_id returned with a paid result ("rcpt_" + 64 hex characters). |
Check a Japan itinerary [{date, prefecture}] against JMA warnings/advisories in effect now. Per stop: matched_advisory (with severity), no_match_in_checked_sources (NOT a statement of no impact) or unknown (data missing, or date not today/tomorrow JST). Returns checked sources and areas, unchecked areas, issued_at, retrieved_at, and current JMA typhoon bulletins (listed, not matched). No forecast.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itinerary | array | yes | 1 to 14 stops {date, prefecture}, in travel order. Only stops dated today or tomorrow (Japan time) can be matched; others return unknown. |
Batch (up to 50) Japanese municipality code lookups as of a date, from e-Stat LOD change history (CC BY 4.0): status mapped / split_candidates (all successors, not apportioned) / unknown / invalid, the code valid on as_of with English and Japanese names, change type and date, confirmed JMA warning areas only, and J-LIS convenience-store certificate availability (available / not_listed / unknown).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| items | array | yes | 1 to 50 lookups; each gives code, or prefecture and name. |
| as_of | string | no | Default as_of for items that do not set their own. |
- 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 Japan Agent API or to call it, at any volume.
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
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.4.1.
No release note was published with this version.
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.
Any signed-in account that does not publish Japan Agent API can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.