Lexar

pro.publifyePublished by publifye.prov1.0.0Updated Oct 24, 2026

Norwegian law for AI: current statutes and central regulations from Lovdata, with source citations

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Lexar gives an AI assistant access to current Norwegian statutes and central regulations from Lovdata, with citations and source links for every passage.

What you can do
Find the law: resolve law names and ambiguous citations to candidate documents rather than guessing, and locate the relevant wording in statutes and regulations. Read it: retrieve the text of a provision and see how a document is structured via outline. Explore context and coverage: list cross-references and preparatory works (forarbeider) linked to a provision, look up term meanings, and check corpus status and what the service does not hold. A help tool, operator_guide, explains which tool suits which question.
When to use it
Useful when an assistant needs to quote or navigate current Norwegian legislation and regulations, or trace the preparatory works behind a provision. It suits legal research drafting where citations to Lovdata sources matter, not situations needing court decisions, local rules or English translations.
Requirements
A remote MCP endpoint over Streamable HTTP, with OAuth 2.1 plus PKCE sign-in completed in the browser on first use. No local runtime, packages, environment variables or headers are declared. Network access to the service is required.
Before you install
The README states it is a research surface, not legal advice, and that it does not generate legal advice. Coverage gaps include court decisions, local regulations, English translations, historical consolidated versions and most preparatory works after 2005; a missing hit does not mean no law exists. Presence of a document does not prove every provision is in force. Plans and prices are set on the vendor's store page, so paid access may apply.

Installation

In SourceWeft

  1. Open Lexar in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/pro.publifye%2Flexar/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lexar": {
      "type": "http",
      "url": "https://lexar-api.publifye.com/mcp"
    }
  }
}

README

Lexar — Norwegian law as an MCP server for Claude, Cursor and any MCP client

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.

Endpointhttps://lexar-api.publifye.com/mcp
TransportStreamable HTTP
AuthOAuth 2.1 + PKCE (S256), DCR open
Registrypro.publifye/lexar (server.json)
Product sitehttps://lexar.publifye.com
What it solveshttps://publifye.com/lexar
Research tools7 (full schemas)

Connect

jsonc
{ "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.

The corpus

Measured on the live service, 2026-09-16, via status:

Documents6,859
Current consolidated law5,871 — 759 statutes, 5,112 central regulations
Announcements (Norsk Lovtidend avd. I, 2026)988
Indexed blocks457,743
Distinct word forms301,140
Cross-references extracted290,805
Document aliases5,054 keys, 1,566 conventional forms

Source acquired 2026-09-12 from the Lovdata publicData API. Source snapshot 82cff3294c90969e6fc78393d5d24c842e5555ac323593904b104afe1c5e4f11.

What the tools do

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.

AreaThe question it answersTools
Finding the lawWhich law or regulation is this, and where is the wording that matters?2
Reading itWhat does the provision actually say, and how is the document put together?2
Context and coverageWhat does it connect to, what do its terms mean, and how much can you rely on?3

Machine-readable: 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.

What it does not cover — read this before you rely on it

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.

Licence and attribution

Data from Lovdata under NLOD 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.

Plans

Current plans and prices are on https://lexar.publifye.com/store, which is the only place they are authoritative. They are deliberately not duplicated here.

Source: services/lexar/README.md at commit 302977c

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 23, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts