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.

Tokyo Charter Bus

REMOTE · TOKYOCHARTERBUS.COM

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

+3 this week 65 Trust /100

Last scanned (19 hours ago)

Scores higher than 46% 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 Security57
Transport & Reachability100
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 57% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 6 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 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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 13 Nov 26 0
    • Tool “list_charter_bus_options” rewrote its description, which is the text the model reads security
  • 11 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.

  • 9 Nov 26 +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.

  • 7 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
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://tokyocharterbus.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tokyocharterbus.com CN=WE1,O=Google Trust Services,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 233faa93f600a2d4133d58f689e995f3
SANs: tokyocharterbus.com
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 tokyocharterbus.com. — Not signed

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

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.

NameTypeReqDescription
add_onsobject–Optional add-on vehicles, only together with this bus/coach request: private cars (taxi/hire-car licence) and luggage vans.
allow_auxiliary_seatsboolean–false = do not plan on fold-down auxiliary seats.
carry_on_bagsinteger––
companystring––
countrystring––
daysarray––
destinationstringyes–
destination_prefecturestring–JIS prefecture code 01-47 of the main destination.
dropoff_locationstring––
emailstringyes–
end_datestring–YYYY-MM-DD, empty for a one-day trip.
group_typestring––
guide_languagestring––
idempotency_keystring–Optional UUID to make retries safe.
itinerary_notesstring––
large_suitcasesinteger––
localestring–BCP 47 locale for names and messages: en, ja, zh-CN, zh-TW, ko, th, id, fr, de, es or it. Defaults to en.
namestringyes–
notesstring––
passengersintegeryes–
phonestring––
pickup_locationstringyes–
pickup_prefecturestring–JIS prefecture code 01-47 of the pick-up (e.g. 13 Tokyo, 12 Chiba for Narita).
pickup_timestring–HH:MM
privacy_consentbooleanyesMust be true: the user agreed to the privacy policy for this request.
start_datestringyesYYYY-MM-DD
user_confirmedbooleanyesMust be true: the user explicitly confirmed sending this request.
vehicle_typestring–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).
vehiclesinteger––
wheelchair_userboolean––

No output schema declared.

No examples provided.

estimate_charter_bus_price ~175

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.

NameTypeReqDescription
daysarray–One entry per operating day.
localestring–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_idstringyesVehicle id from list_charter_bus_options, e.g. coach-45.
vehiclesinteger–Number of identical vehicles.

No output schema declared.

No examples provided.

get_quote_status ~116

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.

NameTypeReqDescription
emailstringyes–
localestring–BCP 47 locale for names and messages: en, ja, zh-CN, zh-TW, ko, th, id, fr, de, es or it. Defaults to en.
referencestringyesRequest reference, e.g. TCB-261101-ABCDE.

No output schema declared.

No examples provided.

get_service_areas_and_routes ~144

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.

NameTypeReqDescription
localestring–BCP 47 locale for names and messages: en, ja, zh-CN, zh-TW, ko, th, id, fr, de, es or it. Defaults to en.

No output schema declared.

No examples provided.

list_charter_bus_options ~295

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.

NameTypeReqDescription
allow_auxiliary_seatsboolean–false = do not count fold-down auxiliary seats.
carry_on_bagsinteger–Carry-on bags kept in the cabin.
categorystring–Filter by vehicle category.
large_suitcasesinteger–Number of large suitcases.
localestring–BCP 47 locale for names and messages: en, ja, zh-CN, zh-TW, ko, th, id, fr, de, es or it. Defaults to en.
passengersinteger–Number of passengers, to get a recommended combination.

No output schema declared.

No examples provided.

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.

remote · tokyocharterbus.com

# add to Claude Code
claude mcp add --transport http dang13021993-tokyocharterbus 'https://tokyocharterbus.com/mcp'
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.