nu:legal Deutsches Recht

eu.nulegalPublished by nulegal.euOfficial publisherv1.0.4Updated Nov 1, 2026

German federal and Land statutes plus court decisions for agents. Keyless, read-only.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Keyless, read-only MCP server for German federal, Land and EU law: look up citations, read statutes and decisions, and follow the citation graph.

What you can do
  • Resolve citations (paragraphs, Articles, dockets, ECLIs, case reports) in batches and check them before quoting
  • Search statutes lexically and case law semantically by topic or full question
  • Read provisions as Markdown, optionally as of a past date, and list their stored versions
  • Read decisions as numbered passages and see what each decision cites
  • See which decisions cite a provision or a decision, ranked by weight or recency
  • Check recent changes and what the corpus covers, including gaps
When to use it
Useful when an assistant has to ground or verify German legal citations, quote statute text, read a decision, or trace who cites what. Also suited to checking whether an answer is complete before saying something does not exist.
Requirements
Remote Streamable HTTP endpoint at recht.nulegal.eu; no key or signup. Optionally run locally with Python 3.12+ and uv, which calls the public REST API; the local HTTP mode binds to loopback by default.
Before you install
Read-only and free, but the texts are non-official reading copies; the official gazette version is binding. Version dates are first-observed dates, not entry-into-force dates, and the archive starts 2019-06-10. Hessen provisions are not linked in the citation graph, so a zero there means not indexed. Attribution is required under CC BY 4.0, and use for AI training is reserved.

Installation

In SourceWeft

  1. Open nu:legal Deutsches Recht in the dashboard and add it to a workspace.
  2. 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/eu.nulegal%2Frecht/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.

{
  "mcpServers": {
    "nu-legal-deutsches-recht": {
      "type": "http",
      "url": "https://recht.nulegal.eu/v1/mcp"
    }
  }
}

README

recht-mcp

[smithery badge]

An MCP server for German law: federal statutes and regulations, the Landesrecht of Bayern, Brandenburg, Nordrhein-Westfalen and Sachsen, and court decisions — for AI agents that need to ground a citation, read a provision, or follow the citation graph, and need to know when an answer is not complete.

On 23 October 2026 the corpus held 12,016 statutes and regulations (254,598 provisions, 312,122 stored versions) and 640,401 court decisions from 946 courts, with 7,797,118 citation links from decisions to provisions and to other decisions. getCoverage returns the current figures.

This repository is the tool layer of the hosted server at https://recht.nulegal.eu/v1/mcp. The hosted endpoint runs this code, vendored at a pinned commit, over a private backend that reads the corpus directly; recht-mcp runs the same code locally over the public REST API. The corpus and the database stay on the service side — see docs/DESIGN.md for exactly where the line runs.

The nine tools

ToolWhat it does
resolveIdentifiersGrounds up to 100 citations at once — § 823 Abs. 1 BGB, BVerwG, Urteil vom 24.10.2023 - 2 C 9.22, ECLIs, BVerfGE 65, 1. Keeps the court and the date as disambiguators, flags a wrong date or a different court, and never returns a near match.
searchOne query over statutes (lexical) and case law (semantic), with a per-jurisdiction roll-up for cross-Land comparison.
getNormThe text of one provision as Markdown (or JSON), optionally as of a date, with its gazette citation (fundstelle).
listNormVersionsEvery stored version of a provision, with the archive floor marked.
listCitingDecisionsDecisions citing a provision or a decision, by citation weight or newest first, with the citing court's own Randnummer.
listCitedAuthoritiesWhat one decision cites: provisions (the weighted Normenkette) and decisions.
listCasePassagesA decision as numbered passages; page through it or jump to a Randnummer.
getChangesProvisions whose text changed recently — the freshness feed as JSON.
getCoverageWhat the corpus holds, and the limits every answer should be read against.

Every tool is read-only. Each answer says what it is and what it is not: version dates are first-observed dates, not Inkrafttreten; the norm-version archive has a floor that every norm answer states; a zero from the citation graph on a Land provision is labelled as "not indexed", not "never cited"; and three kinds of miss — not_in_corpus, outside_coverage, known_missing — are never collapsed into one. The full contract of each tool is in its description (tools/list).

