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

klaws — Korean compliance risk scanner

OCI · GHCR.IO/ROSTRADAMUS/KLAWS:0.1.6 · SCANNED AUG 3

Scan code for Korean compliance risks — PIPA/개인정보보호법, Network Act, Credit Info. Not legal advice.

Available components

oci · ghcr.io/rostradamus/klaws:0.1.6 38
−6 this week 38 Trust /100
Trust breakdown (6 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 →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • CVE data not yet available for this package.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency-health data not yet available.Unverified
Provenance & Transparency45
Schema Quality & AI Usability72
  • 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 2 categories

Categories scored 0 because we could not verify them: 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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

oci · ghcr.io/rostradamus/klaws:0.1.6

# add to Claude Code
claude mcp add rostradamus-klaws -- docker run --rm -i ghcr.io/rostradamus/klaws:0.1.6
# add to Codex CLI
codex mcp add rostradamus-klaws -- docker run --rm -i ghcr.io/rostradamus/klaws:0.1.6
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rostradamus-klaws": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/rostradamus/klaws:0.1.6"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  rostradamus-klaws:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/rostradamus/klaws:0.1.6"]
// mcp.json
{
  "mcpServers": {
    "rostradamus-klaws": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/rostradamus/klaws:0.1.6"
      ]
    }
  }
}
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.

  • 31 Jul 26 −6
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 +33
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
  • 26 Jul 26 11

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Analysed oci/ghcr.io/rostradamus/klaws:0.1.6

Provenance none

Ecosystem: oci · Outcome: none

Reason: no_attestation

MCP tools — 4 exposed · ~514 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.

Tool Tokens
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.

NameTypeReqDescription
law_idstringyesBundled provision ID. Examples by law: PIPA-15, PIPA-29 (개인정보 보호법); NIA-22, NIA-50 (정보통신망법); CIA-19 (신용정보법); ECA-6 (전자상거래법).
liveboolean—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.

NameTypeReqDescription
file_patternstring—Glob pattern selecting which files to scan. Defaults to *.java. Examples: "*.java", "*.kt". Detectors target Java/Kotlin-style source.
pathstringyesAbsolute 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.

NameTypeReqDescription
pathstringyesAbsolute path to the file to scan (e.g. /Users/me/project/src/UserService.java).

No output schema declared.

No examples provided.