Japan JMA warnings, typhoons, volcano levels and municipality code history in English; x402 checks
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
List the tools of this server with prices, data sources, licensing, daily limits and data freshness.
This tool takes no arguments.
List the tools of this server with prices, data sources, licensing, daily limits and data freshness.
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}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.
| Argument | Type | Description |
|---|---|---|
| receipt_id* | string | The receipt_id returned with a paid result ("rcpt_" + 64 hex characters). |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"receipt_id"
],
"properties": {
"receipt_id": {
"type": "string",
"maxLength": 80,
"minLength": 1,
"description": "The receipt_id returned with a paid result (\"rcpt_\" + 64 hex characters)."
}
}
}Which code does this Japanese municipality have on 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 availability for 8 certificate types. Facts only, from e-Stat LOD (CC BY 4.0) and J-LIS.
| Argument | Type | Description |
|---|---|---|
| code | string | Municipality code: 5 digits, or 6 digits including the check digit (e.g. 22131 or 221317). |
| name | string | 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 | YYYY-MM-DD. The date the answer is for (default: today in Japan time). |
| prefecture | string | 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. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"code": {
"type": "string",
"maxLength": 8,
"minLength": 5,
"description": "Municipality code: 5 digits, or 6 digits including the check digit (e.g. 22131 or 221317)."
},
"name": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "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": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "YYYY-MM-DD. The date the answer is for (default: today in Japan time)."
},
"prefecture": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "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."
}
}
}Which codes are valid on a date for up to 50 Japanese municipalities? 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). Facts only; no document preparation or legal advice. Retrying with the same payment is not charged.
| Argument | Type | Description |
|---|---|---|
| as_of | string | Default as_of for items that do not set their own. |
| items* | array | 1 to 50 lookups; each gives code, or prefecture and name. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"items"
],
"properties": {
"as_of": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Default as_of for items that do not set their own."
},
"items": {
"type": "array",
"items": {
"type": "object",
"properties": {
"code": {
"type": "string",
"maxLength": 8,
"minLength": 5,
"description": "Municipality code: 5 digits, or 6 digits including the check digit (e.g. 22131 or 221317)."
},
"name": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "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": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "YYYY-MM-DD. The date the answer is for (default: today in Japan time)."
},
"prefecture": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "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."
}
}
},
"maxItems": 50,
"minItems": 1,
"description": "1 to 50 lookups; each gives code, or prefecture and name."
}
}
}Does a JMA warning or advisory in effect now match a stop on this Japan itinerary [{date, prefecture}]? 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/volcano bulletins (listed, not matched). No forecast. Retrying with the same payment is not charged; use receipt_id with get_receipt.
| Argument | Type | Description |
|---|---|---|
| itinerary* | array | 1 to 14 stops {date, prefecture}, in travel order. Only stops dated today or tomorrow (Japan time) can be matched; others return unknown, but typhoon and volcano bulletins currently in effect are still listed (not matched). |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"itinerary"
],
"properties": {
"itinerary": {
"type": "array",
"items": {
"type": "object",
"required": [
"date",
"prefecture"
],
"properties": {
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "YYYY-MM-DD in Japan time"
},
"prefecture": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "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\"."
}
}
},
"maxItems": 14,
"minItems": 1,
"description": "1 to 14 stops {date, prefecture}, in travel order. Only stops dated today or tomorrow (Japan time) can be matched; others return unknown, but typhoon and volcano bulletins currently in effect are still listed (not matched)."
}
}
}Which typhoons is JMA issuing bulletins for right now, and what do the bulletins forecast? 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 arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}What is the current JMA Volcanic Alert Level (1-5, or warning kind) of this volcano or of every JMA-monitored volcano? Name in English or Japanese, or 3-digit JMA code. Returns 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. Gaps filled from JMA website lists (newer wins). No JMA source seen = not_seen_in_checked_feeds, never assumed level 1.
| Argument | Type | Description |
|---|---|---|
| volcano | string | 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. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"volcano": {
"type": "string",
"maxLength": 60,
"minLength": 1,
"description": "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."
}
}
}Which JMA weather emergency warnings, warnings and advisories are in effect in this Japanese prefecture now? Structured JSON in English and Japanese (type, level, status, areas with JMA's English names, issued_at, source URL). Relay only; no independent forecast.
| Argument | Type | Description |
|---|---|---|
| prefecture* | string | 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 | Also list every municipality (Japanese and English names) per warning. Default false. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"prefecture"
],
"properties": {
"prefecture": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "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": {
"type": "boolean",
"description": "Also list every municipality (Japanese and English names) per warning. Default false."
}
}
}