Skip to content
Rettsarkiv logo

Rettsarkiv MCP server

Which MCP servers are Rettsarkiv's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Rettsarkiv

Whose server it is
  • Registry nameno.rettsarkiv/rettsarkivverified in the MCP registry

The registry name sits under rettsarkiv.no. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools8
  • Server calls itselfrettsarkiv
  • Server version1.27.2
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 217 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Find Norwegian court decisions by topic; Link court decisions to the statutes they rely on.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "Find Norwegian court decisions by topic", the likely first call is search_decisions.
  • Parameters are untyped or undescribed in 8 of 8 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer225 ms
  • Space in an agent's context≈ 2,341 tokensthe definitions of all its tools (8), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 8 of 8

What an agent can do with it

  • can do · Find Norwegian court decisions by topic
  • can do · Link court decisions to the statutes they rely on

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers8 tools · read 2026-10-26
  • search_decisions

    Fritekstsøk i norske Høyesteretts-avgjørelser — rangerte treff, klare til å presenteres direkte. Hver rad: `primary_id`, `decision_date`, `summary`, `sitering_count`. Oppgi `lov`+`section` for å begrense til dommer som anvender en bestemt…

  • find_decisions_applying_law

    «Hvilke Høyesteretts-dommer anvender <lov> § <n>?» Returnerer en ferdig RANGERT liste, klar til å presenteres direkte for brukeren. Hver rad: `primary_id`, `decision_date`, `summary`, `sitering_count`, lesbar `section` («§ 192 Voldtekt»)…

  • find_similar_decisions

    «Hvilke dommer henger sammen med <id>?» — presedens-naboer via SITATGRAFEN. Dette er det PÅLITELIGE relevans-signalet for presedens: ikke at to dommer deler en paragraf (svakt — en § dekker vidt forskjellige saker), men at de henger…

  • get_decision

    Hent én avgjørelse med stabil id (HR-2024-123-A eller Rt-1979-524). Returnerer strukturert tekst, lov-taggede §-referanser og provenance (source_origin + content_hash). Hver §-tag har lesbar overskrift (section_heading). Sett…

  • get_law_section

    Hent tekst for en lovparagraf (NLOD-fri lovtekst), f.eks. lov='straffeloven', section='257' → «§ 257 Menneskehandel …». UTGAVE-BEVISST: oppgi `on_date` (domsdato) for flertydig korttittel — teksten er for den OPPLØSTE utgaven, aldri en…

  • get_law

    Slå opp en lov med metadata + innholdsfortegnelse (paragraf-overskrifter). `lov` kan være lovdata-id (2005-05-20-28) eller korttittel (straffeloven). Bruk get_law_section for selve teksten i en enkelt paragraf.

  • resolve_law

    Slå opp en lovs kanoniske lovdata-id fra korttittel/navn, UTGAVE-BEVISST. VIKTIG: samme korttittel kan peke på ULIKE lover (utgaver) etter ikraft-dato, og samme §-nummer betyr da ULIKE ting. Eksempel: straffeloven § 257 = menneskehandel i…

  • list_changes

    Nye/oppdaterte avgjørelser siden en markør (ISO-tidsstempel). Returnerer en `next`-markør for inkrementell synk. Til full nedlasting av hele korpuset (avsnitt-chunks + embeddings + §-tags): bruk /export-endepunktet (NDJSON) i REST-API-et…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "rettsarkiv": {
      "type": "http",
      "url": "https://rettsarkiv-mcp-953525390683.europe-west3.run.app/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http rettsarkiv https://rettsarkiv-mcp-953525390683.europe-west3.run.app/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://rettsarkiv-mcp-953525390683.europe-west3.run.app/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.