io.github.haomingkoo/japan-seasons
NPM · JAPAN-SEASONS-MCP · 2 COMPONENTS · SCANNED SEP 20
Live Japan seasonal travel MCP: sakura, autumn leaves, flowers, festivals, fruit farms, weather.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 68 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.haomingkoo/japan-seasons MCP server?
io.github.haomingkoo/japan-seasons runs locally as an npm package, launched with npx -y japan-seasons-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · japan-seasons-mcp
claude mcp add haomingkoo-japan-seasons -- npx -y japan-seasons-mcp
{
"mcpServers": {
"haomingkoo-japan-seasons": {
"command": "npx",
"args": [
"-y",
"japan-seasons-mcp"
]
}
}
} {
"servers": {
"haomingkoo-japan-seasons": {
"command": "npx",
"args": [
"-y",
"japan-seasons-mcp"
]
}
}
} codex mcp add haomingkoo-japan-seasons -- npx -y japan-seasons-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"haomingkoo-japan-seasons": {
"type": "local",
"command": [
"npx",
"-y",
"japan-seasons-mcp"
],
"enabled": true
}
}
} openclaw mcp add haomingkoo-japan-seasons --command npx --arg -y --arg japan-seasons-mcp
mcp_servers:
haomingkoo-japan-seasons:
command: "npx"
args: ["-y", "japan-seasons-mcp"] {
"McpServers": {
"haomingkoo-japan-seasons": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"japan-seasons-mcp"
]
}
}
} assistant mcp add haomingkoo-japan-seasons -t stdio -c npx -a -y japan-seasons-mcp
{
"mcpServers": {
"haomingkoo-japan-seasons": {
"command": "npx",
"args": [
"-y",
"japan-seasons-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 −2
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 11 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.77 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/japan-seasons-mcp@0.5.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
festivals_list Japan Seasonal Festivals ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
fetch Fetch Japan in Seasons Result ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Result ID returned by search, such as sakura-now, koyo-now, flowers, festivals, fruit, or mcp-install. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
flowers_spots Seasonal Flower Spots ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
fruit_farms Fruit Picking Farms ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
fruit_seasons Fruit Picking Season Calendar ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
japan_seasonal_answer Answer Japan Seasonal Travel Question ~264
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
kawazu_forecast Kawazu Early Cherry Blossom Forecast ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
koyo_best_dates Best Autumn Leaves Dates for Trip ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | Trip end date in YYYY-MM-DD format, for example '2026-11-27'. Must be on or after start_date. |
| start_date | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
koyo_forecast Autumn Leaves Forecast ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
koyo_now Autumn Leaves Forecast Now ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
koyo_spots Autumn Leaves Viewing Spots ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
sakura_best_dates Best Cherry Blossom Dates for Trip ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | Trip end date in YYYY-MM-DD format, for example '2026-04-14'. Must be on or after start_date. |
| start_date | string | yes | Trip start date in YYYY-MM-DD format, for example '2026-04-08'. The tool compares this against each city's sakura viewing window. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
sakura_forecast Cherry Blossom Forecast ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
sakura_now Sakura Forecast Now ~219
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
sakura_spots Cherry Blossom Viewing Spots ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| prefecture | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
search Search Japan in Seasons ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Natural-language search query, for example 'Japan cherry blossom forecast', 'Kyoto autumn leaves', or 'fruit picking in Japan in September'. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
weather_forecast Japan Weather Forecast ~298
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The tool's user-facing answer as Markdown or JSON text. |
No examples provided.
What is the io.github.haomingkoo/japan-seasons MCP server?
io.github.haomingkoo/japan-seasons is an MCP server listed in the public MCP registry as io.github.haomingkoo/japan-seasons. Live Japan seasonal travel MCP: sakura, autumn leaves, flowers, festivals, fruit farms, weather. This page covers its npm package (japan-seasons-mcp).
Is the io.github.haomingkoo/japan-seasons MCP server safe to use?
io.github.haomingkoo/japan-seasons scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.haomingkoo/japan-seasons MCP server expose?
io.github.haomingkoo/japan-seasons exposes 17 tools: japan_seasonal_answer, sakura_now, koyo_now, search, fetch, and 12 more. Their descriptions and schemas cost roughly 3,070 tokens of context every time the server is loaded.
Is the io.github.haomingkoo/japan-seasons MCP server still maintained?
io.github.haomingkoo/japan-seasons is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.haomingkoo/japan-seasons MCP server under?
io.github.haomingkoo/japan-seasons declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.