RoamTime Japan Foliage Forecast
REMOTE · API.ROAMTIME.AI · SCANNED SEP 27
Forecast peak autumn-foliage dates for viewing spots across Japan. Free tier, no key.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · api.roamtime.ai
claude mcp add --transport http ai-roamtime-foliage 'https://api.roamtime.ai/mcp'
{
"mcpServers": {
"ai-roamtime-foliage": {
"url": "https://api.roamtime.ai/mcp"
}
}
} {
"servers": {
"ai-roamtime-foliage": {
"type": "http",
"url": "https://api.roamtime.ai/mcp"
}
}
} [mcp_servers.ai-roamtime-foliage] url = "https://api.roamtime.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-roamtime-foliage": {
"type": "remote",
"url": "https://api.roamtime.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-roamtime-foliage --url 'https://api.roamtime.ai/mcp' --transport streamable-http
mcp_servers:
ai-roamtime-foliage:
url: "https://api.roamtime.ai/mcp" {
"McpServers": {
"ai-roamtime-foliage": {
"Transport": "http",
"Url": "https://api.roamtime.ai/mcp"
}
}
} assistant mcp add ai-roamtime-foliage -t streamable-http -u 'https://api.roamtime.ai/mcp'
{
"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.
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.
- 26 Sept 26 +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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
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 27 Sept 2026 · Probed https://api.roamtime.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=roamtime.ai | CN=WE1,O=Google Trust Services,C=US | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | b2d0bfc339070cdd0ed67fc1f8cafe1c |
| SANs: roamtime.ai, api.roamtime.ai, *.api.roamtime.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.roamtime.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| roamtime.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.roamtime.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.roamtime.ai/mcp | Inconclusive | 405 |
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 →
fetch Fetch a spot forecast ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Spot id (slug) from search. |
No output schema declared.
No examples provided.
find_peak_spots Find foliage spots at peak ~453
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_coverage Forecast coverage ~109
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?'
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search Search foliage spots ~97
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free-text search query. |
No output schema declared.
No examples provided.
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.