Remote MCP server that lets an assistant search Japanese laws, look up corporations and find official statistics, with English-normalized metadata.
What you can do
Search Japanese laws and regulations by keyword, returning English-normalized metadata and matched Japanese text
Fetch the original Japanese text of a law by law id or revision id, optionally a single article
Look up Japanese corporations by partial name or 13-digit corporate number
Search Japanese official e-Stat statistics tables by keyword and return English-keyed table metadata
When to use it
Useful when you need Japanese legal text, corporate registry details or official statistics inside an assistant session, and want English-labeled metadata while keeping the authentic Japanese source text and attribution.
Requirements
Remote streamable HTTP endpoint, no installation. No authentication or API key for the law tools. The corporation lookup needs a free National Tax Agency application ID, and the statistics search needs a free e-Stat application ID. Network access required.
Before you install
Two tools depend on free application IDs from Japanese public agencies, which you must obtain and supply. Results are Japanese-language source data with English-normalized metadata, so Japanese keywords work best. Returned legal text carries a required source attribution that should be preserved.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.netlify.japan-data-mcp%2Fjapan-data-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parameterslimitkeywordrequired
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. Typical flow: search_japanese_law -> get_law_text.
Parameterslaw_idrequiredarticlemax_chars
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.
Parametersnamecorporate_number
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.
Parameterslimitkeywordrequired
Version history
1
v0.1.0LatestSep 16, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.