Skip to main content
hc
Submit
mcpSource-backed

Korean Law MCP Server

MCP server and CLI for searching Korean statutes, precedents, ordinances, treaties, interpretations, citation checks, amendment timelines, and legal scenario workflows through Korea's official law APIs.

by Chris · submitted by oktofeesh1·added 2026-06-05·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/mcp/korean-law-mcp-server
Source URLs
https://github.com/chrisryugj/korean-law-mcp/blob/main/README-EN.md, https://github.com/chrisryugj/korean-law-mcp
Brand
Korean Law MCP
Brand domain
github.com
Safety notes
Do not treat model output, tool summaries, scenario workflows, citation checks, or amendment comparisons as legal advice., Verify legal conclusions against official Korean legal sources and a qualified professional before using them for compliance, litigation, contracts, immigration, employment, taxation, or public guidance., Legal APIs can return stale, partial, unavailable, mistranslated, or context-dependent results; review dates, jurisdiction, document type, article numbers, and official text., Chain tools and scenario tools can combine many sources into persuasive narratives; require citation review before relying on generated explanations., Remote HTTP deployments must protect API keys, rate limits, and access to legal research workflows.
Privacy notes
`LAW_OC` and any API-key delivery method must be treated as secret and kept out of repositories, shared prompts, logs, and screenshots., Legal questions can reveal disputes, investigations, clients, employers, contracts, personal facts, regulated matters, or litigation strategy., Queries, citations, law names, case numbers, document text, and generated legal analysis may be visible to the MCP client and model provider., Avoid sending confidential client facts, privileged material, personal data, or non-public legal strategy through prompts or tool arguments.
Author
Chris
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

12 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

5 to clear

Platforms

4 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/5 ready
Account & credentials1Install & runtime1Network & hosting1Review & approval1General112 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 4 privacy notes across 3 risk areas. Review closely: credentials & tokens, third-party handling.

3 areas
  • SafetyGeneralDo not treat model output, tool summaries, scenario workflows, citation checks, or amendment comparisons as legal advice.
  • SafetyGeneralVerify legal conclusions against official Korean legal sources and a qualified professional before using them for compliance, litigation, contracts, immigration, employment, taxation, or public guidance.
  • SafetyGeneralLegal APIs can return stale, partial, unavailable, mistranslated, or context-dependent results; review dates, jurisdiction, document type, article numbers, and official text.
  • SafetyGeneralChain tools and scenario tools can combine many sources into persuasive narratives; require citation review before relying on generated explanations.
  • SafetyCredentials & tokensRemote HTTP deployments must protect API keys, rate limits, and access to legal research workflows.
  • PrivacyCredentials & tokens`LAW_OC` and any API-key delivery method must be treated as secret and kept out of repositories, shared prompts, logs, and screenshots.
  • PrivacyGeneralLegal questions can reveal disputes, investigations, clients, employers, contracts, personal facts, regulated matters, or litigation strategy.
  • PrivacyThird-party handlingQueries, citations, law names, case numbers, document text, and generated legal analysis may be visible to the MCP client and model provider.
  • PrivacyGeneralAvoid sending confidential client facts, privileged material, personal data, or non-public legal strategy through prompts or tool arguments.

Disclosure: Uses Korea Law Open API and related official or public legal information sources; usage may require API registration, rate-limit awareness, and jurisdiction-specific review.

Safety notes

  • Do not treat model output, tool summaries, scenario workflows, citation checks, or amendment comparisons as legal advice.
  • Verify legal conclusions against official Korean legal sources and a qualified professional before using them for compliance, litigation, contracts, immigration, employment, taxation, or public guidance.
  • Legal APIs can return stale, partial, unavailable, mistranslated, or context-dependent results; review dates, jurisdiction, document type, article numbers, and official text.
  • Chain tools and scenario tools can combine many sources into persuasive narratives; require citation review before relying on generated explanations.
  • Remote HTTP deployments must protect API keys, rate limits, and access to legal research workflows.

Privacy notes

  • `LAW_OC` and any API-key delivery method must be treated as secret and kept out of repositories, shared prompts, logs, and screenshots.
  • Legal questions can reveal disputes, investigations, clients, employers, contracts, personal facts, regulated matters, or litigation strategy.
  • Queries, citations, law names, case numbers, document text, and generated legal analysis may be visible to the MCP client and model provider.
  • Avoid sending confidential client facts, privileged material, personal data, or non-public legal strategy through prompts or tool arguments.

Prerequisites

  • Node.js 20.19 or newer, matching the upstream package metadata.
  • Korea Law Open API key stored as `LAW_OC`.
  • Korean legal research context where Korea's statutes, precedents, ordinances, treaties, or interpretations are relevant.
  • Korean-language legal terminology familiarity or access to qualified review.
  • Agreement that MCP output is research support, not legal advice.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
