Korean Law MCP Server
Related Servers
Alternatives to Korean Law MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables natural language search and retrieval of Korean laws, precedents, administrative rules, and legal terms, with deep legal chain analysis and full-text access. Supports stdio and streamable-http transports for local and remote deployment.10MIT
- FlicenseAqualityAmaintenanceEnables AI systems to search, retrieve, and analyze Korean legal information from the National Law Information API (law.go.kr), including laws, administrative rules, English translations, and law-ordinance linkages.262-
- AlicenseNot gradedqualityCmaintenanceLets AI agents query South Korea's official statute database — searching laws and ordinances by title, pulling a single article (조문) with its own effective date, or tracing a statute's full revision history — using the caller's own Open API key. Text is returned in Korean only, with support for branch numbering like 제4조의2 and automatic retries against unstable upstream responses.270 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search and retrieve Korean laws, regulations, administrative rules, legal interpretations, and precedents via official APIs for legal review workflows.1MIT
- AlicenseAqualityCmaintenanceEnables MCP clients such as Claude to look up Korean statutes, individual articles, annexes, amendment history, precedents, and interpretive rulings from the Ministry of Government Legislation's national law information open API, and to run guided research scenarios, citation audits, contract risk scans, and citation tracing — all read-only. Supports both a hosted HTTP endpoint with per-user tokens and a local stdio installation using your own API key.12MIT
- FlicenseNot gradedqualityDmaintenanceEnables searching and retrieving Korean laws, precedents, and administrative rules through the National Law Information Center Open API, optimized for AI agents.-
TDQS
Scored across 3 tools
The three tools have clearly distinct roles: configuration check, legal source search, and document retrieval. Search vs. get is a standard and unambiguous split, and the descriptions reinforce how to choose between them.
All names use snake_case and are descriptive, but korean_law_setup does not follow the verb_noun pattern used by search_legal_documents and get_legal_document. The deviation is minor and still readable.
Three tools are well matched to a focused read-only Korean legal search server: setup, search, and fetch. Each tool has a clear purpose and there is no obvious filler.
The core search-and-retrieve workflow is covered, including pagination and article-level retrieval. Minor gaps exist, such as no explicit source-discovery or batch/document metadata tool, but agents can work around them via search.