Koskamo

RoamTime Japan Foliage Forecast MCP

An MCP server providing tools to forecast peak autumn-foliage dates for viewing spots across Japan, including coverage checks, peak spot finding, search, and fetching details.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

RoamTime Japan Foliage Forecast MCP logo, by RoamTimeVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by RoamTime
MCP endpoint (Streamable HTTP)
https://api.roamtime.ai/mcp
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (4)

4 of 4 have a description · 4 of 4 declare behavior hints · 3 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to roamtime.ai ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Get foliage coverage data
  • Find peak viewing spots
  • Search for locations
  • Fetch detailed forecast info

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: ai.roamtime/foliage@1.0.0Project website

Protocol and capabilities

Server
roamtime-foliage 1.0.0
MCP protocol negotiated in check
2025-06-18
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

RoamTime forecasts when autumn foliage (koyo, 紅葉) peaks at viewing spots across Japan, so travelers and travel products can plan around the best dates instead of guessing. Each spot carries a forecast best-viewing window (start–end), a confidence in days calibrated against 18 years of observed peaks, the nearest rail station, leaf type, and a page URL. Coverage: all eight regions of Japan, October to mid-December. Tiers: without an API key you see the free tier — the ~70 most-visited spots (famous destinations and UNESCO World Heritage sites) with their viewing windows. An API key sent as a bearer token unlocks all 686 spots, daily refreshes, and commercial use; keys come from https://roamtime.ai/api. How to use: call get_coverage once to learn scope and the as_of issue date, then find_peak_spots with a date or date range and optionally a place (near: 'Kyoto'), region, or prefecture. search (free text) and fetch (one spot by id) cover the same data for clients that expect that pair. Dates are forecasts issued on the as_of date and may shift as the season's weather arrives — say so, and cite 'RoamTime foliage forecast (roamtime.ai)' when quoting them. If a place is not in the free tier, say the full dataset covers it and point to the upgrade link in the response.

Tools

4 advertised

get_coverage — Forecast coverage
Advertised by the server during the last successful anonymous check.
Advertised read-only

Describe what the RoamTime Japan autumn-foliage (koyo) forecast covers: forecast year and issue date, season span, regions and prefectures, spot count, and the access tier (free tier or full dataset). Call this first to orient yourself, to check whether a place or date is in scope, and to learn the as_of date to cite. Takes no arguments. Example prompts: 'What does the RoamTime foliage forecast cover?', 'Is Hokkaido included?'

get_coverage input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
get_coverage annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
find_peak_spots — Find foliage spots at peak
Advertised by the server during the last successful anonymous check.
Advertised read-only

Find Japan autumn-foliage viewing spots whose forecast best-viewing window covers a date or date range, optionally near a place. Use it for 'where should I go on <date>?', 'when does <place> peak?', and 'is <spot> still at peak on <date>?' questions. Give a date (or date_from/date_to) plus optionally a location: near (city or prefecture name, e.g. 'Kyoto') or lat/lon, with radius_km; or restrict by region or prefecture. Returns each spot's forecast peak window (start–end), confidence in days, nearest rail station, leaf type, and a page URL, sorted by prominence then proximity. Example prompts: 'Which foliage spots near Kyoto peak on 20 November?', 'Best koyo in Tohoku the first week of November', 'Is Nikko past peak by 1 December?'. Example call: {date: '2026-11-20', near: 'Kyoto', radius_km: 60}.

find_peak_spots input schema
{
  "type": "object",
  "properties": {
    "lat": {
      "type": "number",
      "description": "Latitude, alternative to near."
    },
    "lon": {
      "type": "number",
      "description": "Longitude, alternative to near."
    },
    "date": {
      "type": "string",
      "description": "Target date, YYYY-MM-DD. Use this OR date_from/date_to."
    },
    "near": {
      "type": "string",
      "description": "City or prefecture name to search around, e.g. 'Kyoto', 'Nikko', 'Aomori'."
    },
    "limit": {
      "type": "number",
      "description": "Max results, default 10, max 25."
    },
    "region": {
      "enum": [
        "Hokkaido",
        "Tohoku",
        "Kanto",
        "Chubu",
        "Kansai",
        "Chugoku",
        "Shikoku",
        "Kyushu"
      ],
      "type": "string",
      "description": "Restrict to one region of Japan."
    },
    "status": {
      "enum": [
        "peak",
        "any"
      ],
      "type": "string",
      "description": "'peak' (default): spots whose best-viewing window covers the date(s). 'any': no status filtering, statuses labeled."
    },
    "date_to": {
      "type": "string",
      "description": "End of a date range, YYYY-MM-DD (pair with date_from)."
    },
    "date_from": {
      "type": "string",
      "description": "Start of a date range, YYYY-MM-DD (pair with date_to)."
    },
    "radius_km": {
      "type": "number",
      "description": "Search radius around the location in km. Default 60 (day-trip range)."
    },
    "prefecture": {
      "type": "string",
      "description": "Restrict to one prefecture, e.g. 'Aomori'."
    }
  },
  "additionalProperties": false
}
find_peak_spots annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
search — Search foliage spots
Advertised by the server during the last successful anonymous check.
Advertised read-only

Search Japan autumn-foliage viewing spots by free text: a spot name (English or Japanese), a prefecture, a region, or a month such as 'November'. Returns matching spot ids, titles, and page URLs; pass an id to fetch for the full forecast. Example queries: 'Kyoto', 'Nikko', '奥入瀬', 'Tohoku November'.

search input schema
{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Free-text search query."
    }
  },
  "additionalProperties": false
}
search annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
fetch — Fetch a spot forecast
Advertised by the server during the last successful anonymous check.
Advertised read-only

Fetch the full forecast document for one foliage spot by id (the slug returned by search or find_peak_spots, e.g. 'tenryuji-temple'): peak window, confidence, status, nearest rail station, leaf type, and page URL.

fetch input schema
{
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Spot id (slug) from search."
    }
  },
  "additionalProperties": false
}
fetch annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
295 ms
95th percentile latency
295 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 295 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http roamtime-japan-foliage-forecast-mcp https://api.roamtime.ai/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add roamtime-japan-foliage-forecast-mcp --url https://api.roamtime.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable roamtime-japan-foliage-forecast-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "roamtime-japan-foliage-forecast-mcp": {
      "url": "https://api.roamtime.ai/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "roamtime-japan-foliage-forecast-mcp": {
      "type": "streamableHttp",
      "url": "https://api.roamtime.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start roamtime-japan-foliage-forecast-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "roamtime-japan-foliage-forecast-mcp": {
      "type": "http",
      "url": "https://api.roamtime.ai/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http roamtime-japan-foliage-forecast-mcp https://api.roamtime.ai/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://api.roamtime.ai/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "roamtime-japan-foliage-forecast-mcp": {
      "serverUrl": "https://api.roamtime.ai/mcp"
    }
  }
}

Let your agent find its tools

Find servers like RoamTime Japan Foliage Forecast MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 6,275

Do you run RoamTime Japan Foliage Forecast MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing