Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Norwegian law for AI: current statutes and central regulations from Lovdata, with source citations
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://lexar-api.publifye.com/mcp在终端中运行这条命令
claude mcp add --transport http lexar https://lexar-api.publifye.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"lexar": {
"url": "https://lexar-api.publifye.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"lexar": {
"type": "http",
"url": "https://lexar-api.publifye.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://lexar-api.publifye.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 publifye.pro 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于上个月进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Zoo MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
An MCP server that provides access to the Zoo API for various CAD operations and tools.
按原文从作者的仓库复制。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.