Use the hosted server (recommended)

No key, no signup. Point any MCP client that speaks Streamable HTTP at:

https://recht.nulegal.eu/v1/mcp

Claude Code:

claude mcp add --transport http nulegal-recht https://recht.nulegal.eu/v1/mcp

A client configured with JSON:

json
{  "mcpServers": {    "nulegal-recht": { "type": "http", "url": "https://recht.nulegal.eu/v1/mcp" }  }}

Developer documentation for the service and its REST API: https://recht.nulegal.eu/developers.

Run it locally

Requires Python 3.12+ and uv. The package has no third-party runtime dependencies.

git clone https://github.com/nulegal-startup/recht-mcpcd recht-mcpuv run recht-mcp            # stdiouv run recht-mcp --http     # Streamable HTTP on http://127.0.0.1:8765/mcp

Or without a checkout:

uvx --from git+https://github.com/nulegal-startup/recht-mcp recht-mcp

A client that launches stdio servers:

json
{  "mcpServers": {    "nulegal-recht": {      "command": "uvx",      "args": ["--from", "git+https://github.com/nulegal-startup/recht-mcp", "recht-mcp"]    }  }}

Options: --http, --host (default 127.0.0.1), --port (default 8765), --path (default /mcp), --base-url (or RECHT_MCP_BASE_URL; default https://recht.nulegal.eu), --timeout, --log-level. The local HTTP server binds to loopback and refuses browser requests from non-loopback origins.

The local server reads the same data the hosted one does, through the public REST API, and gives the same answers with two documented exceptions (a simplified citation grammar, and no other_laws hint on a provision miss) — see docs/DESIGN.md.

Development

uv syncuv run pytest -q                                   # unit tests, offlineRECHT_MCP_LIVE=1 uv run pytest -q tests/test_live.py   # against recht.nulegal.eu

The live tests call every tool through the local server and compare several answers with the hosted endpoint's.

Data

The legal corpus served by the hosted endpoint — its structure and selection, the links between provisions and decisions, the version history — is licensed separately from this code, under CC BY 4.0. Attribution is required: „Quelle: nu:legal – recht.nulegal.eu“. The terms, including what is reserved, are at https://recht.nulegal.eu/lizenz and https://recht.nulegal.eu/nutzungsbedingungen.

The texts are non-official reading copies. The binding text of a statute is the one in its official gazette; each norm answer names it (fundstelle, authoritative_source).

Contributing and security

Issues are welcome; outside pull requests are not accepted yet — see CONTRIBUTING.md. Report vulnerabilities privately as described in SECURITY.md.

License

The code in this repository is licensed under the GNU Affero General Public License, version 3 only (AGPL-3.0-only) — see LICENSE.

The legal corpus served by the hosted endpoint is licensed separately, under CC BY 4.0 with attribution required (see Data).

The nu:legal name and logo are not licensed.

Source: README.md at commit 8fa93eb

Tools

9

resolveIdentifiers

Resolve legal citations

Look up German legal citations, up to 100 at once: a § or Article, an Aktenzeichen, an ECLI or a Fundstelle. Use it to find a decision by its docket and to check a citation before you state it. Pass each citation as you hold it, with court and date: they pick the right decision where a docket repeats. It never guesses. A miss is `not_in_corpus`; `attested` / `known_missing` means the decision exists but its text is not held; `date_mismatch` / `court_mismatch` mean your citation is wrong there. A found decision carries `cited_by`: how many decisions cite it, and the top citers with a link to the Randnummer where they do. Example: {"citations": ["BGH, Urteil vom 29.03.2017 - VIII ZR 45/16", "§ 573 Abs. 2 BGB"]}

Parametersincludecitationsrequired

getNorm

Get statute text

The text of one provision (§ or Article) as Markdown. `law` is the abbreviation ('BGB', 'StGB', 'DSGVO'; Hessen: 'HBO'), `ref` the number ('573', '3a'). For the text on a past date add `as_of` (YYYY-MM-DD; versions are held from 2019-06-10). The answer says how many versions are held (`versions_held`) and how many decisions cite the provision (`cited_by`). A version date is the day the text was first seen here, not its Inkrafttreten. With `compare_to` (YYYY-MM-DD) the answer adds `diff`, the word diff to the version stored for that date. DATES: each version carries `date_basis`, `in_force_from` (a date the source states) and `observed_from` (first seen here), each with its `*_basis`; the one we do not hold is null. Example: {"law": "BGB", "ref": "573"}

Parameterslawrequiredrefrequiredas_offormatcompare_to

listNormVersions

List statute versions

Every stored version of one provision with its dates, newest first. Use it to see when a provision changed, then read a version with getNorm `as_of`. `at_archive_floor` marks a text that was already in force when the archive began. To compare two versions, call `getNorm(compare_to=…)`: the answer's `diff` is the word diff, and each side says what its date is (`date_basis`: `in_force`, `eurlex_consolidation`, `source_stated`, `observed` or `archive_floor`), so a floor date stays visible. DATES: each version carries `date_basis`, `in_force_from` (a date the source states) and `observed_from` (first seen here), each with its `*_basis`; the one we do not hold is null. Example: {"law": "BGB", "ref": "288"}

Parameterslawrequiredrefrequired

listCitingDecisions

List citing decisions

Who cites this: the decisions citing a provision (`law` + `ref`) or a decision (`case`). Ranked by weight; `sort: "recent"` gives the newest first. Each citer links to the Randnummer where it cites. The graph is built over every decision held, federal, Land and EU courts alike, and links federal, EU and Land provisions; it does not link Hessen provisions, which answer `total: 0` with `coverage.complete_for_this_norm: false`: then fall back to `search` on the provision's wording. `coverage` carries the counts for the provision's jurisdiction. Example: {"law": "BGB", "ref": "573", "sort": "recent", "limit": 5} or {"case": "KORE313182017"}

Parameterslawrefcasesortlimitoffset

listCitedAuthorities

List cited authorities

What one decision cites: the provisions (with how often) and the decisions it relies on. Example: {"case": "KORE313182017"}

Parameterscaserequiredlangoffset

listCasePassages

List case passages

Read a decision: its paragraphs, each with the court's Randnummer (`rn`) and a link. `case` takes a doknr, an ECLI, our decision URL or an Aktenzeichen. Jump to a Randnummer with `around`, page with `offset` and `limit`. The first page also says how often the decision is cited and by whom. The answer carries `card`: typed `headnotes` (Leitsatz apart from Orientierungssatz), the `tenor` where the source marks it, `cited_norms`, `fundstellen`, `cite_as`; never generated text. Example: {"case": "KORE313182017", "around": 15, "limit": 5}

Parameterscaserequiredlanglimitaroundoffsetinclude

getChanges

Change Feed

What changed here, as JSON. Two ways to read it. The cursor feed (send `kinds`, or `cursor`): everything that changed, oldest first, readable to the end without gaps: decisions added or changed, provisions with a new text (new Fassung, new provision, new law), and new citation links (decision X now cites Y, or decision Y gained a citer). Start with `kinds` (and `since`, default 7 days ago), then pass `next_cursor` back unchanged, with the same filters, until `has_more` is false; keep the cursor and poll with it later. Without those arguments: the provisions that got a new text recently, newest first. Poll it with `since` set to the newest `observed` you have processed. `observed` / `observed_at` is when the change reached this service, not when a court decided or a law came into force. Say so if you report a date. The window is the last 120 days; a provision's own history is listNormVersions.

Parameterslawlandcourtkindslimitsincecursor

getCoverage

Corpus coverage

What the corpus holds and what it does not: laws, decisions, courts, the version archive and the Länder covered. Call it before you report that something does not exist. The answer's `coverage` block is /v1/coverage: statutes per Land (`statutes`: full_text, partial or none), decisions per court level, the citation graph and what every version date is, all from one daily table. Example: {}

Parameterscourtinclude

Version history

5
  1. v1.0.4LatestNov 1, 2026
  2. v1.0.3Oct 23, 2026
  3. v1.0.2Sep 30, 2026
  4. v1.0.1Sep 24, 2026
  5. v1.0.0Sep 23, 2026

Score

100% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Nulegal integrations