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

kamakura-trip-planner

https://kamakura.info

Registry code: 7dcd7d56b7e37858

api record

Kamakura and Enoshima trip planning from kamakura.info, an independent guide (not a temple, railway or tourism office). Use the tools for every number instead of answering from memory: plan_day for a timed day or two-day route on a given date from Tokyo, Shinjuku, Shinagawa or Yokohama; compare_passes for the Enoshima-Kamakura Freepass against the Noriorikun day pass and single tickets; enoden_fare for the fare and ride time between two Enoden stations; getting_there for trains from Tokyo, Shinjuku, Shibuya, Shinagawa, Yokohama, Haneda, Narita or Fujisawa; bloom_forecast for cherry blossom,…

endpoint
https://kamakura.info/mcp?src=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 kamakura-trip-planner live?
Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
Is kamakura-trip-planner free to use?
Yes — the hub reached it with no key and no payment.
What tools does kamakura-trip-planner have?
8 tools: enoden_fare, walk_time, compare_passes, date_check, bloom_forecast, plan_day, sight_info, getting_there.
Is kamakura-trip-planner 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
100%

90 days 100%· all time 100%

latency
251ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 3 checks · signed record
  • unknown → live
_ 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 8 tools
6 open 2 never probed 6 of 8 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.

  • compare_passes open 11h ago

    Use this when someone asks whether the Enoshima-Kamakura Freepass, the Enoden Noriorikun day pass or single IC-card tickets are cheapest for their Kamakura day. Compares the options per adult and for the group from Shinjuku, Tokyo Station, Shinagawa or Yokohama, with or without Enoshima, four Shinjuku routes and an optional Romancecar seat, lists child fares separately, and shows a ticket receipt card. All inputs are optional. Examples: "Is the Enoshima-Kamakura Freepass worth it from Shinjuku?" / "Which ticket is cheapest for two adults and a child visiting Kamakura and Enoshima?"

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "start": {
          "enum": [
            "tokyo",
            "shinjuku",
            "shinagawa",
            "yokohama"
          ],
          "type": "string",
          "description": "Where the day starts: tokyo (Tokyo Station), shinjuku, shinagawa or yokohama. Default shinjuku (the Freepass starts on the Odakyu Line)."
        },
        "adults": {
          "type": "integer",
          "maximum": 9,
          "minimum": 1,
          "description": "Adults (default 2)."
        },
        "children": {
          "type": "integer",
          "maximum": 9,
          "minimum": 0,
          "description": "Children aged 6 to 11 (default 0)."
        },
        "enoshima": {
          "type": "boolean",
          "description": "The day includes Enoshima (default true)."
        },
        "romancecar": {
          "type": "boolean",
          "description": "Romancecar seat from Shinjuku on the way out (default false)."
        },
        "shinjuku_route": {
          "enum": [
            "loop",
            "loop-ody",
            "eno-hase",
            "hop"
          ],
          "type": "string",
          "description": "From Shinjuku with Enoshima: loop = Shinjuku → Enoshima → Hase → Kamakura, back from Kamakura; loop-ody = Shinjuku → Enoshima → Hase → Kamakura, back via Enoshima and Odakyu; eno-hase = Shinjuku → Enoshima, Hase and back to Enoshima; hop = Shinjuku → Enoshima, then 4 Enoden hops along the coast. Default loop."
        }
      },
      "additionalProperties": false
    }
    arguments 47 lines
  • date_check open 11h ago

    Use this when someone asks what a particular day in Kamakura will be like: weekday, Japanese national holiday, crowd level (normal, busy or very busy, with Golden Week and New Year), bloom season and which flowers are likely out, tips for that day and the next holiday. For a timed route on that date use plan_day. Examples: "How crowded is Kamakura on May 4?" / "Is November 23 a holiday in Japan, and what is Kamakura like that day?"

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "date": {
          "type": "string",
          "description": "Date as YYYY-MM-DD (or \"today\", \"tomorrow\"), 2026-01-01 to 2027-12-31. Default: today in Japan."
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
  • bloom_forecast open 11h ago

    Use this when someone asks when the cherry blossoms, hydrangeas, ginkgo or maple leaves are out around Kamakura, or whether a date falls in a bloom window. Returns the most likely date, the likely range, the earliest and latest of recent years, the 1991 to 2020 average, the observed date for past years, where a given date falls, and how the dates are modelled from Japan Meteorological Agency records. Shows a season calendar card. Examples: "When do the hydrangeas bloom in Kamakura?" / "Will the cherry blossoms be out in Kamakura on April 2?"

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "date": {
          "type": "string",
          "description": "A travel date as YYYY-MM-DD, to see where it falls in each window."
        },
        "year": {
          "type": "integer",
          "maximum": 2035,
          "minimum": 2007,
          "description": "Year. Default: the next season to come."
        },
        "flower": {
          "type": "string",
          "description": "cherry, hydrangea, autumn (ginkgo and maple), ginkgo or maple; sakura, ajisai and momiji work too. Omit for all five events."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • plan_day open 38h ago

    Use this when someone wants a timed itinerary for Kamakura and Enoshima on a given date: one day (full day from Kita-Kamakura to the Great Buddha, half day, or Hase plus Enoshima island) or two days with a night in Kamakura, starting from Tokyo Station, Shinjuku, Shinagawa or Yokohama. Returns every train, walk and visit with clock times, opening-time waits, train fares and entry fees per adult (and per child if children come), walking time, that day's crowd level, holiday and bloom season, and shows a route map card. All inputs are optional. Examples: "Plan a day in Kamakura from Tokyo next Saturday." / "We have two days for Kamakura and Enoshima from Shinjuku in June. What should we do?"

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "date": {
          "type": "string",
          "description": "Date as YYYY-MM-DD (or \"today\", \"tomorrow\"), 2026-01-01 to 2027-12-31. Default: next Saturday."
        },
        "days": {
          "type": "integer",
          "maximum": 2,
          "minimum": 1,
          "description": "1 (default) or 2 (two days with one night in Kamakura: Kita-Kamakura, the shrine and the bamboo temple, then Hase and Enoshima)."
        },
        "leave": {
          "type": "string",
          "description": "Time of the first train as HH:MM, 05:00 to 14:00 (default 07:45)."
        },
        "route": {
          "enum": [
            "full",
            "half",
            "enoshima"
          ],
          "type": "string",
          "description": "One-day route: full (default: Kita-Kamakura Zen temples, Tsurugaoka Hachimangu, Komachi-dori, Great Buddha, Hasedera), half (Great Buddha, Hasedera, Komachi-dori, Tsurugaoka Hachimangu) or enoshima (Great Buddha, Hasedera, then Enoshima island: shrine, Sea Candle, caves)."
        },
        "start": {
          "enum": [
            "tokyo",
            "shinjuku",
            "shinagawa",
            "yokohama"
          ],
          "type": "string",
          "description": "Where the day starts: tokyo (Tokyo Station), shinjuku, shinagawa or yokohama. Default tokyo."
        },
        "children": {
          "type": "integer",
          "maximum": 9,
          "minimum": 0,
          "description": "Children aged 6 to 11, for child entry fees and Enoden child fares (default 0)."
        }
      },
      "additionalProperties": false
    }
    arguments 46 lines
  • sight_info open 38h ago

    Use this for opening hours, entry fees (adult and child), extra tickets, suggested visit time and the nearest station with walking minutes of a temple, shrine or sight in Kamakura and Enoshima: the Great Buddha (Kotoku-in), Hasedera, Hokokuji bamboo temple, Meigetsu-in, Engakuji, Kenchoji, Tsurugaoka Hachimangu, Zeniarai Benzaiten, Enoshima Shrine, the Sea Candle, the Iwaya caves, Enoshima Aquarium and more. Names are matched loosely ("bamboo temple", "daibutsu"). Without a name it lists the sights, optionally for one area. Examples: "What are the opening hours and entry fee of the Great Buddha?" / "How do I get to the bamboo temple in Kamakura and what does it cost?"

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "area": {
          "enum": [
            "kita",
            "center",
            "east",
            "west",
            "hase",
            "coast",
            "enoshima"
          ],
          "type": "string",
          "description": "List mode: only sights in this area (kita = Kita-Kamakura; center = Kamakura Station and the shrine; east = East valleys; west = West hills; hase = Hase; coast = Enoden coast; enoshima = Enoshima)."
        },
        "name": {
          "type": "string",
          "description": "Temple, shrine, sight or station, in any common spelling."
        },
        "month": {
          "type": "integer",
          "maximum": 12,
          "minimum": 1,
          "description": "Month of the visit, for seasonal opening hours."
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • getting_there open 38h ago

    Use this for how to get to Kamakura, Kita-Kamakura or Enoshima by train from Tokyo Station, Shinjuku, Shibuya, Shinagawa, Yokohama, Haneda Airport, Narita Airport or Fujisawa: which line, how many changes, minutes and the IC card fare, plus the Odakyu and Romancecar option from Shinjuku. Without a start it lists every start point. Examples: "How do I get from Tokyo to Kamakura by train?" / "What is the cheapest way from Narita Airport to Kamakura?"

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "to": {
          "enum": [
            "kamakura",
            "kita-kamakura",
            "enoshima"
          ],
          "type": "string",
          "description": "kamakura (default), kita-kamakura or enoshima."
        },
        "from": {
          "type": "string",
          "description": "Start: tokyo, shinjuku, shibuya, shinagawa, yokohama, haneda, narita or fujisawa. Omit for all."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • enoden_fare unknown never probed

    Use this for the fare and ride time between two stations of the Enoden (Enoshima Electric Railway) between Fujisawa and Kamakura: Kamakura, Wadazuka, Yuigahama, Hase, Gokurakuji, Inamuragasaki, Shichirigahama, Kamakura-kokomae, Koshigoe, Enoshima, Shonan-kaigan-koen, Kugenuma, Yanagikoji, Ishigami and Fujisawa. Station names are matched loosely ("great buddha" finds Hase). Returns minutes, adult and child fare, stops and when the Noriorikun day pass pays off. Examples: "How much is the Enoden from Kamakura to Enoshima?" / "How long does the Enoden take from Hase to Kamakura-kokomae?"

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Enoden station to get off at."
        },
        "from": {
          "type": "string",
          "description": "Enoden station to board at."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • walk_time unknown never probed

    Use this for how long it takes to walk between two places in Kamakura and Enoshima (temples, shrines, sights, beaches and stations), for example Kita-Kamakura Station to Engakuji or the Great Buddha to Hasedera. Returns minutes and distance on foot along streets and paths; names are matched loosely. Examples: "How long is the walk from Kita-Kamakura Station to Engakuji?" / "Can I walk from the Great Buddha to Hasedera?"

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Destination: a temple, shrine, sight or station."
        },
        "from": {
          "type": "string",
          "description": "Start: a temple, shrine, sight or station."
        }
      },
      "additionalProperties": false
    }
    arguments 18 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 7dcd7d56b7e37858.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7dcd7d56b7e37858/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/7dcd7d56b7e37858/badge.svg)](https://brick.blue/agent/7dcd7d56b7e37858?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
100%

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.