Japan Data MCP
by japan-data-mcp.netlify.app in Other
Japanese law, corporation & statistics data as MCP, normalized to English with source attribution.
https://japan-data-mcp.netlify.app/mcp- Tools
- 4
- open to any client
- Uptime
- 90.9%
- last 30 days
- Response time
- 525 ms
- 1.3 s slowest 5%
- Last check
- Passed
- 5 h ago, next in 1 h
Reliability
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"japan-data-mcp": {
"type": "http",
"url": "https://japan-data-mcp.netlify.app/mcp"
}
}
}4 tools
- search_japanese_law
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.
- get_law_text
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…
- search_corporation
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.
- search_statistics
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.
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 5 h ago | Passed | 200 | 605 ms |
| 15 h ago | Passed | 200 | 857 ms |
| 25 h ago | Passed | 200 | 525 ms |
| 34 h ago | Passed | 200 | 405 ms |
| 44 h ago | Passed | 200 | 436 ms |
Show 6 older checks
| 2 days ago | Passed | 200 | 459 ms |
| 3 days ago | Connection failed (UND_ERR_CONNECT_TIMEOUT) | - | - |
| 3 days ago | Passed | 200 | 1.3 s |
| 3 days ago | Passed | 200 | 954 ms |
| 4 days ago | Passed | 200 | 695 ms |
| 4 days ago | Passed | 200 | 500 ms |