Kamakura Trip Planner
REMOTE · KAMAKURA.INFO
Kamakura and Enoshima day plans, Enoden fares and passes, bloom dates, sights and walking times.
Available components
Last scanned (21 hours ago)
Scores higher than 72% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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 Security74
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2379 tokens (~216/item across 11 items; 8 tools + 3 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 Management43
- Stability observed for 13 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 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.
- 19 Nov 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.
- 17 Nov 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.
- 15 Nov 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.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 8 Nov 26 72
First indexed and scored.
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 21 Nov 2026 · Probed https://kamakura.info/mcp?src=mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kamakura.info | CN=WE1,O=Google Trust Services,C=US | 7 Nov 2026 | 5 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 46df20bf6e6bcd0ea3931d55e0d531 |
| SANs: kamakura.info | ||||||
| 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 kamakura.info. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| info. | DS published | 9986 | 8 | Verified |
| kamakura.info. | No DS | 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://kamakura.info/mcp?src=mcp | Verified | 200 | |
| http (plaintext) | http://kamakura.info/mcp?src=mcp | HTTPS enforced | 301 | https://kamakura.info/mcp?src=mcp |
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 →
bloom_forecast Kamakura bloom forecast ~217
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | A travel date as YYYY-MM-DD, to see where it falls in each window. |
| flower | string | – | cherry, hydrangea, autumn (ginkgo and maple), ginkgo or maple; sakura, ajisai and momiji work too. Omit for all five events. |
| year | integer | – | Year. Default: the next season to come. |
| Name | Type | Req | Description |
|---|---|---|---|
| basis_short | string | – | – |
| checked | string | yes | – |
| date | string|null | yes | – |
| link | string | yes | Page on kamakura.info for this answer. |
| method | string | yes | – |
| notes | array | yes | – |
| phenomena | array | yes | – |
| title | string | yes | – |
| year | integer | yes | – |
No examples provided.
compare_passes Freepass or single tickets? ~372
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | Adults (default 2). |
| children | integer | – | Children aged 6 to 11 (default 0). |
| enoshima | boolean | – | The day includes Enoshima (default true). |
| romancecar | boolean | – | Romancecar seat from Shinjuku on the way out (default false). |
| shinjuku_route | string | – | 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 → En… |
| start | string | – | Where the day starts: tokyo (Tokyo Station), shinjuku, shinagawa or yokohama. Default shinjuku (the Freepass starts on the Odakyu Line). |
| Name | Type | Req | Description |
|---|---|---|---|
| cheapest | object | yes | – |
| checked | string | yes | – |
| children | object|null | yes | – |
| input | object | yes | – |
| link | string | yes | Page on kamakura.info for this answer. |
| notes | array | yes | – |
| options | array | yes | – |
| route | string | yes | – |
| start_name | string | yes | – |
No examples provided.
date_check Kamakura date check ~151
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date as YYYY-MM-DD (or "today", "tomorrow"), 2026-01-01 to 2027-12-31. Default: today in Japan. |
| Name | Type | Req | Description |
|---|---|---|---|
| crowd | string | yes | – |
| crowd_text | string | yes | – |
| date | string | yes | – |
| date_label | string | yes | – |
| golden_week | boolean | – | – |
| holiday | string|null | yes | – |
| holiday_ja | string|null | – | – |
| likely_in_bloom | array | yes | – |
| link | string | yes | Page on kamakura.info for this answer. |
| new_year | boolean | – | – |
| next_holiday | object|null | yes | – |
| season | string|null | yes | – |
| season_label | string|null | – | – |
| tips | array | yes | – |
| weekday | string | yes | – |
| weekend | boolean | – | – |
No examples provided.
enoden_fare Enoden fare ~212
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Enoden station to board at. |
| to | string | yes | Enoden station to get off at. |
| Name | Type | Req | Description |
|---|---|---|---|
| adult_yen | integer | yes | – |
| checked | string | yes | – |
| child_yen | integer | yes | – |
| from | string | yes | – |
| link | string | yes | Page on kamakura.info for this answer. |
| minutes | integer | yes | – |
| noriorikun | object | yes | – |
| notes | array | yes | – |
| sources | array | yes | – |
| stops | integer | yes | – |
| to | string | yes | – |
No examples provided.
getting_there Getting to Kamakura ~189
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start: tokyo, shinjuku, shibuya, shinagawa, yokohama, haneda, narita or fujisawa. Omit for all. |
| to | string | – | kamakura (default), kita-kamakura or enoshima. |
| Name | Type | Req | Description |
|---|---|---|---|
| checked | string | yes | – |
| from | string|null | yes | – |
| link | string | yes | Page on kamakura.info for this answer. |
| notes | array | yes | – |
| round_trip_yen | integer|null | yes | – |
| routes | array | yes | – |
| sources | array | yes | – |
| to | string | yes | – |
No examples provided.
plan_day Kamakura day planner ~440
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| children | integer | – | Children aged 6 to 11, for child entry fees and Enoden child fares (default 0). |
| date | string | – | Date as YYYY-MM-DD (or "today", "tomorrow"), 2026-01-01 to 2027-12-31. Default: next Saturday. |
| days | integer | – | 1 (default) or 2 (two days with one night in Kamakura: Kita-Kamakura, the shrine and the bamboo temple, then Hase and Enoshima). |
| leave | string | – | Time of the first train as HH:MM, 05:00 to 14:00 (default 07:45). |
| route | string | – | 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 (… |
| start | string | – | Where the day starts: tokyo (Tokyo Station), shinjuku, shinagawa or yokohama. Default tokyo. |
| Name | Type | Req | Description |
|---|---|---|---|
| children | object|null | yes | – |
| date_label | string | yes | – |
| day_info | object | yes | – |
| days | array | yes | – |
| entry_fees_yen_per_adult | integer | yes | – |
| fees_not_listed | array | yes | – |
| input | object | yes | – |
| link | string | yes | Page on kamakura.info for this answer. |
| notes | array | yes | – |
| trains_yen_per_adult | integer | yes | – |
| walking_min | integer | yes | – |
| warnings | array | yes | – |
No examples provided.
sight_info Kamakura sight info ~277
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | 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). |
| month | integer | – | Month of the visit, for seasonal opening hours. |
| name | string | – | Temple, shrine, sight or station, in any common spelling. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| link | string | yes | Page on kamakura.info for this answer. |
| sights | array | yes | – |
No examples provided.
walk_time Kamakura walking time ~143
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Start: a temple, shrine, sight or station. |
| to | string | yes | Destination: a temple, shrine, sight or station. |
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | – |
| km | number | yes | – |
| link | string | yes | Page on kamakura.info for this answer. |
| metres | integer | yes | – |
| minutes | integer | yes | – |
| note | string|null | yes | – |
| to | string | yes | – |
No examples provided.
How do I install the Kamakura Trip Planner MCP server?
Kamakura Trip Planner is a hosted endpoint at https://kamakura.info/mcp?src=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 · kamakura.info
claude mcp add --transport http info-kamakura-kamakura-trip-planner 'https://kamakura.info/mcp?src=mcp'
What is the Kamakura Trip Planner MCP server?
Kamakura Trip Planner is an MCP server listed in the public MCP registry as info.kamakura/kamakura-trip-planner. Kamakura and Enoshima day plans, Enoden fares and passes, bloom dates, sights and walking times. This page covers its hosted endpoint (https://kamakura.info/mcp?src=mcp).
Is the Kamakura Trip Planner MCP server safe to use?
Kamakura Trip Planner scores 78 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 Kamakura Trip Planner MCP server expose?
Kamakura Trip Planner exposes 8 tools: plan_day, compare_passes, enoden_fare, bloom_forecast, date_check, and 3 more. Their descriptions and schemas cost roughly 2,001 tokens of context every time the server is loaded.
Does the Kamakura Trip Planner MCP server require authentication?
No. We connected to Kamakura Trip Planner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Kamakura Trip Planner MCP server still maintained?
Kamakura Trip Planner is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Kamakura Trip Planner MCP server?
VerifyMCP ran 14 checks on Kamakura Trip Planner, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.