# app.netlify.japan-data-mcp/japan-data-mcp (remote · japan-data-mcp.netlify.app)

Japanese law, corporation & statistics data as MCP, normalized to English with source attribution.

- Trust score: 20/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-24

## Components

- remote · `japan-data-mcp.netlify.app`: 20/100 (this document), [markdown](https://verifymcp.io/servers/app-netlify-japan-data-mcp-japan-data-mcp/japan-data-mcp.md), [page](https://verifymcp.io/servers/app-netlify-japan-data-mcp-japan-data-mcp/japan-data-mcp)

## Channel facts

- Endpoint: `https://japan-data-mcp.netlify.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-08-24.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 503, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 503.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the app.netlify.japan-data-mcp/japan-data-mcp server?

app.netlify.japan-data-mcp/japan-data-mcp is a hosted endpoint at https://japan-data-mcp.netlify.app/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 app-netlify-japan-data-mcp-japan-data-mcp 'https://japan-data-mcp.netlify.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-netlify-japan-data-mcp-japan-data-mcp": {
      "url": "https://japan-data-mcp.netlify.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-netlify-japan-data-mcp-japan-data-mcp": {
      "type": "http",
      "url": "https://japan-data-mcp.netlify.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-netlify-japan-data-mcp-japan-data-mcp]
url = "https://japan-data-mcp.netlify.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-netlify-japan-data-mcp-japan-data-mcp": {
      "type": "remote",
      "url": "https://japan-data-mcp.netlify.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-netlify-japan-data-mcp-japan-data-mcp --url 'https://japan-data-mcp.netlify.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-netlify-japan-data-mcp-japan-data-mcp:
    url: "https://japan-data-mcp.netlify.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-netlify-japan-data-mcp-japan-data-mcp": {
      "Transport": "http",
      "Url": "https://japan-data-mcp.netlify.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-netlify-japan-data-mcp-japan-data-mcp -t streamable-http -u 'https://japan-data-mcp.netlify.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-netlify-japan-data-mcp-japan-data-mcp": {
      "type": "http",
      "url": "https://japan-data-mcp.netlify.app/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-08-17 (score 20, −48)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.30 → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-08-15 (score 68, +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.

### 2026-08-13 (score 67, +1)

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

### 2026-08-11 (score 66, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-10 (score 64, +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-08-08 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-07 (score 62)

First indexed and scored.

## MCP tools (4)

### `search_japanese_law` (~97 tokens)

Search Japanese laws and regulations by keyword and return English-normalized metadata (law id, type, era, promulgation date, category) plus the matched Japanese text. No API key required. Japanese keywords match best; the underlying source is full-text Japanese.

Input parameters:

- `keyword` (string, required): Search term. Japanese matches the source text directly; English is best-effort.
- `limit` (integer): Max results (1-20).

### `get_law_text` (~181 tokens)

Fetch the original Japanese text of a law by its law_id or revision_id (as returned by search_japanese_law). Optionally extract a single article. Returns the authentic Japanese legal text with English-normalized metadata and the required source attribution. No API key required. Typical flow: search_japanese_law -> get_law_text.

Input parameters:

- `article` (string): Optional article number in Arabic numerals as e-Gov numbers them, e.g. "9", or "32_2" for Article 32-2. Omit to get the whole law (truncated to max_chars).
- `law_id` (string, required): law_id (e.g. "321CONSTITUTION") or revision_id from search_japanese_law results.
- `max_chars` (integer): Max characters of Japanese text to return (200-20000).

### `search_corporation` (~73 tokens)

Look up a Japanese corporation by partial name or 13-digit corporate number, returning English-keyed records (corporate number, name, address). Requires a free National Tax Agency application ID.

Input parameters:

- `corporate_number` (string): 13-digit corporate number.
- `name` (string): Partial company name (Japanese).

### `search_statistics` (~70 tokens)

Search Japanese official statistics tables (e-Stat) by keyword and return English-keyed table metadata (id, title, organization, dates). Requires a free e-Stat application ID.

Input parameters:

- `keyword` (string, required): Search term for statistics tables.
- `limit` (integer): Max results (1-20).

## Diagnostics

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

## Score history

- 2026-08-24: 20
- 2026-08-23: 20
- 2026-08-22: 20
- 2026-08-21: 20
- 2026-08-20: 20
- 2026-08-19: 20
- 2026-08-18: 20
- 2026-08-17: 20
- 2026-08-16: 68
- 2026-08-15: 68
- 2026-08-14: 67
- 2026-08-13: 67
- 2026-08-12: 66
- 2026-08-11: 66
- 2026-08-10: 64
- 2026-08-09: 63
- 2026-08-08: 63
- 2026-08-07: 62

## Common questions

### What is the app.netlify.japan-data-mcp/japan-data-mcp server?

app.netlify.japan-data-mcp/japan-data-mcp is listed in the public MCP registry as app.netlify.japan-data-mcp/japan-data-mcp. Japanese law, corporation & statistics data as MCP, normalized to English with source attribution. This page covers its hosted endpoint (https://japan-data-mcp.netlify.app/mcp).

### Is the app.netlify.japan-data-mcp/japan-data-mcp server safe to use?

app.netlify.japan-data-mcp/japan-data-mcp scores 20 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 app.netlify.japan-data-mcp/japan-data-mcp server expose?

app.netlify.japan-data-mcp/japan-data-mcp exposes 4 tools: search_japanese_law, get_law_text, search_corporation, search_statistics. Their descriptions and schemas cost roughly 421 tokens of context every time the server is loaded.

### Does the app.netlify.japan-data-mcp/japan-data-mcp server require authentication?

No. We connected to app.netlify.japan-data-mcp/japan-data-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the app.netlify.japan-data-mcp/japan-data-mcp server still maintained?

app.netlify.japan-data-mcp/japan-data-mcp is still listed as active in the MCP registry. We last reached this channel on 24 August 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-data-mcp.netlify.app/mcp
- Website: https://japan-data-mcp.netlify.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-netlify-japan-data-mcp-japan-data-mcp/japan-data-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-netlify-japan-data-mcp-japan-data-mcp/japan-data-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-netlify-japan-data-mcp-japan-data-mcp/japan-data-mcp