Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Nalegalu 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.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Semantic search over Polish law and case law, citing the exact in-force article.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nalegalu-mcp https://mcp.nalegalu.org/mcp
# 2 — ask your agent for something these tools do
# search_law, get_article, related_cases and 4 more
Nalegalu costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NAAll 1 server
nalegaluorg1 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 nalegalu-mcp https://mcp.nalegalu.org/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
7 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.
Search current Polish statutes and return article-level hits. Start here for a natural-language legal issue or a direct citation. Use the user's own Polish wording, e.g. "kupiłem wadliwy towar od firmy jakie mam prawa". Do not add address, domain, article, act_type, or status filters unless the user explicitly supplied that restriction. Results are primary-
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| limit | integer | no | — |
| address | no | — | |
| domain | no | — | |
| article | no | — | |
| act_type | no | — | |
| status | no | — | |
| include_non_in_force | boolean | no | — |
| case_law_boost | number | no | — |
| candidate_multiplier | integer | no | — |
| top_cases | integer | no | — |
| retrieval_mode | no | — |
Fetch the exact text of one article (or paragraph) of a Polish legal act. Use after search_law or another trusted source supplied the address and article key; never guess them. Deterministic lookup by act address (e.g. WDU19740240141) and article key (e.g. "133" or "Art. 133."). Optional paragraph_key (e.g. "1" or "§ 1.") narrows the result to a single para
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | — |
| article_key | string | yes | — |
| paragraph_key | no | — |
List SAOS cases related to one statutory provision. Use after identifying a relevant provision. A related-case link is not proof of a legal rule: inspect the judgment with get_case before asserting its holding. Deterministic lookup by act address (e.g. WDU19740240141) and article key. Returns case number, court, date, relevance score when available,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | — |
| article_key | string | yes | — |
| paragraph_key | no | — | |
| limit | integer | no | — |
Discover related-case candidates for a natural-language legal issue. This tool first searches statutes, then follows local provision-to-case links for several distinct provisions and deduplicates by SAOS ID. `rerank=false is the inexpensive deterministic discovery stage. With rerank=true, it fetches at most rerank_fetch_limit` public SAOS excerpts
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| provision_limit | integer | no | — |
| cases_per_provision | integer | no | — |
| candidate_limit | integer | no | — |
| context_max_chars | integer | no | — |
| rerank | boolean | no | — |
| rerank_fetch_limit | integer | no | — |
| rerank_result_limit | integer | no | — |
| case_text_max_chars | integer | no | — |
Fetch one SAOS court judgment (metadata + bounded text excerpt). Use only with a saos_id returned by related_cases, research_cases, or search_case_by_signature. Long judgments are paged: when has_more is true, call again with offset=next_offset. If the response has ok=false with a fallback hint, SAOS is unavailable or rate-limited — fetch the returned saos_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| saos_id | integer | yes | — |
| max_chars | integer | no | — |
| offset | integer | no | — |
Verify a cited case signature (sygnatura), e.g. "II CSK 448/14". Use before relying on a judgment cited by a user or another agent. Answers from a local index of all SAOS judgments first; only on a local miss does it query live SAOS. Read the verdict field: "confirmed" (matches listed with saos_id, court, date, type — different courts reuse signatures, so c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| signature | string | yes | — |
| limit | integer | no | — |
| court_type | no | — |
Check whether a supplied quote appears in a SAOS judgment. Use only after resolving the judgment to a saos_id. This validates wording, not whether the quote supports a legal conclusion. Pass the saos_id (from search_case_by_signature or related_cases) and the fragment as quoted. One call replaces paging through the full text: verdict is "exact" (verbatim af
| Parameter | Type | Required | Notes |
|---|---|---|---|
| saos_id | integer | yes | — |
| quote | string | yes | — |
| min_similarity | number | no | — |
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 Nalegalu 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: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. 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.0.
1.0.0
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 Nalegalu 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.