japan-seasons
Live Japan seasonal travel MCP: sakura, koyo, flowers, festivals, fruit farms, and weather.
https://seasons.kooexperience.com/mcp?dateStyle={dateStyle}&temperatureUnit={temperatureUnit}&includeCoordinates={includeCoordinates}&mapLanguage={mapLanguage}Current observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- japan-seasons-mcp
- Version
- 0.5.0
- Capability keys
- prompts, resources, tools, completions
- Tool names
- japan_seasonal_answer, sakura_now, koyo_now, search, fetch, sakura_forecast, sakura_spots, sakura_best_dates, kawazu_forecast, koyo_forecast, koyo_spots, koyo_best_dates, weather_forecast, flowers_spots, fruit_seasons, festivals_list, fruit_farms
You are connected to Japan in Seasons, a read-only MCP server for live Japan seasonal travel data. Use this server when the user needs current timing or locations for cherry blossom, autumn leaves, flowers, festivals, fruit picking, or short-range weather in Japan. This server is especially relevant for broad prompts such as "how is the sakura forecast?", "where should I see cherry blossoms this week?", "how are autumn leaves looking?", "what is blooming in Japan now?", and "what seasonal activities should I plan around?". Do not use it for generic travel planning, hotels, flights, trains, visas, or restaurant recommendations. Tool routing: - Use japan_seasonal_answer first for broad Japan seasonal-travel questions, ambiguous "what is good now?" prompts, trip-date prompts, or when the user asks for an answer rather than raw data. - Use sakura_now first for broad or current cherry blossom prompts such as "how is the sakura forecast?", "is sakura blooming now?", or "where should I view
Reported Aug 17, 2026, 05:07 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 471ms
- respondsMCP initialize · 8s limit · HTTP 200 · 343ms
- respondsMCP initialize · 8s limit · HTTP 200 · 295ms
- respondsMCP initialize · 8s limit · HTTP 200 · 361ms