Korean Law MCP
Korean law: statutes, precedents, ordinances, treaties and citation verification (법제처 API).
Norwegian law for AI: current statutes and central regulations from Lovdata, with source citations
选择你使用的 AI 应用,然后复制设置。
通过 5/5 项检查 · 你的提问会经过开发者的服务器(lexar-api.publifye.com)
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Lexarhttps://lexar-api.publifye.com/mcpAuthentication 保持 Claude 检测到的设置,然后点击 Add
+ConnectorsLexar
用 Lexar 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Lexar,或回答中出现 Lexar 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
仅企业版 ChatGPT 可连接
适用于网页版 ChatGPT Business、Enterprise 或 Edu,需由工作区管理员或所有者添加 · 使用 Free、Plus 或 Pro:你的 ChatGPT 方案暂时无法自行连接 MCP
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Lexarhttps://lexar-api.publifye.com/mcp开启新聊天,输入前先从插件列表中选择 Lexar
用 Lexar 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Lexar,或回答中出现 Lexar 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user lexar https://lexar-api.publifye.com/mcp应能看到 Lexar 在列表中并显示已连接
用 Lexar 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Lexar,或回答中出现 Lexar 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Lexar 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Lexar,或回答中出现 Lexar 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Lexar 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Lexar,或回答中出现 Lexar 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://lexar-api.publifye.com/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user lexar https://lexar-api.publifye.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"lexar": {
"url": "https://lexar-api.publifye.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"lexar": {
"type": "http",
"url": "https://lexar-api.publifye.com/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月12日
注册名称已通过域名 publifye.pro 验证(注册中心会核实域名所有权)
代码最后更新于32天前
使用 CC-BY-4.0
在 217 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于32天前,最新版本(1.0.0)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于支持远程 MCP 的应用,例如 ChatGPT Business 及以上方案。
同一分类中有:Korean Law MCP, Global law, Tw Legal Rag
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Korean law: statutes, precedents, ordinances, treaties and citation verification (법제처 API).
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
Taiwan law MCP server: 22M court judgments, statutes, agency rulings, with citation checks
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Lexar puts the current text of Norwegian law in front of an AI assistant: consolidated statutes and central regulations from Lovdata, with the citation and the source URL attached to every passage it returns. It is a research surface, not legal advice — it hands you the wording and tells you what it does not cover.
| Endpoint | https://lexar-api.publifye.com/mcp |
| Transport | Streamable HTTP |
| Auth | OAuth 2.1 + PKCE (S256), DCR open |
| Registry | pro.publifye/lexar (server.json) |
| Product site | https://lexar.publifye.com |
| What it solves | https://publifye.com/lexar |
| Research tools | 7 (full schemas) |
{ "mcpServers": { "lexar": { "type": "http", "url": "https://lexar-api.publifye.com/mcp" } } }
The OAuth flow runs in the browser on first use. See [../../docs/connect.md](../../docs/connect.md).
Measured on the live service, 2026-09-16, via status:
| Documents | 6,859 |
| Current consolidated law | 5,871 — 759 statutes, 5,112 central regulations |
| Announcements (Norsk Lovtidend avd. I, 2026) | 988 |
| Indexed blocks | 457,743 |
| Distinct word forms | 301,140 |
| Cross-references extracted | 290,805 |
| Document aliases | 5,054 keys, 1,566 conventional forms |
Source acquired 2026-09-12 from the Lovdata publicData API. Source snapshot 82cff3294c90969e6fc78393d5d24c842e5555ac323593904b104afe1c5e4f11.
Seven tools, and the number is fixed by specification rather than by what happened to get built — richer capability goes into typed inputs and results, not into more tools.
| Area | The question it answers | Tools |
|---|---|---|
| [Finding the law](tools/finding.md) | Which law or regulation is this, and where is the wording that matters? | 2 |
| [Reading it](tools/reading.md) | What does the provision actually say, and how is the document put together? | 2 |
| [Context and coverage](tools/context.md) | What does it connect to, what do its terms mean, and how much can you rely on? | 3 |
Machine-readable: [tools.json](tools.json) carries all 7 with full JSON Schema, plus the excluded buckets listed by name so the count is auditable. One more tool is callable: operator_guide, a method guide to read once first — which tool for which question, and what Lexar does not hold. It is help, not research, and is listed in tools.json under help_and_health.
Preparatory works. Lexar holds 29,627 *forarbeider* documents under NLOD 2.0: 23,965 from Stortinget (ST/) and 5,662 from Nasjonalbiblioteket (NB/) — innstillinger, Ot.prp., lovvedtak, referater and more. Reading a provision shows pointers to the preparatory works that discuss it; connections with kind=forarbeider lists them, and read and outline open a document by its id. A pointer is offered by default only where its kind of link was hand-checked at 85% precision or better; the rest are held and reachable with include_low_confidence=true. Prop. and Ot.prp. after 2005 are mostly held as designations only, not as text.
`resolve` never picks silently. A law name or an ambiguous citation returns candidates, because guessing which statute someone meant is the one failure a legal research tool must not have.
[PROVENANCE.md](PROVENANCE.md) records the source, the licence, the measured corpus and the gaps. The short version, because it decides whether Lexar can answer your question at all:
Not in the corpus: court decisions, local regulations, English translations, historical consolidated versions, and most Prop. and Ot.prp. after 2005 (held as designations, not text). So *no hit does not mean no law* — it may mean the answer lives somewhere Lexar does not hold.
And a document being present is not proof that every provision in it is in force. Publication, consolidation and legal commencement are three separate facts, and Lexar distinguishes them rather than flattening them into one.
Lexar provides source text and navigation. It does not generate legal advice.
Data from Lovdata under [NLOD 2.0](https://data.norge.no/nlod/no/2.0), which permits commercial reuse and redistribution under its own conditions.
Inneholder data fra Lovdata under Norsk lisens for offentlige data (NLOD) 2.0.
Lexar sells hosted access, indexing, availability and operational service — not the corpus. The underlying open legal data stays open, and nothing here restricts a right NLOD already grants you. Lexar's own formatting, indexes and derived classifications are identified separately from the source text.
Current plans and prices are on [https://lexar.publifye.com/store](https://lexar.publifye.com/store), which is the only place they are authoritative. They are deliberately not duplicated here.