# Tokyo Charter Bus (remote · tokyocharterbus.com)

Discover Tokyo charter coaches, routes and reference fares. Quotations need user confirmation.

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `tokyocharterbus.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/dang13021993-tokyocharterbus/tokyocharterbus.md), [page](https://verifymcp.io/servers/dang13021993-tokyocharterbus/tokyocharterbus)

## Channel facts

- Endpoint: `https://tokyocharterbus.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_quote_request).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1377 tokens (~275/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 57% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Tokyo Charter Bus MCP server?

Tokyo Charter Bus is a hosted endpoint at https://tokyocharterbus.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.

### Claude

```bash
claude mcp add --transport http dang13021993-tokyocharterbus 'https://tokyocharterbus.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dang13021993-tokyocharterbus": {
      "url": "https://tokyocharterbus.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dang13021993-tokyocharterbus": {
      "type": "http",
      "url": "https://tokyocharterbus.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dang13021993-tokyocharterbus]
url = "https://tokyocharterbus.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dang13021993-tokyocharterbus": {
      "type": "remote",
      "url": "https://tokyocharterbus.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dang13021993-tokyocharterbus --url 'https://tokyocharterbus.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dang13021993-tokyocharterbus:
    url: "https://tokyocharterbus.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dang13021993-tokyocharterbus": {
      "Transport": "http",
      "Url": "https://tokyocharterbus.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dang13021993-tokyocharterbus -t streamable-http -u 'https://tokyocharterbus.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dang13021993-tokyocharterbus": {
      "type": "http",
      "url": "https://tokyocharterbus.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 61, 0)

- [security] Tool “list_charter_bus_options” rewrote its description, which is the text the model reads

### 2026-11-11 (score 61, +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.

### 2026-11-09 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 59, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (5)

### `list_charter_bus_options` (~295 tokens)

List charter vehicle options

Lists bus and coach types customers can enquire about for group transport with a driver in and from Tokyo (charter coaches and minibuses), the 7-seat private car with driver (alphard-7, max 6 passengers, hire-car licence, arranged with licensed local hire-car operators per request, requests accepted across Japan) and add-on cars offered only with a coach booking. Returns passenger seats (driver excluded), auxiliary seats, luggage information and verification status. Optionally recommends a bus combination for a passenger and suitcase count. Also returns fixed_prices: indicative per-vehicle starting amounts (JPY, tax included) for selected routes, null where a written quote is required, plus the owner-approved 7-seat Alphard day rate. Reference amounts are not binding fixed-price offers or confirmations of availability.

Input parameters:

- `allow_auxiliary_seats` (boolean): false = do not count fold-down auxiliary seats.
- `carry_on_bags` (integer): Carry-on bags kept in the cabin.
- `category` (string): Filter by vehicle category.
- `large_suitcases` (integer): Number of large suitcases.
- `locale` (string): BCP 47 locale for names and messages: en, ja, zh-CN, zh-TW, ko, th, id, fr, de, es or it. Defaults to en.
- `passengers` (integer): Number of passengers, to get a recommended combination.

### `get_service_areas_and_routes` (~144 tokens)

Get service areas and routes

Returns the areas served from Tokyo (Tokyo, Narita and Haneda airports, Mt. Fuji, Kawaguchiko, Hakone, Nikko, Yokohama, multi-day trips to Kyoto/Osaka and seasonal ski trips to Yuzawa/Naeba/Karuizawa) with typical facts, approximate distance and drive time from Tokyo where applicable, and the page for each. Only areas actually served are listed.

Input parameters:

- `locale` (string): BCP 47 locale for names and messages: en, ja, zh-CN, zh-TW, ko, th, id, fr, de, es or it. Defaults to en.

### `estimate_charter_bus_price` (~175 tokens)

Estimate a charter bus fare

Calculates the fare structure of a charter bus trip under Japan's time + distance fare system (billable hours including roll-call, billable km including empty running, night hours, relief-driver flags). Returns a yen reference estimate only when the published rate table has been verified and all routing inputs are present; otherwise returns status 'quote_required'. Never a confirmed price.

Input parameters:

- `days` (array): One entry per operating day.
- `locale` (string): BCP 47 locale for names and messages: en, ja, zh-CN, zh-TW, ko, th, id, fr, de, es or it. Defaults to en.
- `vehicle_id` (string, required): Vehicle id from list_charter_bus_options, e.g. coach-45.
- `vehicles` (integer): Number of identical vehicles.

### `create_quote_request` (~521 tokens)

Send a quote request

Sends a charter quote request to Tokyo Charter Bus staff and returns a request reference. Call ONLY after the user has reviewed the details and explicitly confirmed sending them, and agreed to the privacy policy (set user_confirmed and privacy_consent to true). This does not book or reserve a vehicle; staff reply with a written quotation.

Input parameters:

- `add_ons` (object): Optional add-on vehicles, only together with this bus/coach request: private cars (taxi/hire-car licence) and luggage vans.
- `allow_auxiliary_seats` (boolean): false = do not plan on fold-down auxiliary seats.
- `carry_on_bags` (integer)
- `company` (string)
- `country` (string)
- `days` (array)
- `destination` (string, required)
- `destination_prefecture` (string): JIS prefecture code 01-47 of the main destination.
- `dropoff_location` (string)
- `email` (string, required)
- `end_date` (string): YYYY-MM-DD, empty for a one-day trip.
- `group_type` (string)
- `guide_language` (string)
- `idempotency_key` (string): Optional UUID to make retries safe.
- `itinerary_notes` (string)
- `large_suitcases` (integer)
- `locale` (string): BCP 47 locale for names and messages: en, ja, zh-CN, zh-TW, ko, th, id, fr, de, es or it. Defaults to en.
- `name` (string, required)
- `notes` (string)
- `passengers` (integer, required)
- `phone` (string)
- `pickup_location` (string, required)
- `pickup_prefecture` (string): JIS prefecture code 01-47 of the pick-up (e.g. 13 Tokyo, 12 Chiba for Narita).
- `pickup_time` (string): HH:MM
- `privacy_consent` (boolean, required): Must be true: the user agreed to the privacy policy for this request.
- `start_date` (string, required): YYYY-MM-DD
- `user_confirmed` (boolean, required): Must be true: the user explicitly confirmed sending this request.
- `vehicle_type` (string): Bus type, 'multiple', 'any', or 'alphard-7' for a 7-seat private car with driver (max 6 passengers per car; hire-car licence; quote only).
- `vehicles` (integer)
- `wheelchair_user` (boolean)

### `get_quote_status` (~116 tokens)

Get quote request status

Returns the status of an existing quote request. Requires both the request reference (TCB-…) and the e-mail address used for the request; returns no contact details.

Input parameters:

- `email` (string, required)
- `locale` (string): BCP 47 locale for names and messages: en, ja, zh-CN, zh-TW, ko, th, id, fr, de, es or it. Defaults to en.
- `reference` (string, required): Request reference, e.g. TCB-261101-ABCDE.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dang13021993-tokyocharterbus/tokyocharterbus#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 65
- 2026-11-19: 64
- 2026-11-18: 64
- 2026-11-17: 63
- 2026-11-16: 63
- 2026-11-15: 62
- 2026-11-14: 62
- 2026-11-13: 61
- 2026-11-12: 61
- 2026-11-11: 61
- 2026-11-10: 60
- 2026-11-09: 60
- 2026-11-08: 59
- 2026-11-07: 59
- 2026-11-06: 58

## Common questions

### What is the Tokyo Charter Bus MCP server?

Tokyo Charter Bus is an MCP server listed in the public MCP registry as io.github.dang13021993/tokyocharterbus. Discover Tokyo charter coaches, routes and reference fares. Quotations need user confirmation. This page covers its hosted endpoint (https://tokyocharterbus.com/mcp).

### Is the Tokyo Charter Bus MCP server safe to use?

Tokyo Charter Bus scores 65 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 Tokyo Charter Bus MCP server expose?

Tokyo Charter Bus exposes 5 tools: list_charter_bus_options, get_service_areas_and_routes, estimate_charter_bus_price, create_quote_request, get_quote_status. Their descriptions and schemas cost roughly 1,251 tokens of context every time the server is loaded.

### Does the Tokyo Charter Bus MCP server require authentication?

No. We connected to Tokyo Charter Bus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Tokyo Charter Bus MCP server still maintained?

Tokyo Charter Bus 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 Tokyo Charter Bus MCP server?

VerifyMCP ran 13 checks on Tokyo Charter Bus, 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.

## Links

- Remote endpoint: https://tokyocharterbus.com/mcp
- Website: https://tokyocharterbus.com/
- Changelog RSS feed: https://verifymcp.io/servers/dang13021993-tokyocharterbus/tokyocharterbus.xml
- Changelog JSON feed: https://verifymcp.io/servers/dang13021993-tokyocharterbus/tokyocharterbus/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dang13021993-tokyocharterbus/tokyocharterbus.json
- HTML version of this page: https://verifymcp.io/servers/dang13021993-tokyocharterbus/tokyocharterbus
