klaws — Korean compliance risk scanner
OCI · GHCR.IO/ROSTRADAMUS/KLAWS:0.1.6
Scan code for Korean compliance risks — PIPA/개인정보보호법, Network Act, Credit Info. Not legal advice.
Available components
Last scanned (3 hours ago)
Scores higher than 93% of OCI servers
Category Security
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 119 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 699 tokens (~174/item across 4 items; 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 19 Oct 26 0
- Stability: 0.97 → pass security
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 −3
- Stability: pass → 0.80 functional
- 12 Oct 26 +1
- Stability: 0.93 → pass security
- 10 Oct 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 97 to 93.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 oci/ghcr.io/rostradamus/klaws:0.1.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
get_law_reference ~182
Look up a bundled Korean law provision by ID and return its Korean and English names, a plain-language summary, the source URL on law.go.kr, a risk level, and (when available) the full Korean article text. Typically used to expand a related_laws ID returned by a scan. This is reference material, not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| law_id | string | yes | Bundled provision ID. Examples by law: PIPA-15, PIPA-29 (개인정보 보호법); NIA-22, NIA-50 (정보통신망법); CIA-19 (신용정보법); ECA-6 (전자상거래법). |
| live | boolean | – | If true, fetch the latest full text from law.go.kr (requires network access). If false (default), use the text bundled in the binary. |
No output schema declared.
No examples provided.
list_detectors ~63
List every available compliance risk detector with its id, name, description (the code pattern it looks for), and the related_laws it maps to. Use this to explain what klaws checks for, or to see which risks to expect before scanning. Takes no arguments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_directory ~178
Scan all matching files in a directory tree for possible Korean compliance risks across PIPA, the Network Act, the Credit Information Act, and the E-Commerce Act. Returns a JSON report where each finding has a detector_id, risk_level (HIGH or MEDIUM), file_path, line_number, snippet, a hedged message, and related_laws (provision IDs you can pass to get_law_reference). Findings are possible risks for review, not legal conclusions. Use this for a whole project or folder; use scan_file for a single file.
| Name | Type | Req | Description |
|---|---|---|---|
| file_pattern | string | – | Glob pattern selecting which files to scan. Defaults to *.java. Examples: "*.java", "*.kt". Detectors target Java/Kotlin-style source. |
| path | string | yes | Absolute path to the directory to scan (e.g. /Users/me/project/src). |
No output schema declared.
No examples provided.
scan_file ~91
Scan a single source file for possible Korean compliance risks and return the same JSON report shape as scan_directory. Use this to check one file (for example, the file currently being edited); use scan_directory to review a whole project. Findings are possible risks for review, not legal conclusions.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to the file to scan (e.g. /Users/me/project/src/UserService.java). |
No output schema declared.
No examples provided.
How do I install the klaws — Korean compliance risk scanner MCP server?
klaws — Korean compliance risk scanner runs locally as a container image, launched with docker run --rm -i ghcr.io/rostradamus/klaws:0.1.6. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/rostradamus/klaws:0.1.6
claude mcp add rostradamus-klaws -- docker run --rm -i ghcr.io/rostradamus/klaws:0.1.6
What is the klaws — Korean compliance risk scanner MCP server?
klaws — Korean compliance risk scanner is an MCP server listed in the public MCP registry as io.github.rostradamus/klaws. Scan code for Korean compliance risks, PIPA/개인정보보호법, Network Act, Credit Info. Not legal advice. This page covers its container image (ghcr.io/rostradamus/klaws:0.1.6).
Is the klaws — Korean compliance risk scanner MCP server safe to use?
klaws — Korean compliance risk scanner scores 55 out of 100 on VerifyMCP. 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 klaws — Korean compliance risk scanner MCP server expose?
klaws — Korean compliance risk scanner exposes 4 tools: get_law_reference, list_detectors, scan_directory, scan_file. Their descriptions and schemas cost roughly 514 tokens of context every time the server is loaded.
Is the klaws — Korean compliance risk scanner MCP server still maintained?
klaws — Korean compliance risk scanner 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 klaws — Korean compliance risk scanner MCP server under?
klaws — Korean compliance risk scanner declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.