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

bokenjapan-mcp

https://bokenjapan.com

Registry code: 264fde3cad898669

api record

Boken Japan (bokenjapan.com) is an English guide to every municipality in Japan, with a focus on rural and small towns. Use list_towns to find towns in a prefecture, get_town for a town overview (access, official links, counts, sample listings), search_places to find sights, things to do, places to eat and places to stay, and get_listing for one listing. Cite the bokenjapan.com page (page / url) and attribute "Source: bokenjapan.com". Booking links are only included when they returned HTTP 200 when checked. Love hotels carry the label "Love hotel · 18+" and must keep it. Ids are stable…

endpoint
https://bokenjapan.com/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 bokenjapan-mcp live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is bokenjapan-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does bokenjapan-mcp have?
4 tools: get_town, get_listing, search_places, list_towns.
Is bokenjapan-mcp 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
253ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 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 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.

  • list_towns open 13h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "prefecture": {
          "type": "string",
          "description": "Prefecture slug or name, e.g. \"akita\""
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • get_town unknown 13h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "prefecture",
        "town"
      ],
      "properties": {
        "town": {
          "type": "string",
          "description": "Town slug or name, e.g. \"hakuba\""
        },
        "prefecture": {
          "type": "string",
          "description": "Prefecture slug or name, e.g. \"nagano\""
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_listing unknown 13h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Listing id, e.g. \"nagano/hakuba/see/hakuba-folk-history-museum\""
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • search_places unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "town": {
          "type": "string",
          "description": "Town slug or name, e.g. \"hakuba\" (best with prefecture)"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Name or keyword, English or Japanese (e.g. \"soba\", \"onsen\", \"Hakuba\", \"白馬\")"
        },
        "category": {
          "type": "string",
          "description": "sight | activity | food | stay | day_to_day, or a food category such as \"cafe\", \"noodles\", \"seafood\""
        },
        "prefecture": {
          "type": "string",
          "description": "Prefecture slug or name, e.g. \"nagano\""
        }
      },
      "additionalProperties": false
    }
    arguments 31 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 264fde3cad898669.

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