Skip to content

nu:legal Deutsches Recht MCP server

eu.nulegal/rechtnulegal.eustreamable-httpv1.0.4Scanned

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

11 tools: 11 only read.

Tools: 0 delete, 0 irreversible, 0 write, 11 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the nu:legal Deutsches Recht MCP server can do

The nu:legal Deutsches Recht MCP server is published by nulegal.eu, a domain the MCP Registry verified. It has 11 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool reads private data (get_lawyer); 1 tool brings in text other people can write (get_lawyer).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.0.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Only reads 11Show 11 read-only tools
  • get_lawyerOne lawyer's profile by `id` from search_lawyers: the official register entry with the date it was checked (chamber, admission, firm, office address, phone, fax, e-mail, website, b…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_lawyer" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "mail": it reads mail.
    • untrusted-inputThe description's first sentence says "mail": it reads inbound email, which other people can write.
    Description, as the server wrote it
    One lawyer's profile by `id` from search_lawyers: the official register entry with the date it was checked (chamber, admission, firm, office address, phone, fax, e-mail, website, beA id), Fachanwalt titles, contact data, languages, focus areas, opening hours and ratings per platform with the combined score. It holds what the public profile page (`profile_url`) shows, no more. Example: {"id": "8a0fa1b2c3d4e5f6"}

    Annotations the server declares

    • title: Get a lawyer's profile
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • getChangesWhat changed here, as JSON.No findings

    Why it is in this group

    • The name "getChanges" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Change Feed
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • getCoverageWhat the corpus holds and what it does not: laws, decisions, courts, the version archive and the Länder covered.No findings

    Why it is in this group

    • The name "getCoverage" says "get": a word for reading.
    Description, as the server wrote it
    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: {}

    Annotations the server declares

    • title: Corpus coverage
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • getNormThe text of one provision (§ or Article) as Markdown.No findings

    Why it is in this group

    • The name "getNorm" says "get": a word for reading.
    Description, as the server wrote it
    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; for EU acts, the EMRK and some Landesrecht from the day their held text applies). The answer says how many versions are held (`versions_held`) and how many decisions cite the provision (`cited_by`). A version date is not always its Inkrafttreten: `date_basis` says what it is. For most federal law it is the day the text was first seen here; for an EU act it is the day its text applies (`applies_from`). 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"}

    Annotations the server declares

    • title: Get statute text
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • listCasePassagesRead a decision: its paragraphs, each with the court's Randnummer (`rn`) and a link.No findings

    Why it is in this group

    • The name "listCasePassages" says "list": a word for reading.
    Description, as the server wrote it
    Read a decision: its paragraphs, each with the court's Randnummer (`rn`) and a link. `case` takes 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": "bgh/2017-03-29/viii-zr-45-16", "around": 15, "limit": 5}

    Annotations the server declares

    • title: List case passages
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • listCitedAuthoritiesWhat one decision cites: the provisions (with how often) and the decisions it relies on.No findings

    Why it is in this group

    • The name "listCitedAuthorities" says "list": a word for reading.
    Description, as the server wrote it
    What one decision cites: the provisions (with how often) and the decisions it relies on. Example: {"case": "bgh/2017-03-29/viii-zr-45-16"}

    Annotations the server declares

    • title: List cited authorities
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • listCitingDecisionsWho cites this: the decisions citing a provision (`law` + `ref`) or a decision (`case`).No findings

    Why it is in this group

    • The name "listCitingDecisions" says "list": a word for reading.
    Description, as the server wrote it
    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": "bgh/2017-03-29/viii-zr-45-16"}

    Annotations the server declares

    • title: List citing decisions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • listNormVersionsEvery stored version of one provision with its dates, newest first.No findings

    Why it is in this group

    • The name "listNormVersions" says "list": a word for reading.
    Description, as the server wrote it
    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"}

    Annotations the server declares

    • title: List statute versions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • resolveIdentifiersLook up German legal citations, up to 100 at once: a § or Article, an Aktenzeichen, an ECLI or a Fundstelle.No findings

    Why it is in this group

    • The name "resolveIdentifiers" says "resolve": a word for reading.
    Description, as the server wrote it
    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"]}

    Annotations the server declares

    • title: Resolve legal citations
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_lawyersFind lawyers in Germany in the official register of the Bundesrechtsanwaltskammer.No findings

    Why it is in this group

    • The name "search_lawyers" says "search": a word for reading.
    Description, as the server wrote it
    Find lawyers in Germany in the official register of the Bundesrechtsanwaltskammer. Give `city` (a German city or place; English names such as Munich or Cologne work; a 5-digit postcode is searched 10 km around, a smaller place 25 km), `name` (a lawyer or a firm), or both. Narrow with `area`, one of the 24 Fachanwalt areas in German or English ('Arbeitsrecht' or 'employment law', 'Strafrecht' or 'criminal law'), and `language` ('Türkisch' or 'Turkish'). Lawyers holding the Fachanwalt title for the area come first, then distance (postcode and place searches), then the combined rating. No paid placement; the order is no quality judgement. Next page: pass `next_offset` as `offset`. Each result has an `id` for get_lawyer and a `profile_url` to show the user. In-house lawyers (Syndikusrechtsanwälte) and lawyers who left the bar are not listed. Example: {"city": "Köln", "area": "Strafrecht", "language": "Arabic"}

    Annotations the server declares

    • title: Find lawyers in Germany
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:53 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 added, 4 changed.+2 added~4 changedView diff
  2. Tools9 changed.~9 changedView diff
  3. Tools4 changed.~4 changedView diff

Install

Pinned to version 1.0.4. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__recht__resolveIdentifiers",
      "mcp__recht__search",
      "mcp__recht__getNorm",
      "mcp__recht__listNormVersions",
      "mcp__recht__listCitingDecisions",
      "mcp__recht__listCitedAuthorities",
      "mcp__recht__listCasePassages",
      "mcp__recht__getChanges",
      "mcp__recht__getCoverage",
      "mcp__recht__search_lawyers",
      "mcp__recht__get_lawyer"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as recht. Review it before you use it.

Capability tags behind 1 rule
  • mcp__recht__get_lawyer private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/eu.nulegal/recht/verify?hash=4cfb8e5e2a0a10b2bea76b483c0eb884b2c962eb68403bf41ca6bc7864ca29d5" | jq -e '.changed == false'

Pinned hash 4cfb8e5e2a0a, from Nov 14, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/eu.nulegal/recht/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for eu.nulegal/recht
[![Anlyon Radar](https://radar.anlyon.com/badge/eu.nulegal/recht.svg)](https://radar.anlyon.com/servers/eu.nulegal/recht)

Source: MCP Registry · repository. Synced Nov 1, 2026, 12:17 UTC.

nu:legal Deutsches Recht MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the nu:legal Deutsches Recht MCP server safe?

No scan can promise that. What its definitions show: 11 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the nu:legal Deutsches Recht MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the nu:legal Deutsches Recht MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the nu:legal Deutsches Recht MCP server have?

11 tools: 11 read. resolveIdentifiers, search, getNorm, listNormVersions, listCitingDecisions, listCitedAuthorities, listCasePassages, getChanges and 3 more.

Does the nu:legal Deutsches Recht MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the nu:legal Deutsches Recht MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the nu:legal Deutsches Recht MCP server changed its tools?

Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.