12 minutes
Difficulty
intermediate
Tool listing metadata
Disclosure
Uses Korea Law Open API and related official or public legal information sources; usage may require API registration, rate-limit awareness, and jurisdiction-specific review.
Full copyable content
{
  "mcpServers": {
    "korean-law": {
      "command": "korean-law-mcp",
      "env": {
        "LAW_OC": "YOUR_KOREA_LAW_OPEN_API_KEY"
      }
    }
  }
}

About this resource

Content

Korean Law MCP is an MCP server and CLI for Korean legal research. It wraps Korea Law Open API and related legal information sources so Claude can search statutes, retrieve law text, inspect precedents and decisions, compare amendment history, verify article citations, map article impact, and run scenario-style legal research workflows.

The package exposes korean-law-mcp for MCP clients and korean-law for CLI use. The upstream package metadata requires Node.js 20.19 or newer and the configuration examples use LAW_OC for the Korea Law Open API key.

Source Review

These sources were reviewed on 2026-06-05. Prefer the live repository, English README, package metadata, API documentation, architecture notes, server source, citation-verification source, scenario source, environment example, NPM registry metadata, and official Open API guide for current tool counts, installation requirements, API-key handling, supported domains, and rate limits.

Features

  • Search Korean statutes and retrieve official law text.
  • Search and retrieve precedents, Constitutional Court decisions, administrative appeals, tax tribunal decisions, customs interpretations, treaties, and related decision domains.
  • Verify legal article citations against official data to detect nonexistent laws, articles, or paragraph references.
  • Compare law text across dates and inspect amendment timelines.
  • Generate article impact maps across cited and citing legal materials.
  • Run scenario workflows for action basis, dispute preparation, procedures, ordinance comparison, amendment tracking, document review, and related research.
  • Search ordinances, administrative rules, annexes, forms, and legal-system trees.
  • Use the same package as an MCP server or CLI.

Installation

Install the package and configure the Korea Law Open API key:

npm install -g korean-law-mcp

Then add the MCP server to Claude or another MCP client:

{
  "mcpServers": {
    "korean-law": {
      "command": "korean-law-mcp",
      "env": {
        "LAW_OC": "YOUR_KOREA_LAW_OPEN_API_KEY",
        "LAW_API_PROTOCOL": "https"
      }
    }
  }
}

Test with low-risk lookups before using scenario workflows for real legal research, and verify the returned official source text manually.

Use Cases

  • Check whether a Korean legal citation exists before trusting a model-written answer.
  • Retrieve the current text of a statute article for research notes.
  • Compare how an article changed between two effective dates.
  • Gather statutes, precedents, interpretations, and ordinances for a Korean legal issue.
  • Explore which lower-level rules or ordinances may be affected by a law article.
  • Build an initial checklist for a Korean administrative or compliance procedure.

Safety and Privacy

Legal tooling needs a higher bar than ordinary search. Korean Law MCP can help retrieve and structure official legal information, but it cannot replace a qualified legal professional, official filing guidance, or jurisdiction-specific review. Treat all model-generated explanations as drafts and verify source text, dates, citations, and procedural details.

Do not send privileged facts, confidential client material, or sensitive dispute strategy through an MCP client unless that workflow has been approved. Keep LAW_OC secret, and avoid remote deployments that expose API keys or legal research endpoints without authentication and rate limits.

Duplicate Check

Existing legal entries cover other jurisdictions or providers, but no chrisryugj/korean-law-mcp, Korean Law MCP, or matching source URL was found in content/mcp.

#legal#korea#research#citations#government-data

Source citations

Add this badge to your README

