Skip to content

japanlaw.org — Japanese law MCP server

org.japanlaw/japanese-lawjapanlaw.orgstreamable-httpv2.0.1Scanned

Japanese statutes and the Ministry of Justice's English, cited to the item, every line sourced.

9 tools: 9 only read.

Tools: 0 delete, 0 irreversible, 0 write, 9 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the japanlaw.org — Japanese law MCP server can do

The japanlaw.org — Japanese law MCP server is published by japanlaw.org, a domain the MCP Registry verified. It has 9 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 2.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Only reads 9Show 9 read-only tools
  • fetchRead in full a law or provision search found, by its id.No findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.
    Description, as the server wrote it
    Read in full a law or provision search found, by its id. A provision's id (labor-standards-act/art-36) returns it as Markdown: the Japanese text with each paragraph's English under it, every English line marked as the Ministry of Justice's translation, the Ministry's with a slip corrected, or machine translation; its address and URLs on every line; what it cites and what cites it; and its sources. A law's id (labor-standards-act) returns the law's overview — what it is for, who it applies to, how it is enforced — the texts held, and its outline, never its whole text. A japanlaw.org URL is accepted as an id too. A provision is read in the text in force unless asOf (a day) or version names another text held: an earlier one, or one an amendment not yet in force will leave.

    Annotations the server declares

    • title: Read a provision or a law
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_amendmentsWhat an amendment to a Japanese law changes, and when; for what changes across every law between two days, list_changes.No findings

    Why it is in this group

    • The name "get_amendments" says "get": a word for reading.
    Description, as the server wrote it
    What an amendment to a Japanese law changes, and when; for what changes across every law between two days, list_changes. A law's amendments whose changes japanlaw.org holds: the amending Act (titles, law number), the day it takes effect, whether it is in force, not yet in force or since replaced (state), how many provisions it changes, adds and removes, and its version — the text it leaves, which get_provision and fetch read where textHeld is true. With version — {"law": "labor-standards-act", "version": "20270401_508AC0000000060"} — every provision that amendment changes, its wording before and after in Japanese and English, and whose each English is (beforeEnglishWhose, afterEnglishWhose). A long one stops at a provision; continued.cursor, passed back as cursor with the same version, goes on. An amendment e-Gov publishes no text for is named as such (comparedAcross, textPublished false): its changes are listed with the next amendment's and cannot be told apart from them — never describe them as its own. One whose changes are not held says so; never describe its changes from memory. Link each amendment by its url.

    Annotations the server declares

    • title: See what amendments changed
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_citing_provisionsFind the provisions that refer to a given one — in the same law, in other laws, and in the Cabinet and Ministerial Orders (政令, 省令) that set the details it leaves to them: every pro…No findings

    Why it is in this group

    • The name "get_citing_provisions" says "get": a word for reading.
    Description, as the server wrote it
    Find the provisions that refer to a given one — in the same law, in other laws, and in the Cabinet and Ministerial Orders (政令, 省令) that set the details it leaves to them: every provision in the laws japanlaw.org holds that cites the given one. Each with its law, designation, the words it cites with, an id for fetch and its url; link each one you name by its fromUrl. Call it with law and address, as get_provision: {"law": "labor-standards-act", "address": "Article 36(1)"}.

    Annotations the server declares

    • title: Find what cites a provision
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_definitionsWhat a word means in a Japanese law that defines it.No findings

    Why it is in this group

    • The name "get_definitions" says "get": a word for reading.
    Description, as the server wrote it
    What a word means in a Japanese law that defines it. The words a law defines for itself (定義語): inside that law, and only as far as each definition reaches, the word means what the statute says, not what it means in everyday speech or in another law. For each, the statute's own words (statuteJa), its reading, its English and whose that is (englishWhose), a plain explanation by japanlaw.org (explanation, in lang), where it is defined (definedAt, url) and how far it reaches (scope, scopeLabel). With address — {"law": "labor-standards-act", "address": "art-36"} — the definitions that apply in that provision, because its text uses the word, and japanlaw.org's explanations of the words of Japanese law it uses (concepts: 施行, 政令, 附則…). Call it before explaining what a provision means. term narrows the answer to one word, in Japanese, its reading or its English. A law with many terms stops at one; continued.cursor, passed back as cursor with the same arguments, goes on. The text in force only.

    Annotations the server declares

    • title: Look up the words a law defines
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_lawWhat a Japanese law is for, who it applies to, and its chapters and articles.No findings

    Why it is in this group

    • The name "get_law" says "get": a word for reading.
    Description, as the server wrote it
    What a Japanese law is for, who it applies to, and its chapters and articles. One law: titles, number, kind, when the text in force took effect, the texts held (versions: in force, not yet in force, no longer in force, each with the days it stands), how much of it has the Ministry's English, and this site's plain description of it — what it is for, who it applies to and who it does not, and on request (aspect) its exceptions and how it is enforced — each claim with the provisions it rests on (basis). Then its outline: by default the parts and chapters of the main text (編, 章); outline "articles" lists every article (for a very long law, its headings instead), and under (a heading's path, such as ch-4) lists everything under that heading. outlineUrl turns an outline path into its page.

    Annotations the server declares

    • title: Describe one law
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_provision日本の法令の条・項・号の本文を読む。引用や説明の前に確かめる(改正で文言が変わっていることがある)。 Read the text of an article, paragraph or item of a Japanese law, to quote or explain it: the wording may have changed since a mo…No findings

    Why it is in this group

    • The name "get_provision" says "get": a word for reading.
    Description, as the server wrote it
    日本の法令の条・項・号の本文を読む。引用や説明の前に確かめる(改正で文言が変わっていることがある)。 Read the text of an article, paragraph or item of a Japanese law, to quote or explain it: the wording may have changed since a model learned it. One article, paragraph or item of a law, with everything under it. Call it with law and address: {"law": "labor-standards-act", "address": "art-36"}, or {"law": "労働基準法", "address": "第三十二条の三第一項"}. For each paragraph and item, the Japanese text (textJa), its English (textEn) and whose that English is (englishWhose: ministry — the Ministry of Justice's translation; corrected — the Ministry's with a slip this site corrected; machine — this site's machine translation, not official), and its url. Also the terms it defines, how many provisions it cites and how many cite it (references "lists" names them), and the official e-Gov page. A very long one — a big appended table, a 附則 of many articles — stops at a provision; continued.cursor, passed back as cursor with the same address, goes on from there. Shown to the reader as a card where the chat app can draw one. The text in force by default; asOf (a day) or version reads another text held — as it stood on a past day, or as an amendment not yet in force will leave it — and version says which text the answer is. Quoting it, link its url (the reader's page, with the English marked), not e-Gov's, and say whose English each quoted paragraph is.

    Annotations the server declares

    • title: Read one provision
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_changesWhat changes in Japanese law between two days, across every law japanlaw.org holds — 来年施行される改正、4月1日に変わる法令 — or one law's, or one topic's.No findings

    Why it is in this group

    • The name "list_changes" says "list": a word for reading.
    Description, as the server wrote it
    What changes in Japanese law between two days, across every law japanlaw.org holds — 来年施行される改正、4月1日に変わる法令 — or one law's, or one topic's. Each change: the day it takes effect (day: on that day; by, a day a Cabinet Order sets, that day at the latest; open, not set yet), whether it is still to come, the law, the amending Act (titles, law number), its version, and its url. With no until, every change still to come is listed, those with no day yet last; since defaults to today. A long list stops at limit; continued.cursor, passed back as cursor with the same arguments, goes on. For what one change does, provision by provision, call get_amendments with its law and version. Link each change by its url.

    Annotations the server declares

    • title: See what changes across the laws
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_lawsCheck whether japanlaw.org holds a law, and find the name to pass as law.No findings

    Why it is in this group

    • The name "list_laws" says "list": a word for reading.
    Description, as the server wrote it
    Check whether japanlaw.org holds a law, and find the name to pass as law. Every law japanlaw.org holds — or only those of one kind (法律 Act, 政令 Cabinet Order, 省令 Ministerial Order…), of one topic, or whose names hold query's words — each with its Japanese and English title, kind, law number and url; get_law has the rest. total counts the laws listed, held all the laws held, and kinds counts them by kind. A law not in the whole list is not held, whatever its kind — a 条例 (a prefecture's or city's ordinance) included — so say so rather than quoting its text from memory.

    Annotations the server declares

    • title: List the laws held
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:22 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://japanlaw.org/.well-known/oauth-protected-resource/mcp
Authorization servers
https://japanlaw.org
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes

Posture changes

  1. Nov 8, 2026
    • RFC 9728 protected resource metadata: none to https://japanlaw.org/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://japanlaw.org
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://japanlaw.org/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://japanlaw.org; Dynamic client registration: not observed -> yes (and …View diff
    • RFC 9728 protected resource metadata: none to https://japanlaw.org/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://japanlaw.org
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes
  3. Tools1 added, 8 changed.+1 added~8 changedView diff

Install

Pinned to version 2.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http japanese-law https://japanlaw.org/mcp
claude mcp add --transport http japanese-law https://japanlaw.org/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__japanese-law__search",
      "mcp__japanese-law__fetch",
      "mcp__japanese-law__list_laws",
      "mcp__japanese-law__get_law",
      "mcp__japanese-law__get_provision",
      "mcp__japanese-law__get_citing_provisions",
      "mcp__japanese-law__get_definitions",
      "mcp__japanese-law__get_amendments",
      "mcp__japanese-law__list_changes"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as japanese-law. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/org.japanlaw/japanese-law/verify?hash=786fffb27b0b71709aa153ba83fc1c44bf916d159ba01eb95347d9c25af95c62" | jq -e '.changed == false'

Pinned hash 786fffb27b0b, from Nov 16, 2026, 01:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/org.japanlaw/japanese-law/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for org.japanlaw/japanese-law
[![Anlyon Radar](https://radar.anlyon.com/badge/org.japanlaw/japanese-law.svg)](https://radar.anlyon.com/servers/org.japanlaw/japanese-law)

Source: MCP Registry. Synced Nov 2, 2026, 17:18 UTC.

japanlaw.org — Japanese law MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the japanlaw.org — Japanese law MCP server safe?

No scan can promise that. What its definitions show: 9 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the japanlaw.org — Japanese law MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the japanlaw.org — Japanese law MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the japanlaw.org — Japanese law MCP server have?

9 tools: 9 read. search, fetch, list_laws, get_law, get_provision, get_citing_provisions, get_definitions, get_amendments and 1 more.

Does the japanlaw.org — Japanese law MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the japanlaw.org — Japanese law MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the japanlaw.org — Japanese law MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.