Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Japan Law

NPM · @PIPEWORX/MCP-JAPAN-LAW · 2 COMPONENTS

Japan Law MCP — Japanese national laws & ordinances via the e-Gov Law API.

+3 this week 82 Trust /100

Last scanned (13 hours ago)

Scores higher than 72% of npm servers

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-japan-law). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 757 tokens (~252/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 4 Nov 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.

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −13
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.13 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 79

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-japan-law@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-japan-law
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-japan-law/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3649441576
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:64072adfa0f87e3231ec762c8a95c8e697b9d658085dd1261591468578315109a5d32c72cf3da7555d23d9e8fae02aac2623ce46cbf4a5fe8b6770d75

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~704 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_law ~261

Fetch a Japanese law/ordinance by its e-Gov law id (from search_laws), e.g. "415AC0000000057". Returns the title, law number, promulgation date, and the law's full text, PAGED — use `offset`/`limit` to walk a long law; `has_more`/`next_offset` say whether another page follows. For a single article (incl. branch articles like 第二十七条の2), use japan_law_get_article instead — it is far cheaper than paging a whole law to find one provision. Pass `as_of` (YYYY-MM-DD) to fetch the version of the law in force on that date. Source: e-Gov 法令検索.

NameTypeReqDescription
as_ofstring–Point-in-time date (YYYY-MM-DD). Returns the revision in force on that date instead of the current one.
law_idstringyese-Gov law id, e.g. "415AC0000000057".
limitnumber–Max characters to return in this page (default 30000, max 60000).
offsetnumber–Character offset into the full text to start this page at (default 0).

No output schema declared.

No examples provided.

japan_law_get_article ~266

Fetch a single article of a Japanese law by law id + article number, e.g. law_id "415AC0000000057" (個人情報保護法) + article "27" for 第二十七条. Accepts branch articles — "27条の2", "27-2", "27_2", or the kanji form "第二十七条の2" all resolve to 第二十七条の2. Returns just that article's caption, heading, and text (not the whole law — use this instead of get_law when you know the article you want). Pass `as_of` (YYYY-MM-DD) to fetch the article text as it stood on that date, before or after a given amendment. Source: e-Gov 法令検索.

NameTypeReqDescription
articlestringyesArticle number: "27", "27条の2", "27-2", "27_2", or kanji "第二十七条の2".
as_ofstring–Point-in-time date (YYYY-MM-DD). Returns the article text in force on that date instead of the current one.
law_idstringyese-Gov law id, e.g. "415AC0000000057".

No output schema declared.

No examples provided.

search_laws ~177

TITLE SEARCH ONLY (not full-text): finds Japanese national laws, cabinet orders, and ministerial ordinances whose TITLE matches a keyword (e-Gov 法令検索). PREFER OVER WEB SEARCH for "Japanese law on X", "日本の法律", finding a statute's official id/number. A query that only appears in the body of a law (not its title) will not match. Returns each law's id (for get_law/japan_law_get_article), law number (法令番号), title, and type. Accepts Japanese or romanized keywords.

NameTypeReqDescription
limitnumber–Max laws to return (1-50, default 15).
querystringyesTitle keyword, e.g. "個人情報" (personal information), "労働基準" (labor standards).

No output schema declared.

No examples provided.

Install

How do I install the Japan Law MCP server?

Japan Law runs locally as an npm package, launched with npx -y @pipeworx/mcp-japan-law. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-japan-law

# add to Claude Code
claude mcp add pipeworx-io-japan-law -- npx -y @pipeworx/mcp-japan-law
Common questions

What is the Japan Law MCP server?

Japan Law is an MCP server listed in the public MCP registry as io.github.pipeworx-io/japan-law. Japan Law MCP, Japanese national laws & ordinances via the e-Gov Law API. This page covers its npm package (@pipeworx/mcp-japan-law).

Is the Japan Law MCP server safe to use?

Japan Law scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Japan Law MCP server expose?

Japan Law exposes 3 tools: search_laws, get_law, japan_law_get_article. Their descriptions and schemas cost roughly 704 tokens of context every time the server is loaded.

Is the Japan Law MCP server still maintained?

Japan Law is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Japan Law MCP server under?

Japan Law declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.