# Japan Inbound & Cross-Border Rules MCP (remote · jp-rules-mcp.onrender.com)

Official Japan inbound travel & cross-border rules for AI Agents (Tax-Free, Shinkansen).

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `jp-rules-mcp.onrender.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/toymachine325-blip-jp-rules-mcp/jp-rules-mcp.md), [page](https://verifymcp.io/servers/toymachine325-blip-jp-rules-mcp/jp-rules-mcp)

## Channel facts

- Endpoint: `https://jp-rules-mcp.onrender.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 not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 816 tokens (~272/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the Japan Inbound & Cross-Border Rules MCP server?

Japan Inbound & Cross-Border Rules MCP is a hosted endpoint at https://jp-rules-mcp.onrender.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 toymachine325-blip-jp-rules-mcp 'https://jp-rules-mcp.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "toymachine325-blip-jp-rules-mcp": {
      "url": "https://jp-rules-mcp.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "toymachine325-blip-jp-rules-mcp": {
      "type": "http",
      "url": "https://jp-rules-mcp.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.toymachine325-blip-jp-rules-mcp]
url = "https://jp-rules-mcp.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "toymachine325-blip-jp-rules-mcp": {
      "type": "remote",
      "url": "https://jp-rules-mcp.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add toymachine325-blip-jp-rules-mcp --url 'https://jp-rules-mcp.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  toymachine325-blip-jp-rules-mcp:
    url: "https://jp-rules-mcp.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "toymachine325-blip-jp-rules-mcp": {
      "Transport": "http",
      "Url": "https://jp-rules-mcp.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add toymachine325-blip-jp-rules-mcp -t streamable-http -u 'https://jp-rules-mcp.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "toymachine325-blip-jp-rules-mcp": {
      "type": "http",
      "url": "https://jp-rules-mcp.onrender.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 62, +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-18 (score 61, +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-16 (score 60, +1)

- [security] Tool “check_jp_travel_compliance” rewrote its description, which is the text the model reads
- [security] Tool “query_jp_inbound_rules” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “query_jp_inbound_rules” reworded the description of “apiKey”

### 2026-11-15 (score 59)

First indexed and scored.

## MCP tools (3)

### `list_jp_rule_categories` (~146 tokens)

【無料 / 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.

### `query_jp_inbound_rules` (~292 tokens)

【無料 / Free 0 JPY】日本のインバウンド旅行・越境規制ルール（2026年11月改正新免税制度、JR新幹線特大荷物、祝日大型連休混雑、税関検疫）をカテゴリ・キーワードで英語検索します。APIキー不要・課金0円。 / 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). Free, no API key required.

Input parameters:

- `apiKey` (string): オプションのAIお小遣いキー（本ツールは無料のため渡されても課金されません） / Optional AI allowance API key (query is free, no charge even if provided).
- `category` (string): ルールカテゴリ ('tax_free', 'rail_luggage', 'holidays', 'customs') / Rule category filter ('tax_free', 'rail_luggage', 'holidays', or 'customs')
- `keyword` (string): 検索キーワード / Keyword to search across rules, facts, or summaries
- `limit` (number): 取得最大件数（デフォルト: 10） / Maximum number of rules to return (default: 10)

### `check_jp_travel_compliance` (~378 tokens)

【有料 / 30 JPY】旅行者の購入額・荷物寸法・旅行日を指定し、日本の法規制適合性（新免税対象可否・特大荷物事前予約義務・祝日混雑リスク）を即決自動判定します。AIお小遣い月額上限ロック連動（1回30円、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. 30 JPY per check, requires AI allowance API key.

Input parameters:

- `apiKey` (string): AIお小遣いキー / AI allowance API key (sk_souon_...). Authorization Bearer header also supported.
- `baggageTotalCm` (number): 荷物3辺合計（cm。checkType === 'shinkansen_baggage' で使用） / Total baggage dimensions in cm (length + width + height) (for shinkansen_baggage check)
- `checkType` (string, required): 判定種別 ('tax_free', 'shinkansen_baggage', 'holiday_peak') / Compliance check type: 'tax_free', 'shinkansen_baggage', or 'holiday_peak'
- `purchaseAmountJpy` (number): 購入金額（税抜日本円。checkType === 'tax_free' で使用） / Purchase amount in JPY excluding tax (for tax_free check)
- `travelDate` (string): 旅行日 (YYYY-MM-DD。checkType === 'holiday_peak' で使用) / Travel date in YYYY-MM-DD format (for holiday_peak check)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/toymachine325-blip-jp-rules-mcp/jp-rules-mcp#diagnostics

## Score history

- 2026-11-21: 62
- 2026-11-20: 62
- 2026-11-19: 61
- 2026-11-18: 61
- 2026-11-17: 60
- 2026-11-16: 60
- 2026-11-15: 59

## Common questions

### What is the Japan Inbound & Cross-Border Rules MCP server?

Japan Inbound & Cross-Border Rules MCP is listed in the public MCP registry as io.github.toymachine325-blip/jp-rules-mcp. Official Japan inbound travel & cross-border rules for AI Agents (Tax-Free, Shinkansen). This page covers its hosted endpoint (https://jp-rules-mcp.onrender.com/mcp).

### Is the Japan Inbound & Cross-Border Rules MCP server safe to use?

Japan Inbound & Cross-Border Rules MCP scores 62 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 Japan Inbound & Cross-Border Rules MCP server expose?

Japan Inbound & Cross-Border Rules MCP exposes 3 tools: list_jp_rule_categories, query_jp_inbound_rules, check_jp_travel_compliance. Their descriptions and schemas cost roughly 816 tokens of context every time the server is loaded.

### Does the Japan Inbound & Cross-Border Rules MCP server require authentication?

No. We connected to Japan Inbound & Cross-Border Rules MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Japan Inbound & Cross-Border Rules MCP server still maintained?

Japan Inbound & Cross-Border Rules MCP 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 Japan Inbound & Cross-Border Rules MCP server?

VerifyMCP ran 12 checks on Japan Inbound & Cross-Border Rules MCP, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Japan Inbound & Cross-Border Rules MCP: Authorization. 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://jp-rules-mcp.onrender.com/mcp
- Repository: https://github.com/toymachine325-blip/jp-rules-mcp.git
- Changelog RSS feed: https://verifymcp.io/servers/toymachine325-blip-jp-rules-mcp/jp-rules-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/toymachine325-blip-jp-rules-mcp/jp-rules-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/toymachine325-blip-jp-rules-mcp/jp-rules-mcp.json
- HTML version of this page: https://verifymcp.io/servers/toymachine325-blip-jp-rules-mcp/jp-rules-mcp
