Kr Law
NPM · @PIPEWORX/MCP-KR-LAW · 2 COMPONENTS
Korea Law MCP — South Korean national statutes via the Ministry of Government Legislation's (법제처)…
Available components
Last scanned (15 hours ago)
Scores higher than 69% of npm servers
Category Education and Research
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-kr-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 Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 817 tokens (~272/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 Management20
- Stability observed for 6 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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.10 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 78
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-kr-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-kr-law |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-kr-law/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649591589 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:183a31010f3f6087121e3841e957068ea9e19d834370abcac26d74a78f36a833c5fcc6917b5d47ffe1d8ae3dce9248d6d4dcc29ae09fde1a28e2e5841 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
kr_law_article ~308
Fetch ONE article (조문) of a South Korean statute by mst (from kr_law_search) and article_no (e.g. "5" or "4-2" for 제4조의2). Never returns the whole law body. Omit article_no to get a paginated table of contents (article numbers + titles) instead. Returns the article's own text, paragraphs (항) and items (호), its own effective date (which can differ from the law's), and law-level metadata (promulgation date, effective date, ministry) kept as separate fields. BYOK: requires your own OC; pass it as _apiKey.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Your own OC (Open API user id) from https://open.law.go.kr/LSO/main.do. The Ministry's public demo id "test" works here for smoke-testing. |
| article_no | string | – | Article number, e.g. "5", or "4-2" for a branch article (제4조의2). Omit for a table of contents. |
| display | number | – | Table-of-contents mode only: entries per page, 1-200 (default 50). |
| mst | string | yes | Law version id (법령일련번호) from kr_law_search's "mst" field. |
| page | number | – | Table-of-contents mode only: 1-based page number (default 1). |
No output schema declared.
No examples provided.
kr_law_history ~179
Revision history for a South Korean statute: every promulgation with its own date, promulgation number, and entry-into-force date, each as a separate historical mst you can pass to kr_law_article. Requires the caller's OC to have the 법령연혁 (law history) service separately enabled under My Applications at open.law.go.kr — if it is not, this throws a specific, actionable upstream error rather than a generic failure. BYOK: pass your OC as _apiKey.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Your own OC (Open API user id) from https://open.law.go.kr/LSO/main.do, with 법령연혁 enabled under My Applications. |
| mst | string | yes | Law version id (법령일련번호) from kr_law_search's "mst" field. |
No output schema declared.
No examples provided.
kr_law_search ~277
Search South Korean national statutes by title keyword (국가법령정보, Ministry of Government Legislation). Returns each matching law's id, mst (version id — pass to kr_law_article/kr_law_history), ministry, promulgation/effective dates, and whether it is the current ("현행") or a superseded ("연혁") version. BYOK: requires your own OC from open.law.go.kr (Korean real-name verification to register); pass it as _apiKey.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Your own OC (Open API user id) from https://open.law.go.kr/LSO/main.do. The Ministry's public demo id "test" works here for smoke-testing. |
| display | number | – | Results per page, 1-100 (default 20). |
| page | number | – | 1-based page number (default 1). |
| query | string | yes | Title keyword, Korean or romanized, e.g. "도로교통법" (Road Traffic Act) or "개인정보". |
| status | string | – | Narrow to currently-in-force laws only ("current") or search as-is ("all", default). "historical" still returns the general list; filter client-side on the returned "status" field for superseded vers… |
No output schema declared.
No examples provided.
How do I install the Kr Law MCP server?
Kr Law runs locally as an npm package, launched with npx -y @pipeworx/mcp-kr-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-kr-law
claude mcp add pipeworx-io-kr-law -- npx -y @pipeworx/mcp-kr-law
What is the Kr Law MCP server?
Kr Law is an MCP server listed in the public MCP registry as io.github.pipeworx-io/kr-law. Korea Law MCP, South Korean national statutes via the Ministry of Government Legislation's (법제처)… This page covers its npm package (@pipeworx/mcp-kr-law).
Is the Kr Law MCP server safe to use?
Kr Law scores 81 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 Kr Law MCP server expose?
Kr Law exposes 3 tools: kr_law_search, kr_law_article, kr_law_history. Their descriptions and schemas cost roughly 764 tokens of context every time the server is loaded.
Is the Kr Law MCP server still maintained?
Kr 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 Kr Law MCP server under?
Kr 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.
What did VerifyMCP test on the Kr Law MCP server?
VerifyMCP ran 16 checks on Kr Law, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.