mcpbeat Sign in

Nalegalu MCP Server

by nalegaluorg Your server? Claim it
answering

Nalegalu MCP is answering right now. Last checked 12 min ago. It exposes 7 tools. Last commit 13 Jul 2026.

Semantic search over Polish law and case law, citing the exact in-force article.

Uptime history 51 days of history · worst day 94%
51 days agonow
93.4%
Uptime 24h
85 of 91 checks
7
Tools
read from the server
213 ms
Response time
average over 24h
9
Stars
last commit 13 Jul 2026

What changed 16

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 August 2026. No other catalogue keeps this.

24 Aug a tool changed version3 times that day
24 Aug a tool appeared research_cases
24 Aug a tool description was rewritten related_cases
14 Aug a tool disappeared health
13 Aug 7 tool descriptions were rewritten get_article, get_case, health and 4 more
12 Aug a tool changed the parameters it asks for search_law
11 Aug 2 tool descriptions were rewritten health, related_cases
and 2 more, back to 11 August 2026

Nalegalu MCP does not always answer

Over the last week it answered 98.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add nalegalu --transport http https://mcp.nalegalu.org/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "nalegalu": {
      "url": "https://mcp.nalegalu.org/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.nalegalu]
url = "https://mcp.nalegalu.org/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "nalegalu": {
      "url": "https://mcp.nalegalu.org/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "nalegalu": {
      "url": "https://mcp.nalegalu.org/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

case
get_case
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.
search_case_by_signature
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.
article
get_article
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.
law
search_law
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.
related
related_cases
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.
research
research_cases
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.
verify
verify_quote
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.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

health
removed 14 Aug 2026

Endpoints

URLTransportStateLatencyChecked
https://mcp.nalegalu.org/mcp streamable-http answering 388 ms 12 min ago

Alternatives to Nalegalu MCP

same job, measured the same way
Lexbase — legislação portuguesa
by lexbase

Search Portuguese consolidated legislation: the exact in-force article, official source.

answering
Simlir MCP Server
by simlir

Simlir MCP server for semantic product search, visual search, and exact product lookup.

22 installs/wk local only
Websharp
by jgador

Search the web and extract article text for LLMs.

local only
Deepcontext
by wild-card

Advanced codebase indexing and semantic search MCP server

118 installs/wk local only
Socraticode
by giancarloerra

MCP server for enterprise local codebase indexing, semantic search, and code dependency graphs.

2 850 installs/wk local only
I
FO Semantic MCP
by xplusplusai

Semantic search over 50,000+ Dynamics 365 F&O artifacts: tables, forms, classes, and more.

48 installs/wk local only
Jp Eli MCP
by matematicsolutions

MCP server for Japan's e-Gov law search API: search, fetch, and cite national legislation.

242 installs/wk local only
Research
by shamra-academia

The only MCP server for Arabic academic research — search, read & cite Arabic + English papers.

answering

Nalegalu MCP — questions

Answers built from our own checks of this server.

What can Nalegalu MCP do?
It exposes 7 tools, read directly from the server on our last check. Among them: get_article, get_case, related_cases, research_cases, search_case_by_signature, search_law and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Nalegalu MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 85 of 91 checks got a reply (93.4%), average response time 213 ms. The bar chart above shows every period we have measured.
Did Nalegalu MCP ever remove tools?
Yes. health is no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect Nalegalu MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Nalegalu MCP need an API key?
No. Nalegalu MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Nalegalu MCP?
It answers our handshake in 213 ms on average, which is faster than 67% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Nalegalu MCP open source?
Yes — it is published under the CC0-1.0 licence, written in Python, 9 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.