Japan RuleWatch
REMOTE · JAPAN-RULEWATCH-MCP-MAINNET.KADOPI.WORKERS.DEV · SCANNED SEP 20
Japan tourism entry and ecommerce evidence MCP for business agents; free tools and x402 pack.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 560 tokens (~80/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 9% 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
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · japan-rulewatch-mcp-mainnet.kadopi.workers.dev
claude mcp add --transport http kadopi-japan-rulewatch-mcp 'https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp'
{
"mcpServers": {
"kadopi-japan-rulewatch-mcp": {
"url": "https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp"
}
}
} {
"servers": {
"kadopi-japan-rulewatch-mcp": {
"type": "http",
"url": "https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp"
}
}
} [mcp_servers.kadopi-japan-rulewatch-mcp] url = "https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp"
{
"$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 mcp add kadopi-japan-rulewatch-mcp --url 'https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp' --transport streamable-http
mcp_servers:
kadopi-japan-rulewatch-mcp:
url: "https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp" {
"McpServers": {
"kadopi-japan-rulewatch-mcp": {
"Transport": "http",
"Url": "https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp"
}
}
} assistant mcp add kadopi-japan-rulewatch-mcp -t streamable-http -u 'https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp'
{
"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.
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 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 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.
- 14 Sept 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.
- 13 Sept 26 0
- Server version: 0.1.0 → 0.1.1 functional
- 12 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 11 Sept 26 55
First indexed and scored.
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 20 Sept 2026 · Probed https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kadopi.workers.dev | CN=WE1,O=Google Trust Services,C=US | 13 Aug 2026 | 11 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7378f7e851e7d509138dab0d6217f927 |
| SANs: kadopi.workers.dev, *.kadopi.workers.dev | ||||||
| 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 japan-rulewatch-mcp-mainnet.kadopi.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | 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://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcp | Inconclusive | 405 |
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 →
get_commercial_terms ~46
Free: return the current business-only commercial terms profile for a supported paid product. A status other than ready means Mainnet purchase is unavailable.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | yes | – |
No output schema declared.
No examples provided.
get_entry_pack ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accepted_terms_sha256 | string | – | – |
| accepted_terms_version | string | – | – |
| business_purchase_confirmed | boolean | – | – |
| buyer_business_name | string | – | – |
| buyer_country_code | string | – | – |
| language | string | yes | – |
| pack_id | string | yes | – |
No output schema declared.
No examples provided.
get_evidence_pack ~52
Return a concise evidence pack for one rule ID returned by search_rules. Includes official URLs, scope limits, and no legal-compliance verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Exact rule ID returned by search_rules |
No output schema declared.
No examples provided.
get_tourism_evidence_pack ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptsReservationOnPlatform | boolean | – | – |
| actsAsContractingParty | boolean | – | – |
| collectsTravelPayment | boolean | – | – |
| handlesCancellationOrRefund | boolean | – | – |
No output schema declared.
No examples provided.
get_tourism_preflight ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptsReservationOnPlatform | boolean | – | – |
| actsAsContractingParty | boolean | – | – |
| collectsTravelPayment | boolean | – | – |
| handlesCancellationOrRefund | boolean | – | – |
No output schema declared.
No examples provided.
search_entry_cases ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | yes | – |
| language | string | yes | – |
| region_id | string | yes | – |
No output schema declared.
No examples provided.
search_rules ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Japanese or English search terms, maximum 200 characters |
No output schema declared.
No examples provided.
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.