# io.github.haomingkoo/japan-seasons (remote · seasons.kooexperience.com)

Live Japan seasonal travel MCP: sakura, autumn leaves, flowers, festivals, fruit farms, weather.

- Trust score: 72/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `seasons.kooexperience.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/haomingkoo-japan-seasons/seasons.md), [page](https://verifymcp.io/servers/haomingkoo-japan-seasons/seasons)
- npm · `japan-seasons-mcp`: 70/100, [markdown](https://verifymcp.io/servers/haomingkoo-japan-seasons/japan-seasons-mcp.md), [page](https://verifymcp.io/servers/haomingkoo-japan-seasons/japan-seasons-mcp)

## Channel facts

- Endpoint: `https://seasons.kooexperience.com/mcp?dateStyle={dateStyle}&temperatureUnit={temperatureUnit}&includeCoordinates={includeCoordinates}&mapLanguage={mapLanguage}`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 17 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3858 tokens (~175/item across 22 items; 17 tools + 5 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http haomingkoo-japan-seasons https://seasons.kooexperience.com/mcp?dateStyle={dateStyle}&temperatureUnit={temperatureUnit}&includeCoordinates={includeCoordinates}&mapLanguage={mapLanguage}
```

### Codex

```toml
[mcp_servers.haomingkoo-japan-seasons]
url = "https://seasons.kooexperience.com/mcp?dateStyle={dateStyle}&temperatureUnit={temperatureUnit}&includeCoordinates={includeCoordinates}&mapLanguage={mapLanguage}"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "haomingkoo-japan-seasons": {
      "type": "remote",
      "url": "https://seasons.kooexperience.com/mcp?dateStyle={dateStyle}&temperatureUnit={temperatureUnit}&includeCoordinates={includeCoordinates}&mapLanguage={mapLanguage}",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add haomingkoo-japan-seasons --url https://seasons.kooexperience.com/mcp?dateStyle={dateStyle}&temperatureUnit={temperatureUnit}&includeCoordinates={includeCoordinates}&mapLanguage={mapLanguage} --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  haomingkoo-japan-seasons:
    url: "https://seasons.kooexperience.com/mcp?dateStyle={dateStyle}&temperatureUnit={temperatureUnit}&includeCoordinates={includeCoordinates}&mapLanguage={mapLanguage}"
```

### Other

```json
{
  "mcpServers": {
    "haomingkoo-japan-seasons": {
      "type": "http",
      "url": "https://seasons.kooexperience.com/mcp?dateStyle={dateStyle}&temperatureUnit={temperatureUnit}&includeCoordinates={includeCoordinates}&mapLanguage={mapLanguage}"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 67)

First indexed and scored.

## MCP tools (17)

### `japan_seasonal_answer` (~264 tokens)

Answer Japan Seasonal Travel Question

Use this first when the user asks a broad Japan seasonal travel question, including cherry blossom forecasts, autumn leaves, flowers, festivals, fruit picking, or what is good during travel dates. This is the best entry point for natural traveler prompts because it routes to the right live dataset and returns a ready-to-use recommendation. Do not use this for hotels, flights, trains, visas, restaurants, or generic itinerary planning unrelated to seasonal timing.

Input parameters:

- `end_date` (string): Optional trip end date in YYYY-MM-DD format. Provide this when the user gives travel dates.
- `location` (string): Optional city, prefecture, or region such as Tokyo, Kyoto, Hokkaido, Kansai, Tohoku.
- `question` (string): The user's natural-language question, for example 'How is the sakura forecast?', 'Where should I see autumn leaves in late November?', or 'What seasonal things are good in Japan in June?'
- `season` (string): Optional explicit season/topic. Use auto unless the user clearly asks for one topic. Use overview for broad questions about what seasonal activities are good in a month.
- `start_date` (string): Optional trip start date in YYYY-MM-DD format. Provide this when the user gives travel dates.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `sakura_now` (~219 tokens)

Sakura Forecast Now

Use this first for broad cherry blossom prompts such as 'How is the sakura forecast?', 'Is sakura blooming now?', 'Where should I view sakura today?', 'Where should I see cherry blossoms this week?', or 'How is Kyoto sakura looking?'. Returns a concise current answer from live Japan Meteorological Corporation forecast and observation data, including specific viewing spot suggestions when current spot data is available, plus next-step guidance for the full park list and weather. Do not use this for autumn leaves, non-sakura flowers, hotels, trains, or generic itinerary planning.

Input parameters:

- `city` (string): Optional city, prefecture, or region filter such as Tokyo, Kyoto, Hokkaido, Kansai, Tohoku. Omit for nationwide status.
- `end_date` (string): Optional trip end date in YYYY-MM-DD format. Use with start_date when the user gives travel dates.
- `start_date` (string): Optional trip start date in YYYY-MM-DD format. Use with end_date when the user gives travel dates.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `koyo_now` (~188 tokens)

Autumn Leaves Forecast Now

Use this first for broad autumn leaves prompts such as 'How are autumn leaves looking?', 'Where is koyo good now?', 'Kyoto autumn leaves forecast', or 'Where should I see fall foliage in Japan?'. Returns a concise current answer from live Japan Meteorological Corporation maple and ginkgo forecast data. Do not use this for cherry blossoms, fruit picking, hotels, trains, or generic itinerary planning.

Input parameters:

- `end_date` (string): Optional trip end date in YYYY-MM-DD format. Use with start_date when the user gives travel dates.
- `region` (string): Optional city, prefecture, or region filter such as Kyoto, Tokyo, Hokkaido, Kansai, Nikko, Tohoku. Omit for nationwide status.
- `start_date` (string): Optional trip start date in YYYY-MM-DD format. Use with end_date when the user gives travel dates.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `search` (~114 tokens)

Search Japan in Seasons

Use this for ChatGPT/deep-research style retrieval over Japan in Seasons. Searches live seasonal-travel dataset guides and returns result IDs for fetch. Use for questions about Japan cherry blossom forecasts, autumn leaves, seasonal flowers, festivals, fruit picking, weather, or the MCP server itself. Do not use for hotels, flights, trains, visas, or restaurants.

Input parameters:

- `query` (string, required): Natural-language search query, for example 'Japan cherry blossom forecast', 'Kyoto autumn leaves', or 'fruit picking in Japan in September'.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `fetch` (~81 tokens)

Fetch Japan in Seasons Result

Use this after search to retrieve a full Japan in Seasons result with citation URL and text. For live sakura or autumn leaves result IDs, this fetches the current forecast answer from live JMC data.

Input parameters:

- `id` (string, required): Result ID returned by search, such as sakura-now, koyo-now, flowers, festivals, fruit, or mcp-install.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `sakura_forecast` (~150 tokens)

Cherry Blossom Forecast

Use this when the user asks about cherry blossom timing, peak bloom, whether sakura has started, or how cities compare across Japan. Returns Japan Meteorological Corporation forecast bloom dates, full-bloom dates, observed dates when available, historical averages, and status for 48 observation cities. Do not use this for specific parks or temples; call sakura_spots next for prefecture-level viewing spots.

Input parameters:

- `city` (string): Optional city, prefecture, or region filter such as 'Tokyo', 'Kyoto', 'Hokkaido', or 'Tohoku'. Partial case-insensitive matches are supported across city, prefecture, and region names. Omit to return…

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `sakura_spots` (~173 tokens)

Cherry Blossom Viewing Spots

Use this when the user already knows the prefecture and needs exact cherry blossom viewing spots with current status and GPS coordinates. Each spot uses JMC reporter observations as the primary status when filed within the last 48 hours (states: pre-bloom through hazakura/green leaves); falls back to the JMC bloom-meter estimate otherwise, with any stale observation shown as secondary context. Also returns the prefecture's JMA reference station summary. Do not use this for nationwide timing comparisons or date matching; use sakura_forecast or sakura_best_dates first.

Input parameters:

- `prefecture` (string, required): Required prefecture filter. Accepts English prefecture name or numeric prefecture code such as 'Tokyo', 'Kyoto', 'Hokkaido', or '13'. This tool returns one prefecture at a time.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `sakura_best_dates` (~150 tokens)

Best Cherry Blossom Dates for Trip

Use this when the user provides travel dates and wants to know where sakura is likely to be best during that trip. Returns cities whose viewing window overlaps the requested date range, based on observed or forecast full-bloom dates. Do not use this for January-February early-bloom Kawazu requests; use kawazu_forecast for those.

Input parameters:

- `end_date` (string, required): Trip end date in YYYY-MM-DD format, for example '2026-04-14'. Must be on or after start_date.
- `start_date` (string, required): Trip start date in YYYY-MM-DD format, for example '2026-04-08'. The tool compares this against each city's sakura viewing window.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `kawazu_forecast` (~186 tokens)

Kawazu Early Cherry Blossom Forecast

Use this for January-February cherry blossom requests or when the user specifically asks about Kawazu-zakura, early blossoms, or the Izu Peninsula. Returns the Japan Meteorological Corporation forecast comment, forecast map links, and Kawazu cherry spots with bloom percentages, full-bloom percentages, forecast dates, and coordinates. Do not use this for standard Somei-Yoshino sakura elsewhere in Japan.

Input parameters:

- `include_spots` (boolean): Whether to include the full list of Kawazu viewing spots. Defaults to true. Set false when the user only needs the overall forecast summary and map.
- `spot_name` (string): Optional case-insensitive substring filter for a specific Kawazu landmark or area, such as '原木', '駅前', 'iZoo', or '七滝'. Use this when the user asks about one named spot instead of the full list.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `koyo_forecast` (~186 tokens)

Autumn Leaves Forecast

Use this when the user asks when autumn leaves peak, whether one city colors earlier than another, or wants a national overview for October-December. Returns city-level maple and ginkgo forecast dates, forecast maps, and regional commentary from Japan Meteorological Corporation. Do not use this for specific temples, gardens, or GPS-tagged locations; call koyo_spots next for those.

Input parameters:

- `region` (string): Optional case-insensitive filter for a region, prefecture, or city such as 'Kyoto', 'Tokyo', 'Hokkaido', 'Kansai'. Use this when the user only cares about one part of Japan instead of the full nation…
- `tree_type` (string): Optional tree filter. Use 'maple' for momiji-only dates, 'ginkgo' for ginkgo-only dates, or omit/use 'all' to return both.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `koyo_spots` (~146 tokens)

Autumn Leaves Viewing Spots

Use this when the user already knows the prefecture and needs exact autumn leaves viewing spots. Returns Japan Meteorological Corporation koyo spots for one prefecture with best start, peak, and end dates, leaf type, popularity rating, and GPS coordinates. Omit prefecture to get a top-destinations guide. Do not use this for cross-city date matching; use koyo_forecast or koyo_best_dates first.

Input parameters:

- `prefecture` (string): Prefecture filter. Accepts English name or numeric code such as 'Kyoto', 'Tokyo', 'Hokkaido', or '26'. Omit to receive a curated list of top koyo destinations across Japan.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `koyo_best_dates` (~149 tokens)

Best Autumn Leaves Dates for Trip

Use this when the user gives autumn travel dates and wants the best cities during that window. Returns cities whose maple or ginkgo viewing windows overlap the trip, based on forecast peak dates. Do not use this for general climate questions or for exact park recommendations without dates; use koyo_spots when the prefecture is already known.

Input parameters:

- `end_date` (string, required): Trip end date in YYYY-MM-DD format, for example '2026-11-27'. Must be on or after start_date.
- `start_date` (string, required): Trip start date in YYYY-MM-DD format, for example '2026-11-20'. The tool checks whether each city's koyo window overlaps this date.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `weather_forecast` (~298 tokens)

Japan Weather Forecast

Use this when short-range weather could change the recommendation, especially for sakura petal fall, rain risk, or packing advice. Returns the next 3 days of Japan Meteorological Agency forecast text, temperatures, and 6-hour rain probabilities for one supported city. Do not use this for seasonal bloom timing months in advance; use the sakura or koyo forecast tools for that.

Input parameters:

- `city` (string, required): Supported city name such as 'Tokyo', 'Kyoto', 'Osaka', or 'Sapporo'. Partial case-insensitive matching is accepted. Full supported list: Sapporo, Hakodate, Asahikawa, Kushiro, Obihiro, Aomori, Moriok…

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `flowers_spots` (~223 tokens)

Seasonal Flower Spots

Use this for non-sakura flower trips such as plum, wisteria, hydrangea, lavender, sunflower, or cosmos. Returns curated flower spots with peak windows, official URLs, notes, and GPS coordinates. Do not use this for cherry blossom or autumn leaves timing; use the sakura or koyo tools for those live forecasts.

Input parameters:

- `month` (integer): Optional month number from 1 to 12. Returns only flower types whose curated season includes that month, for example 4 for wisteria or 6 for hydrangea.
- `prefecture` (string): Optional prefecture filter such as 'Kanagawa', 'Kyoto', 'Tokyo', or 'Hokkaido'. Partial case-insensitive matches are supported.
- `type` (string): Optional flower type filter. Allowed values: 'all', 'plum', 'nanohana', 'wisteria', 'iris', 'hydrangea', 'lavender', 'sunflower', or 'cosmos'. Omit or use 'all' to return every flower type.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `fruit_seasons` (~121 tokens)

Fruit Picking Season Calendar

Use this when the user asks what fruit is in season in a given month or which month is best for strawberries, grapes, peaches, apples, and similar picking trips. Returns the fruit season calendar, peak months, best regions, and notes for 14 fruits. Call fruit_farms next if the user needs actual farm listings, map coordinates, or booking links.

Input parameters:

- `month` (integer): Optional month number from 1 to 12. Returns fruits in season during that month plus fruits starting the following month. Omit to return the full year calendar.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `festivals_list` (~195 tokens)

Japan Seasonal Festivals

Use this when the user wants recurring Japan events to plan around, such as fireworks, matsuri, or winter festivals. Returns curated events with typical dates, attendance, official URLs, notes, and GPS coordinates. Do not use this for bloom timing, one-off concerts, or weather forecasts.

Input parameters:

- `month` (integer): Optional month number from 1 to 12. Useful examples: 7 or 8 for fireworks season, 10 or 11 for autumn matsuri, and 1 or 2 for winter events.
- `prefecture` (string): Optional prefecture filter such as 'Tokyo', 'Kyoto', 'Osaka', or 'Hokkaido'. Partial case-insensitive matches are supported.
- `type` (string): Optional event type filter. Allowed values: 'all', 'fireworks', 'matsuri', or 'winter'. Omit or use 'all' to return every event type.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

### `fruit_farms` (~227 tokens)

Fruit Picking Farms

Use this when the user needs actual fruit-picking farms, booking links, and map coordinates. Returns farms from the local dataset, and month filtering automatically narrows results to fruits that are in season. If the user only asks which fruit is in season, call fruit_seasons first.

Input parameters:

- `fruit` (string): Optional fruit name such as 'Strawberry', 'Apple', 'Grape', 'Peach', 'Cherry', or 'Mikan'. Matching is case-insensitive. Use with or instead of month.
- `limit` (integer): Optional maximum number of farms to return. Default is 30 and the hard maximum is 100.
- `month` (integer): Optional travel month from 1 to 12. Filters to farms with at least one fruit in season during that month, for example 5 for May strawberry farms.
- `region` (string): Optional prefecture, city, or region substring such as 'Yamanashi', 'Nagano', 'Aomori', or 'Tokyo'. Partial case-insensitive matching is supported against farm names and addresses.

Output parameters:

- `answer` (string): The tool's user-facing answer as Markdown or JSON text.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/haomingkoo-japan-seasons/seasons#diagnostics

## Score history

- 2026-08-03: 72
- 2026-08-02: 71
- 2026-08-01: 71
- 2026-07-31: 70
- 2026-07-30: 69
- 2026-07-29: 69
- 2026-07-28: 68
- 2026-07-27: 67
- 2026-07-26: 67

## Links

- Remote endpoint: https://seasons.kooexperience.com/mcp?dateStyle={dateStyle}&temperatureUnit={temperatureUnit}&includeCoordinates={includeCoordinates}&mapLanguage={mapLanguage}
- Repository: https://github.com/haomingkoo/japan-seasons-mcp
- Changelog RSS feed: https://verifymcp.io/servers/haomingkoo-japan-seasons/seasons/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/haomingkoo-japan-seasons/seasons/changelog.json
- HTML version of this page: https://verifymcp.io/servers/haomingkoo-japan-seasons/seasons