# Nalegalu MCP (remote · mcp.nalegalu.org)

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

- Trust score: 61/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.nalegalu.org`: 61/100 (this document), [markdown](https://verifymcp.io/servers/nalegaluorg-nalegalu/mcp.md), [page](https://verifymcp.io/servers/nalegaluorg-nalegalu/mcp)

## Channel facts

- Endpoint: `https://mcp.nalegalu.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 47/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 855 tokens (~122/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http nalegaluorg-nalegalu https://mcp.nalegalu.org/mcp
```

### Codex

```toml
[mcp_servers.nalegaluorg-nalegalu]
url = "https://mcp.nalegalu.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nalegaluorg-nalegalu": {
      "type": "remote",
      "url": "https://mcp.nalegalu.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nalegaluorg-nalegalu --url https://mcp.nalegalu.org/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nalegaluorg-nalegalu:
    url: "https://mcp.nalegalu.org/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 59, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 56, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 54, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 53)

First indexed and scored.

## MCP tools (7)

### `health` (~14 tokens)

Return local vector search service metadata.

### `search_law` (~97 tokens)

Search Polish legal acts and return compact article-level hits.

Input parameters:

- `act_type`
- `address`
- `article`
- `candidate_multiplier` (integer)
- `case_law_boost` (number)
- `domain`
- `include_non_in_force` (boolean)
- `limit` (integer)
- `query` (string, required)
- `status`
- `top_cases` (integer)

### `get_article` (~113 tokens)

Fetch the exact text of one article (or paragraph) of a Polish legal act.

        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.

Input parameters:

- `address` (string, required)
- `article_key` (string, required)
- `paragraph_key`

### `related_cases` (~108 tokens)

List SAOS court cases related to one article (or paragraph) of a Polish legal act.

        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.

Input parameters:

- `address` (string, required)
- `article_key` (string, required)
- `limit` (integer)
- `paragraph_key`

### `get_case` (~125 tokens)

Fetch one SAOS court judgment (metadata + bounded text excerpt).

        Use the saos_id from related_cases or search results. 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.

Input parameters:

- `max_chars` (integer)
- `offset` (integer)
- `saos_id` (integer, required)

### `search_case_by_signature` (~235 tokens)

Check whether a cited case signature (sygnatura) exists, e.g. "II CSK 448/14".

        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.

Input parameters:

- `court_type`
- `limit` (integer)
- `signature` (string, required)

### `verify_quote` (~163 tokens)

Check whether a quoted fragment actually appears in a SAOS judgment.

        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.

Input parameters:

- `min_similarity` (number)
- `quote` (string, required)
- `saos_id` (integer, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nalegaluorg-nalegalu/mcp#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 60
- 2026-08-01: 60
- 2026-07-31: 59
- 2026-07-30: 56
- 2026-07-29: 55
- 2026-07-28: 55
- 2026-07-27: 54
- 2026-07-26: 53

## Links

- Remote endpoint: https://mcp.nalegalu.org/mcp
- Repository: https://github.com/nalegaluorg/nalegalu
- Website: https://nalegalu.org/
- Changelog RSS feed: https://verifymcp.io/servers/nalegaluorg-nalegalu/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/nalegaluorg-nalegalu/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/nalegaluorg-nalegalu/mcp