# Japan RuleWatch (remote · japan-rulewatch-mcp-mainnet.kadopi.workers.dev)

Japan tourism entry and ecommerce evidence MCP for business agents; free tools and x402 pack.

- Trust score: 60/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `japan-rulewatch-mcp-mainnet.kadopi.workers.dev`: 60/100 (this document), [markdown](https://verifymcp.io/servers/kadopi-japan-rulewatch-mcp/japan-rulewatch-mcp-mainnet.md), [page](https://verifymcp.io/servers/kadopi-japan-rulewatch-mcp/japan-rulewatch-mcp-mainnet)

## Channel facts

- Endpoint: `https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## 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-09-20.

- **Endpoint Security**: 46/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 7 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 63/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 560 tokens (~80/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 70/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 9% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Japan RuleWatch MCP server?

Japan RuleWatch is a hosted endpoint at https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/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 kadopi-japan-rulewatch-mcp 'https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "kadopi-japan-rulewatch-mcp": {
      "url": "https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kadopi-japan-rulewatch-mcp": {
      "type": "http",
      "url": "https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.kadopi-japan-rulewatch-mcp]
url = "https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kadopi-japan-rulewatch-mcp": {
      "type": "remote",
      "url": "https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kadopi-japan-rulewatch-mcp --url 'https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kadopi-japan-rulewatch-mcp:
    url: "https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "kadopi-japan-rulewatch-mcp": {
      "Transport": "http",
      "Url": "https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add kadopi-japan-rulewatch-mcp -t streamable-http -u 'https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "kadopi-japan-rulewatch-mcp": {
      "type": "http",
      "url": "https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/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-09-20 (score 60, +1)

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

### 2026-09-18 (score 59, +1)

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

### 2026-09-16 (score 58, +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-09-14 (score 57, +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-09-13 (score 56, 0)

- [functional] Server version: 0.1.0 → 0.1.1

### 2026-09-12 (score 56, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-11 (score 55)

First indexed and scored.

## MCP tools (7)

### `search_rules` (~64 tokens)

Search a small curated index of official Japanese sources about mail-order sales advertising. Use this before get_evidence_pack. Results are evidence pointers, not legal conclusions.

Input parameters:

- `limit` (integer)
- `query` (string, required): Japanese or English search terms, maximum 200 characters

### `get_commercial_terms` (~46 tokens)

Free: return the current business-only commercial terms profile for a supported paid product. A status other than ready means Mainnet purchase is unavailable.

Input parameters:

- `product_id` (string, required)

### `search_entry_cases` (~96 tokens)

Free: search the fixed Japan tourism entry-case catalog by region, activity, and language. Returns a model-case preview, key decision themes and what the paid preparation pack adds. It does not include source locations, contact routes, inquiry text or an action plan. Japan Rule is a private commercial service, not a government service.

Input parameters:

- `activity` (string, required)
- `language` (string, required)
- `region_id` (string, required)

### `get_entry_pack` (~115 tokens)

Paid: return the fixed Iya soba entry-preparation pack with sources, contacts, consultation text, unknowns, and next actions. It gives no customer-specific legal verdict. Japan Rule is not a government service.

Input parameters:

- `accepted_terms_sha256` (string)
- `accepted_terms_version` (string)
- `business_purchase_confirmed` (boolean)
- `buyer_business_name` (string)
- `buyer_country_code` (string)
- `language` (string, required)
- `pack_id` (string, required)

### `get_evidence_pack` (~52 tokens)

Return a concise evidence pack for one rule ID returned by search_rules. Includes official URLs, scope limits, and no legal-compliance verdict.

Input parameters:

- `id` (string, required): Exact rule ID returned by search_rules

### `get_tourism_preflight` (~86 tokens)

Free: classify a Japan-bound hotel service flow into the supported A/B/C model, list missing facts, and flag manual review. It does not return primary-source evidence.

Input parameters:

- `acceptsReservationOnPlatform` (boolean)
- `actsAsContractingParty` (boolean)
- `collectsTravelPayment` (boolean)
- `handlesCancellationOrRefund` (boolean)

### `get_tourism_evidence_pack` (~101 tokens)

Paid: return official Japanese primary-source URLs, evidence locations, checked dates, source versions, general requirements, traveler-screen checks, and re-check triggers for a complete supported A/B/C flow. This is informational evidence, not a legal verdict.

Input parameters:

- `acceptsReservationOnPlatform` (boolean)
- `actsAsContractingParty` (boolean)
- `collectsTravelPayment` (boolean)
- `handlesCancellationOrRefund` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kadopi-japan-rulewatch-mcp/japan-rulewatch-mcp-mainnet#diagnostics

## Score history

- 2026-09-20: 60
- 2026-09-19: 59
- 2026-09-18: 59
- 2026-09-17: 58
- 2026-09-16: 58
- 2026-09-15: 57
- 2026-09-14: 57
- 2026-09-13: 56
- 2026-09-12: 56
- 2026-09-11: 55

## Common questions

### What is the Japan RuleWatch MCP server?

Japan RuleWatch is an MCP server listed in the public MCP registry as io.github.kadopi/japan-rulewatch-mcp. Japan tourism entry and ecommerce evidence MCP for business agents; free tools and x402 pack. This page covers its hosted endpoint (https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp).

### Is the Japan RuleWatch MCP server safe to use?

Japan RuleWatch scores 60 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 RuleWatch MCP server expose?

Japan RuleWatch exposes 7 tools: search_rules, get_commercial_terms, search_entry_cases, get_entry_pack, get_evidence_pack, and 2 more. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.

### Does the Japan RuleWatch MCP server require authentication?

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

### Is the Japan RuleWatch MCP server still maintained?

Japan RuleWatch is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp
- Repository: https://github.com/kadopi/japan-rulewatch-mcp
- Changelog RSS feed: https://verifymcp.io/servers/kadopi-japan-rulewatch-mcp/japan-rulewatch-mcp-mainnet.xml
- Changelog JSON feed: https://verifymcp.io/servers/kadopi-japan-rulewatch-mcp/japan-rulewatch-mcp-mainnet.json
- HTML version of this page: https://verifymcp.io/servers/kadopi-japan-rulewatch-mcp/japan-rulewatch-mcp-mainnet