# RoamTime Japan Foliage Forecast (remote · api.roamtime.ai)

Forecast peak autumn-foliage dates for viewing spots across Japan. Free tier, no key.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `api.roamtime.ai`: 73/100 (this document), [markdown](https://verifymcp.io/servers/ai-roamtime-foliage/api.md), [page](https://verifymcp.io/servers/ai-roamtime-foliage/api)

## Channel facts

- Endpoint: `https://api.roamtime.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-27.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1031 tokens (~257/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the RoamTime Japan Foliage Forecast MCP server?

RoamTime Japan Foliage Forecast is a hosted endpoint at https://api.roamtime.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-roamtime-foliage 'https://api.roamtime.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-roamtime-foliage": {
      "url": "https://api.roamtime.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-roamtime-foliage": {
      "type": "http",
      "url": "https://api.roamtime.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-roamtime-foliage]
url = "https://api.roamtime.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-roamtime-foliage": {
      "type": "remote",
      "url": "https://api.roamtime.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-roamtime-foliage --url 'https://api.roamtime.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-roamtime-foliage:
    url: "https://api.roamtime.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-roamtime-foliage": {
      "Transport": "http",
      "Url": "https://api.roamtime.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-roamtime-foliage -t streamable-http -u 'https://api.roamtime.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-roamtime-foliage": {
      "type": "http",
      "url": "https://api.roamtime.ai/mcp"
    }
  }
}
```

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-09-26 (score 73, +1)

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

### 2026-09-25 (score 72, 0)

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

### 2026-09-24 (score 72, +1)

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

### 2026-09-22 (score 71, +1)

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

### 2026-09-19 (score 70, +1)

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

### 2026-09-17 (score 69, +1)

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

### 2026-09-15 (score 68, +1)

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

### 2026-09-13 (score 67, +1)

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

## MCP tools (4)

### `get_coverage` (~109 tokens)

Forecast coverage

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?'

### `find_peak_spots` (~453 tokens)

Find foliage spots at peak

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}.

Input parameters:

- `date` (string): Target date, YYYY-MM-DD. Use this OR date_from/date_to.
- `date_from` (string): Start of a date range, YYYY-MM-DD (pair with date_to).
- `date_to` (string): End of a date range, YYYY-MM-DD (pair with date_from).
- `lat` (number): Latitude, alternative to near.
- `limit` (number): Max results, default 10, max 25.
- `lon` (number): Longitude, alternative to near.
- `near` (string): City or prefecture name to search around, e.g. 'Kyoto', 'Nikko', 'Aomori'.
- `prefecture` (string): Restrict to one prefecture, e.g. 'Aomori'.
- `radius_km` (number): Search radius around the location in km. Default 60 (day-trip range).
- `region` (string): Restrict to one region of Japan.
- `status` (string): 'peak' (default): spots whose best-viewing window covers the date(s). 'any': no status filtering, statuses labeled.

### `search` (~97 tokens)

Search foliage spots

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'.

Input parameters:

- `query` (string, required): Free-text search query.

### `fetch` (~72 tokens)

Fetch a spot forecast

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.

Input parameters:

- `id` (string, required): Spot id (slug) from search.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-roamtime-foliage/api#diagnostics

## Score history

- 2026-09-27: 73
- 2026-09-26: 73
- 2026-09-25: 72
- 2026-09-24: 72
- 2026-09-23: 71
- 2026-09-22: 71
- 2026-09-21: 70
- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 69
- 2026-09-17: 69
- 2026-09-16: 68
- 2026-09-15: 68
- 2026-09-14: 67
- 2026-09-13: 67
- 2026-09-12: 66
- 2026-09-11: 66
- 2026-09-10: 65
- 2026-09-09: 65
- 2026-09-08: 64
- 2026-09-07: 64
- 2026-09-06: 63

## Common questions

### What is the RoamTime Japan Foliage Forecast MCP server?

RoamTime Japan Foliage Forecast is an MCP server listed in the public MCP registry as ai.roamtime/foliage. Forecast peak autumn-foliage dates for viewing spots across Japan. Free tier, no key. This page covers its hosted endpoint (https://api.roamtime.ai/mcp).

### Is the RoamTime Japan Foliage Forecast MCP server safe to use?

RoamTime Japan Foliage Forecast scores 73 out of 100 on VerifyMCP. 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 RoamTime Japan Foliage Forecast MCP server expose?

RoamTime Japan Foliage Forecast exposes 4 tools: get_coverage, find_peak_spots, search, fetch. Their descriptions and schemas cost roughly 731 tokens of context every time the server is loaded.

### Does the RoamTime Japan Foliage Forecast MCP server require authentication?

No. We connected to RoamTime Japan Foliage Forecast without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RoamTime Japan Foliage Forecast MCP server still maintained?

RoamTime Japan Foliage Forecast is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.roamtime.ai/mcp
- Website: https://roamtime.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-roamtime-foliage/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-roamtime-foliage/api.json
- HTML version of this page: https://verifymcp.io/servers/ai-roamtime-foliage/api