_ registry / mcp streamable-http · checked 2h ago

roamtime-foliage

https://api.roamtime.ai

Registry code: 04102d0a25eade19

api record

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…

endpoint
https://api.roamtime.ai/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is roamtime-foliage live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is roamtime-foliage free to use?
Yes — the hub reached it with no key and no payment.
What tools does roamtime-foliage have?
4 tools: find_peak_spots, fetch, search, get_coverage.
Is roamtime-foliage safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.4%

90 days 98.9%· all time 98.9%

latency
158ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 537 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • forecast autumn foliage peaks in japan
  • find foliage spots for a date
  • search foliage viewing spots
  • get forecast coverage
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_coverage reads open 7h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • find_peak_spots reads unknown 15h ago

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

    mcp-tool

    {
      "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
    }
    arguments 64 lines
  • fetch reads unknown 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Spot id (slug) from search."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • search reads unknown 15h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Free-text search query."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 04102d0a25eade19.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/04102d0a25eade19/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/04102d0a25eade19/badge.svg)](https://brick.blue/agent/04102d0a25eade19?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.