Official Japan inbound travel & cross-border rules for AI Agents (Tax-Free, Shinkansen).
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
【有料 / 2 JPY】旅行者の購入額・荷物寸法・旅行日を指定し、日本の法規制適合性（新免税対象可否・特大荷物事前予約義務・祝日混雑リスク）を即決自動判定します。AIお小遣い月額上限ロック連動（1回2円、sk_souon_...必須）。 / Instant automated compliance evaluation for Japan inbound travel regulations: tax-free shopping eligibility (Nov 2026 reform), Shinkansen oversized baggage rules, or peak holiday congestion risk. 2 JPY per check, requires AI allowance API key.
判定種別 ('tax_free', 'shinkansen_baggage', 'holiday_peak') / Compliance check type: 'tax_free', 'shinkansen_baggage', or 'holiday_peak'
AIお小遣いキー / AI allowance API key (sk_souon_...). Authorization Bearer header also supported.
旅行日 (YYYY-MM-DD。checkType === 'holiday_peak' で使用) / Travel date in YYYY-MM-DD format (for holiday_peak check)
荷物3辺合計（cm。checkType === 'shinkansen_baggage' で使用） / Total baggage dimensions in cm (length + width + height) (for shinkansen_baggage check)
購入金額（税抜日本円。checkType === 'tax_free' で使用） / Purchase amount in JPY excluding tax (for tax_free check)
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http jp-rules-mcp https://jp-rules-mcp.onrender.com/mcp
【有料 / 2 JPY】旅行者の購入額・荷物寸法・旅行日を指定し、日本の法規制適合性（新免税対象可否・特大荷物事前予約義務・祝日混雑リスク）を即決自動判定します。AIお小遣い月額上限ロック連動（1回2円、sk_souon_...必須）。 / Instant automated compliance evaluation for Japan inbound travel regulations: tax-free shopping eligibility (Nov 2026 reform), Shinkansen oversized baggage rules, or peak holiday congestion risk. 2 JPY per check, requires AI allowance API key.
| Argument | Type | Description |
|---|---|---|
| apiKey | string | AIお小遣いキー / AI allowance API key (sk_souon_...). Authorization Bearer header also supported. |
| checkType* | string | 判定種別 ('tax_free', 'shinkansen_baggage', 'holiday_peak') / Compliance check type: 'tax_free', 'shinkansen_baggage', or 'holiday_peak' |
| travelDate | string | 旅行日 (YYYY-MM-DD。checkType === 'holiday_peak' で使用) / Travel date in YYYY-MM-DD format (for holiday_peak check) |
| baggageTotalCm | number | 荷物3辺合計（cm。checkType === 'shinkansen_baggage' で使用） / Total baggage dimensions in cm (length + width + height) (for shinkansen_baggage check) |
| purchaseAmountJpy | number | 購入金額（税抜日本円。checkType === 'tax_free' で使用） / Purchase amount in JPY excluding tax (for tax_free check) |
{
"type": "object",
"required": [
"checkType"
],
"properties": {
"apiKey": {
"type": "string",
"description": "AIお小遣いキー / AI allowance API key (sk_souon_...). Authorization Bearer header also supported."
},
"checkType": {
"enum": [
"tax_free",
"shinkansen_baggage",
"holiday_peak"
],
"type": "string",
"description": "判定種別 ('tax_free', 'shinkansen_baggage', 'holiday_peak') / Compliance check type: 'tax_free', 'shinkansen_baggage', or 'holiday_peak'"
},
"travelDate": {
"type": "string",
"description": "旅行日 (YYYY-MM-DD。checkType === 'holiday_peak' で使用) / Travel date in YYYY-MM-DD format (for holiday_peak check)"
},
"baggageTotalCm": {
"type": "number",
"description": "荷物3辺合計（cm。checkType === 'shinkansen_baggage' で使用） / Total baggage dimensions in cm (length + width + height) (for shinkansen_baggage check)"
},
"purchaseAmountJpy": {
"type": "number",
"description": "購入金額（税抜日本円。checkType === 'tax_free' で使用） / Purchase amount in JPY excluding tax (for tax_free check)"
}
}
}【無料 / Free 0 JPY】日本のインバウンド旅行・越境規制（2026年11月施行の新免税制度、JR新幹線特大荷物、祝日・大型連休混雑、税関・検疫持込制限）のカテゴリ一覧、ルール件数、最終検証日時を取得します。APIキー不要・課金0円。 / List available categories, rule counts, and verification timestamps for Japan inbound travel and cross-border regulations (tax-free reform Nov 2026, bullet train luggage, holiday rush, customs restrictions). Free, no API key required.
No arguments.
{
"type": "object",
"properties": {}
}【有料 / 2 JPY】日本のインバウンド旅行・越境規制ルール（2026年11月改正新免税制度、JR新幹線特大荷物、祝日大型連休混雑、税関検疫）をカテゴリ・キーワードで英語検索します。AIお小遣い月額上限ロック連動（1回2円、sk_souon_...必須）。 / Query official Japan inbound travel and cross-border regulatory rules in structured English JSON (tax-free reform Nov 2026, Shinkansen luggage limits, peak holiday crowding, customs/quarantine). 2 JPY per query, requires AI allowance API key.
| Argument | Type | Description |
|---|---|---|
| limit | number | 取得最大件数（デフォルト: 10） / Maximum number of rules to return (default: 10) |
| apiKey | string | AIお小遣いキー / AI allowance API key (sk_souon_...). Authorization Bearer header also supported. |
| keyword | string | 検索キーワード / Keyword to search across rules, facts, or summaries |
| category | string | ルールカテゴリ ('tax_free', 'rail_luggage', 'holidays', 'customs') / Rule category filter ('tax_free', 'rail_luggage', 'holidays', or 'customs') |
{
"type": "object",
"properties": {
"limit": {
"type": "number",
"description": "取得最大件数（デフォルト: 10） / Maximum number of rules to return (default: 10)"
},
"apiKey": {
"type": "string",
"description": "AIお小遣いキー / AI allowance API key (sk_souon_...). Authorization Bearer header also supported."
},
"keyword": {
"type": "string",
"description": "検索キーワード / Keyword to search across rules, facts, or summaries"
},
"category": {
"type": "string",
"description": "ルールカテゴリ ('tax_free', 'rail_luggage', 'holidays', 'customs') / Rule category filter ('tax_free', 'rail_luggage', 'holidays', or 'customs')"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 15, 2026.
Takes a password, API key or token as an argument, so the secret passes through the model's context and chat logs.
Fix: Read credentials from the server's own configuration (environment, OAuth) instead of a tool argument.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.