Nalegalu MCP
REMOTE · MCP.NALEGALU.ORG · SCANNED SEP 20
Semantic search over Polish law and case law, citing the exact in-force article.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1623 tokens (~231/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Nalegalu MCP server?
Nalegalu MCP is a hosted endpoint at https://mcp.nalegalu.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.nalegalu.org
claude mcp add --transport http nalegaluorg-nalegalu 'https://mcp.nalegalu.org/mcp'
{
"mcpServers": {
"nalegaluorg-nalegalu": {
"url": "https://mcp.nalegalu.org/mcp"
}
}
} {
"servers": {
"nalegaluorg-nalegalu": {
"type": "http",
"url": "https://mcp.nalegalu.org/mcp"
}
}
} [mcp_servers.nalegaluorg-nalegalu] url = "https://mcp.nalegalu.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nalegaluorg-nalegalu": {
"type": "remote",
"url": "https://mcp.nalegalu.org/mcp",
"enabled": true
}
}
} openclaw mcp add nalegaluorg-nalegalu --url 'https://mcp.nalegalu.org/mcp' --transport streamable-http
mcp_servers:
nalegaluorg-nalegalu:
url: "https://mcp.nalegalu.org/mcp" {
"McpServers": {
"nalegaluorg-nalegalu": {
"Transport": "http",
"Url": "https://mcp.nalegalu.org/mcp"
}
}
} assistant mcp add nalegaluorg-nalegalu -t streamable-http -u 'https://mcp.nalegalu.org/mcp'
{
"mcpServers": {
"nalegaluorg-nalegalu": {
"type": "http",
"url": "https://mcp.nalegalu.org/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Sept 26 +2
- Stability: fail → pass ▲ security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: nalegalu-vector-search → nalegalu security
- Tool “related_cases” rewrote its description, which is the text the model reads security
- Schema quality: 206 → 231 ▼ functional
- Server version: 1.0.0 → 1.2.2 functional
- New tool “research_cases” functional
- 14 Aug 26 0
- Stability: 0.60 → fail ▼ security
- Tool “health” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_article” rewrote its description, which is the text the model reads security
- Tool “get_case” rewrote its description, which is the text the model reads security
- Tool “related_cases” rewrote its description, which is the text the model reads security
- Tool “search_case_by_signature” rewrote its description, which is the text the model reads security
- Tool “search_law” rewrote its description, which is the text the model reads security
- Tool “verify_quote” rewrote its description, which is the text the model reads security
- Schema quality: 139 → 206 ▼ functional
- Schema quality: good → excellent functional
- 12 Aug 26 0
- “search_law” added an optional parameter “retrieval_mode” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.nalegalu.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nalegalu.org | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 66f50f060de3769b13e0ebe238fa1b0b |
| SANs: nalegalu.org, *.nalegalu.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.nalegalu.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| nalegalu.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.nalegalu.org/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.nalegalu.org/mcp | HTTPS enforced | 301 | https://mcp.nalegalu.org/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_article ~137
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 paragraph.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| article_key | string | yes | – |
| paragraph_key | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_case ~132
Fetch one SAOS court judgment (metadata + bounded text excerpt). Use only with a saos_id returned by related_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_url yourself with your own web tools instead of retrying this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | – |
| offset | integer | – | – |
| saos_id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
related_cases ~279
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, and a SAOS link per case; scored cases sort first. Newer data also carries citation context per case: mentions (how many times the article appears in the judgment text), mention_match ("exact" = found with a matching act marker; "ambiguous" = bare mention, possibly another act's article — discount it), and context (snippet around the mention). mentions=0 or a missing context means the link comes from SAOS metadata but the text scan could not confirm it — treat relevance as unverified rather than assuming the case is on point. If count is zero, it means this local provision-to-case link dataset has no rows; it is not an exhaustive SAOS or case-law search.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| article_key | string | yes | – |
| limit | integer | – | – |
| paragraph_key | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
research_cases ~207
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 and reranks them only when the server has explicitly configured a Cohere reranker. It never decides a holding: call ``get_case`` for every judgment used in an answer.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_limit | integer | – | – |
| case_text_max_chars | integer | – | – |
| cases_per_provision | integer | – | – |
| context_max_chars | integer | – | – |
| provision_limit | integer | – | – |
| query | string | yes | – |
| rerank | boolean | – | – |
| rerank_fetch_limit | integer | – | – |
| rerank_result_limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_case_by_signature ~247
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 check the court), "not_found" (strong evidence the citation is fabricated or wrong), "outside_coverage" (administrative courts NSA/WSA are not in SAOS — verify in CBOSA instead), "unverified" (local miss and SAOS unreachable; do not treat as nonexistent). Optional court_type: COMMON, SUPREME, CONSTITUTIONAL_TRIBUNAL, NATIONAL_APPEAL_CHAMBER. has_text=false on a match means SAOS stores no text for it, so verify_quote cannot check quotes against that judgment.
| Name | Type | Req | Description |
|---|---|---|---|
| court_type | – | – | – |
| limit | integer | – | – |
| signature | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_law ~180
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-source material, not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| act_type | – | – | – |
| address | – | – | – |
| article | – | – | – |
| candidate_multiplier | integer | – | – |
| case_law_boost | number | – | – |
| domain | – | – | – |
| include_non_in_force | boolean | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| retrieval_mode | – | – | – |
| status | – | – | – |
| top_cases | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
verify_quote ~191
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 after normalizing whitespace, quote marks and dashes), "near_match" (best passage plus similarity score — compare it against the claim), or "not_found" (treat the quote as fabricated or misattributed). If ok=false with a fallback hint, fetch saos_url with your own web tools instead of retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| min_similarity | number | – | – |
| quote | string | yes | – |
| saos_id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Nalegalu MCP server?
Nalegalu MCP is listed in the public MCP registry as io.github.nalegaluorg/nalegalu. Semantic search over Polish law and case law, citing the exact in-force article. This page covers its hosted endpoint (https://mcp.nalegalu.org/mcp).
Is the Nalegalu MCP server safe to use?
Nalegalu MCP scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Nalegalu MCP server expose?
Nalegalu MCP exposes 7 tools: search_law, get_article, related_cases, research_cases, get_case, and 2 more. Their descriptions and schemas cost roughly 1,373 tokens of context every time the server is loaded.
Does the Nalegalu MCP server require authentication?
No. We connected to Nalegalu MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nalegalu MCP server still maintained?
Nalegalu MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.