Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
nu:legal Deutsches Recht is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
9
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
German federal and Land statutes plus court decisions for agents. Keyless, read-only, CC BY 4.0.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nu-legal-deutsches-recht-mcp https://recht.nulegal.eu/v1/mcp
# 2 — ask your agent for something these tools do
# resolveIdentifiers, search, getNorm and 6 more
nu:legal Deutsches Recht costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NUAll 1 server
nulegal1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http nu-legal-deutsches-recht-mcp https://recht.nulegal.eu/v1/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Ground a batch of German legal citations against the corpus. Call this BEFORE stating any citation you did not read here. Takes the citation in the form you already hold it — including the court name, the dispositive word and the date a model normally writes around a docket. KEEP THEM IN: the court and the date are used to disambiguate. An Aktenzeichen is unique per court, not nationwide, and 21,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| citations | array | yes | The citations, verbatim as you hold them. |
| include | array | no | Opt-in extra payload. 'text' returns a norm's FULL text instead of the 300-character stub — the stub is the same 300 characters whichever Absatz you cited, so never verify a quotation against it. 'lei |
One query over BOTH corpora: federal and Land statutes (lexical, with concept pinning) and court decisions (semantic — natural-language questions work well here and are the better shape for case law). Search both unless you have a reason not to. A term of art often does not appear in the statute that governs it: 'Verzugspauschale' matches no provision (§ 288 BGB says 'Pauschale in Höhe von 40 Eur
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | German query. Keywords, a citation, or a full question. |
| scope | string | no | 'all' (default) searches both. Narrow only when you know which corpus answers. |
| limit | integer | no | — |
| include_repealed | boolean | no | Include repealed (aufgehobene) provisions. Off by default; turn it on when researching an older state of the law. |
The text of one provision, by default as clean Markdown — about a tenth the size of the reader page for the same provision, with no navigation, no scripts and no boilerplate. law is the abbreviation as a citation writes it ('BGB', 'DSGVO', 'BDSG 2018', 'RVG'); ref is the bare number, with any letter suffix and no § or Art. ('622', '823', '3a', '83'). Aliases resolve, and CASE IS READ: 'LwG' i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| law | string | yes | Law abbreviation, or a law_key (slug in search results) when an abbreviation is ambiguous. |
| ref | string | yes | Provision number without § or Art. A sub-unit ('Abs. 1', 'lit. f') is dropped: the whole provision is returned. |
| as_of | string | no | Return the version stored for this date. |
| format | string | no | 'markdown' (default, compact, quotable) or 'json' for the structured payload. |
Every stored version of one provision, newest first, so you can find out which dates getNorm(as_of=…) can actually answer before you ask. Each entry carries first_observed (the day the text was first seen here — NOT the Inkrafttreten), valid_to, date_precision and the law-level amendment_note. at_archive_floor: true marks the version that was current when mirroring began: its date is
| Parameter | Type | Required | Notes |
|---|---|---|---|
| law | string | yes | — |
| ref | string | yes | — |
Incoming citation edges. Give EITHER law + ref (which decisions apply this statute provision) OR case (which decisions cite this decision) — exactly one of the two. Results are ranked by citation weight, then court tier, then recency. Read the ranking honestly: for a provision with many EU decisions the first ten can be almost all CJEU, and the German courts appear only further down. If `to
| Parameter | Type | Required | Notes |
|---|---|---|---|
| law | string | no | — |
| ref | string | no | — |
| case | string | no | A juris doknr, an ECLI, or this site's decision URL as search returns it. |
| limit | integer | no | — |
| offset | integer | no | Rows to skip, for reading past the first page. |
| sort | string | no | 'weight' (default) is citation weight, then court tier, then recency. 'recent' is newest decision first; where it cannot be computed the answer falls back to 'weight' and says so in sort_applied. |
Outgoing citation edges of one decision: the statute provisions it cites (with how often it cites each — that is the Normenkette, weighted) and the decisions it relies on. treatment is null on every edge and stays null. Classifying an edge as gefolgt / abgegrenzt / aufgegeben is unbuilt work, and a wrong 'aufgegeben' in a brief is worse than no label at all. Read the citing passage yourself wit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case | string | yes | A juris doknr, an ECLI, or this site's decision URL as search returns it. |
The full text of one decision, split into its paragraphs, each with a permalink you can cite. rn is the Randnummer the COURT printed, read out of the decision's own markup. It is never inferred from position: where a document prints no numbers, rn is null and stays null. anchor_basis is derived per decision — only 'native_numbering' means our anchor and the printed number provably coincide,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case | string | yes | A juris doknr, an ECLI, or this site's decision URL as search returns it. |
| offset | integer | no | — |
| limit | integer | no | — |
| around | integer/string | no | A Randnummer as the court printed it. Returns a window of limit passages centred on it. Not combinable with offset. |
Which provisions got a new text recently, newest first — the freshness feed, as JSON. Poll it with since set to the newest observed you have already processed. observed is the day the new text was FIRST SEEN here, which is not necessarily the day it came into force. Say so if you report a date. The window is the last 120 days; the law's own Änderungsverlauf goes further back.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | no | Only changes observed on or after this date. |
| limit | integer | no | — |
Corpus scope with its holes stated. Call this once when your answer depends on whether an absence is real. Returns totals (laws, provisions, versions, decisions, courts, citation edges), the per-source windows, the count of Aktenzeichen we can prove exist and do not hold, and limits: the version-archive floor, the federal scope of the citation graph, what a version date actually means, and why
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install nu:legal Deutsches Recht or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.2.
1.0.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish nu:legal Deutsches Recht can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.