app.netlify.japan-data-mcp/japan-data-mcp
REMOTE · JAPAN-DATA-MCP.NETLIFY.APP · SCANNED AUG 24
Japanese law, corporation & statistics data as MCP, normalized to English with source attribution.
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 →
Endpoint Security51
- 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 connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 503, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
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.
remote · japan-data-mcp.netlify.app
claude mcp add --transport http app-netlify-japan-data-mcp-japan-data-mcp 'https://japan-data-mcp.netlify.app/mcp'
{
"mcpServers": {
"app-netlify-japan-data-mcp-japan-data-mcp": {
"url": "https://japan-data-mcp.netlify.app/mcp"
}
}
} {
"servers": {
"app-netlify-japan-data-mcp-japan-data-mcp": {
"type": "http",
"url": "https://japan-data-mcp.netlify.app/mcp"
}
}
} [mcp_servers.app-netlify-japan-data-mcp-japan-data-mcp] url = "https://japan-data-mcp.netlify.app/mcp"
{
"$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 mcp add app-netlify-japan-data-mcp-japan-data-mcp --url 'https://japan-data-mcp.netlify.app/mcp' --transport streamable-http
mcp_servers:
app-netlify-japan-data-mcp-japan-data-mcp:
url: "https://japan-data-mcp.netlify.app/mcp" {
"McpServers": {
"app-netlify-japan-data-mcp-japan-data-mcp": {
"Transport": "http",
"Url": "https://japan-data-mcp.netlify.app/mcp"
}
}
} assistant mcp add app-netlify-japan-data-mcp-japan-data-mcp -t streamable-http -u 'https://japan-data-mcp.netlify.app/mcp'
{
"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.
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.
- 17 Aug 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.30 → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- 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. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 15 Aug 26 +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.
- 13 Aug 26 +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.
- 11 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 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.
- 8 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- 7 Aug 26 62
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 24 Aug 2026 · Probed https://japan-data-mcp.netlify.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.netlify.app,O=Netlify\, Inc,L=San Francisco,ST=California,C=US | CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US | 16 Feb 2026 | 19 Mar 2027 | ECDSA 256 | SHA256-RSA | cd5d0afb0611b5bd9d692535c0ca7c4 |
| SANs: *.netlify.app, netlify.app | ||||||
| CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 30 Mar 2021 | 29 Mar 2031 | RSA 2048 | SHA256-RSA | cf5bd062b5602f47ab8502c23ccf066 |
DNSSEC insecure
Validation of japan-data-mcp.netlify.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| netlify.app. | 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 | 503 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://japan-data-mcp.netlify.app/mcp | HTTP error | 503 | |
| http (plaintext) | http://japan-data-mcp.netlify.app/mcp | Inconclusive | 503 |
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.
get_law_text ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
No output schema declared.
No examples provided.
search_corporation ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| corporate_number | string | – | 13-digit corporate number. |
| name | string | – | Partial company name (Japanese). |
No output schema declared.
No examples provided.
search_japanese_law ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | Search term. Japanese matches the source text directly; English is best-effort. |
| limit | integer | – | Max results (1-20). |
No output schema declared.
No examples provided.
search_statistics ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | Search term for statistics tables. |
| limit | integer | – | Max results (1-20). |
No output schema declared.
No examples provided.
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.