Show that Korean Law MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/korean-law-mcp-server.svg)](https://heyclau.de/entry/mcp/korean-law-mcp-server)

How it compares

Korean Law MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field
Korean Law MCP Server

MCP server and CLI for searching Korean statutes, precedents, ordinances, treaties, interpretations, citation checks, amendment timelines, and legal scenario workflows through Korea's official law APIs.

Open dossier
NotebookLM MCP Server

MCP server that lets Claude work with Google NotebookLM notebooks through a real Chrome profile, source ingestion, citations, and audio overviews.

Open dossier
AgentQL logoAgentQL MCP Server

AgentQL MCP server for extracting structured JSON from public webpages using a URL and natural-language extraction prompt.

Open dossier
Agentset logoAgentset MCP Server

Official Agentset MCP server that lets Claude retrieve cited knowledge-base results from an Agentset namespace through the `knowledge-base-retrieve` tool, with optional tenant scoping and custom tool descriptions.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand——AgentQL logoAgentQLAgentset logoAgentset
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorChrisPleasePromptoAgentQLAgentset
Added2026-06-052026-06-052026-06-062026-06-06
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓Do not treat model output, tool summaries, scenario workflows, citation checks, or amendment comparisons as legal advice. Verify legal conclusions against official Korean legal sources and a qualified professional before using them for compliance, litigation, contracts, immigration, employment, taxation, or public guidance. Legal APIs can return stale, partial, unavailable, mistranslated, or context-dependent results; review dates, jurisdiction, document type, article numbers, and official text. Chain tools and scenario tools can combine many sources into persuasive narratives; require citation review before relying on generated explanations. Remote HTTP deployments must protect API keys, rate limits, and access to legal research workflows.✓NotebookLM MCP Server drives a real browser profile to interact with Google NotebookLM. setup_auth opens an interactive login flow and persists cookies in a local Chrome profile for later reuse. Tools can add sources, ask questions, generate and download audio overviews, manage notebook library metadata, close sessions, reset sessions, and clean up stored data. cleanup_data and re_auth can wipe stored browser state or local server data, so review tool arguments before allowing destructive maintenance actions. Bind Streamable HTTP mode only on trusted networks and keep stdio as the default for local desktop clients.✓AgentQL MCP exposes one tool, `extract-web-data`, that sends a target URL and natural-language extraction prompt to the AgentQL API. The tool is intended for public webpages; do not use it to bypass access controls, scrape private pages, evade paywalls, or extract data where automated collection is prohibited. Web extraction can still trigger target-site rate limits, legal restrictions, robots guidance, or terms-of-service concerns. The source implementation uses AgentQL's query-data endpoint with fast mode, no screenshot capture, no scroll-to-bottom behavior, and no local browser cookies. Treat extracted output as untrusted web data that may include errors, stale content, ads, tracking text, or prompt-injection attempts.✓The MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace. The `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance. Namespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent. API keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager. Custom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows.
Privacy notes✓`LAW_OC` and any API-key delivery method must be treated as secret and kept out of repositories, shared prompts, logs, and screenshots. Legal questions can reveal disputes, investigations, clients, employers, contracts, personal facts, regulated matters, or litigation strategy. Queries, citations, law names, case numbers, document text, and generated legal analysis may be visible to the MCP client and model provider. Avoid sending confidential client facts, privileged material, personal data, or non-public legal strategy through prompts or tool arguments.✓Google account cookies, NotebookLM notebook URLs, notebook metadata, source contents, questions, answers, citations, generated audio, browser session data, prompts, and tool outputs may be visible to the MCP client and model provider. The README notes there is no encrypted credential store; account separation is by Chrome profile directory. NotebookLM sources can contain private documents, internal research, customer material, legal drafts, meeting notes, and unreleased product plans. Review local profile and library storage before sharing machines, logs, screenshots, or exported artifacts.✓Target URLs, extraction prompts, API key-authenticated requests, and extracted structured data are sent to AgentQL's API. Extracted data can include personal data, copyrighted content, customer information, job postings, prices, social content, or other third-party material. AGENTQL_API_KEY should stay out of prompts, issues, logs, screenshots, and committed configuration files. Claude transcripts and downstream reports may retain extracted data, so avoid collecting information that is not approved for the model session.✓Retrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data. Retrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry. Tenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base. Do not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files.
Prerequisites
  • Node.js 20.19 or newer, matching the upstream package metadata.
  • Korea Law Open API key stored as `LAW_OC`.
  • Korean legal research context where Korea's statutes, precedents, ordinances, treaties, or interpretations are relevant.
  • Korean-language legal terminology familiarity or access to qualified review.
  • Node.js and npx available to the MCP client runtime.
  • Chrome or the bundled Patchright Chromium fallback available on the host.
  • Google account access for the NotebookLM notebooks you want to use.
  • One-time interactive authentication with setup_auth before headless reuse.
  • Node.js and npx available to the MCP client runtime.
  • AgentQL API key from the AgentQL developer portal.
  • Approved list of public webpages or domains Claude may query.
  • Review of target site terms, robots guidance, rate limits, and data-use rules before extraction.
  • Agentset account or self-hosted Agentset deployment with a populated namespace.
  • Agentset API key with access to the namespace Claude should query.
  • Node.js 18.17 or newer for running the `@agentset/mcp` package.
  • Namespace ID selected with `--ns` or `AGENTSET_NAMESPACE_ID`.
Install
npm install -g korean-law-mcp
npx notebooklm-mcp@latest
npx -y agentql-mcp
Run `npx @agentset/mcp --ns <namespace-id>` with `AGENTSET_API_KEY` set in the MCP server environment.
Config
{
  "mcpServers": {
    "korean-law": {
      "command": "korean-law-mcp",
      "env": {
        "LAW_OC": "YOUR_KOREA_LAW_OPEN_API_KEY",
        "LAW_API_PROTOCOL": "https"
      }
    }
  }
}
{
  "mcpServers": {
    "notebooklm": {
      "command": "npx",
      "args": ["notebooklm-mcp@latest"]
    }
  }
}
{
  "mcpServers": {
    "agentql": {
      "command": "npx",
      "args": ["-y", "agentql-mcp"],
      "env": {
        "AGENTQL_API_KEY": "<your-agentql-api-key>"
      }
    }
  }
}
{
  "mcpServers": {
    "agentset": {
      "command": "npx",
      "args": ["-y", "@agentset/mcp@latest", "--ns", "ns_xxx"],
      "env": {
        "AGENTSET_API_KEY": "agentset_xxx"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.