Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Boken Japan: rural and small-town Japan travel data

REMOTE · BOKENJAPAN.COM

Read-only travel data for every municipality in Japan, from bokenjapan.com

Available components

+3 this week 75 Trust /100

Last scanned (12 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 861 tokens (~123/item across 7 items; 5 tools + 2 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 Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 91% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 20 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.

  • 18 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.

  • 16 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.

  • 13 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.

  • 12 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: pass → fail ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “buy” functional
  • 11 Nov 26 70

    First indexed and scored.

Diagnostics

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://bokenjapan.com/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bokenjapan.com CN=YE2,O=Let's Encrypt,C=US 8 Oct 2026 6 Jan 2027 ECDSA 256 ECDSA-SHA384 695d72e35024733427f9df3dc20f0316f77
SANs: *.bokenjapan.com, bokenjapan.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of bokenjapan.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
bokenjapan.com. 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://bokenjapan.com/mcp/ Verified 200
http (plaintext) http://bokenjapan.com/mcp/ HTTPS enforced 301 https://bokenjapan.com/mcp/
MCP tools · 5 exposed · ~596 tokens

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 →

Tool Tokens
buy ~168

How to pay BokenJapan for a sponsorship tier or a Verified listing check. Returns the live Stripe Payment Link (hosted checkout the human buyer opens and pays on), price in JPY incl. and excl. 10% consumption tax, refund policy and legal disclosure links, and the bank-transfer invoice route. Does not take card data and does not charge anything: the buyer completes payment on Stripe. Call without product_id to list products. Product data comes from https://bokenjapan.com/pay.json.

NameTypeReqDescription
product_idstring–founding | featured | regional | prefecture | addon | verified_check (ids from pay.json). Omit to list all products.
quantityinteger–Verified check: number of listings (one payment per listing). Sponsorship tiers: 1.

No output schema declared.

No examples provided.

get_listing ~68

One listing by id (format <prefecture>/<town>/<section>/<slug>, as returned by search_places or get_town), with all published facts.

NameTypeReqDescription
idstringyesListing id, e.g. "nagano/hakuba/see/hakuba-folk-history-museum"

No output schema declared.

No examples provided.

get_town ~101

Overview of one Boken Japan town (municipality): names EN/JA, coordinates, access (nearest station, car needed), official links, address and phone of the town office, listing counts by type, section pages, sample listings and stays with checked booking links.

NameTypeReqDescription
prefecturestringyesPrefecture slug or name, e.g. "nagano"
townstringyesTown slug or name, e.g. "hakuba"

No output schema declared.

No examples provided.

list_towns ~60

Without prefecture: the 47 prefectures with town and listing counts. With prefecture: every town in it with names, page URL and listing counts.

NameTypeReqDescription
prefecturestring–Prefecture slug or name, e.g. "akita"

No output schema declared.

No examples provided.

search_places ~199

Search Boken Japan listings (sights, things to do, places to eat, places to stay, day-to-day) by name or keyword, optionally within a prefecture and/or town and by category. Returns facts with the bokenjapan.com page, source URL, town access, checked booking links (stays) and last_verified.

NameTypeReqDescription
categorystring–sight | activity | food | stay | day_to_day, or a food category such as "cafe", "noodles", "seafood"
limitinteger––
prefecturestring–Prefecture slug or name, e.g. "nagano"
querystringyesName or keyword, English or Japanese (e.g. "soba", "onsen", "Hakuba", "白馬")
townstring–Town slug or name, e.g. "hakuba" (best with prefecture)

No output schema declared.

No examples provided.

Install

How do I install the Boken Japan: rural and small-town Japan travel data MCP server?

Boken Japan: rural and small-town Japan travel data is a hosted endpoint at https://bokenjapan.com/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 · bokenjapan.com

# add to Claude Code
claude mcp add --transport http com-bokenjapan-mcp 'https://bokenjapan.com/mcp/'
Common questions

What is the Boken Japan: rural and small-town Japan travel data MCP server?

Boken Japan: rural and small-town Japan travel data is an MCP server listed in the public MCP registry as com.bokenjapan/mcp. Read-only travel data for every municipality in Japan, from bokenjapan.com. This page covers its hosted endpoint (https://bokenjapan.com/mcp/).

Is the Boken Japan: rural and small-town Japan travel data MCP server safe to use?

Boken Japan: rural and small-town Japan travel data scores 75 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 Boken Japan: rural and small-town Japan travel data MCP server expose?

Boken Japan: rural and small-town Japan travel data exposes 5 tools: search_places, get_town, get_listing, list_towns, buy. Their descriptions and schemas cost roughly 596 tokens of context every time the server is loaded.

Does the Boken Japan: rural and small-town Japan travel data MCP server require authentication?

No. We connected to Boken Japan: rural and small-town Japan travel data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Boken Japan: rural and small-town Japan travel data MCP server still maintained?

Boken Japan: rural and small-town Japan travel data 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 Boken Japan: rural and small-town Japan travel data MCP server?

VerifyMCP ran 13 checks on Boken Japan: rural and small-town Japan travel data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.