Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

eu.ansvar/finnish-law-mcp

NPM · @ANSVAR/FINNISH-LAW-MCP · SCANNED OCT 3

Query Finnish statutes from Finlex, EU cross-references, case law, and preparatory works

−1 this week 81 Trust /100

Deprecated

This server is marked deprecated in the MCP registry.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security92
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency42
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2577 tokens (~151/item across 17 items; 16 tools + 1 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 Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the eu.ansvar/finnish-law-mcp server?

eu.ansvar/finnish-law-mcp runs locally as an npm package, launched with npx -y @ansvar/finnish-law-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @ansvar/finnish-law-mcp

# add to Claude Code
claude mcp add eu-ansvar-finnish-law-mcp -- npx -y @ansvar/finnish-law-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "eu-ansvar-finnish-law-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ansvar/finnish-law-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "eu-ansvar-finnish-law-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ansvar/finnish-law-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add eu-ansvar-finnish-law-mcp -- npx -y @ansvar/finnish-law-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "eu-ansvar-finnish-law-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@ansvar/finnish-law-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add eu-ansvar-finnish-law-mcp --command npx --arg -y --arg @ansvar/finnish-law-mcp
# ~/.hermes/config.yaml
mcp_servers:
  eu-ansvar-finnish-law-mcp:
    command: "npx"
    args: ["-y", "@ansvar/finnish-law-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "eu-ansvar-finnish-law-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@ansvar/finnish-law-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add eu-ansvar-finnish-law-mcp -t stdio -c npx -a -y @ansvar/finnish-law-mcp
// mcp.json
{
  "mcpServers": {
    "eu-ansvar-finnish-law-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ansvar/finnish-law-mcp"
      ]
    }
  }
}
Changelog

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.

  • 2 Oct 26 +1

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

  • 30 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 29 Sept 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 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
  • 27 Sept 26 +1

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

  • 25 Sept 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
  • 23 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 22 Sept 26 +1
    • Stability: 0.97 → pass security
Diagnostics

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 3 Oct 2026 · Analysed npm/@ansvar/finnish-law-mcp@1.2.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
postinstall unreviewed test -d dist || npm run build || true

Background: Why install scripts are a supply-chain risk →

Dependencies 94 packages
Packages resolved 94
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~2,562 tokens

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 →

Tool Tokens
about ~35

Server metadata, dataset statistics, freshness, and provenance. Call this to verify data coverage, currency, and content basis before relying on results.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

build_legal_stance ~173

Build a comprehensive set of citations for a legal question. Searches across statutes, case law, and preparatory works simultaneously to aggregate relevant citations. Use this for broad legal research questions. When NOT to use: If you need a specific provision or targeted search, use get_provision or search_legislation instead.

NameTypeReqDescription
as_of_datestring–Optional historical date (YYYY-MM-DD) for time-aware retrieval.
document_idstring–Optionally limit statute search to one document
include_case_lawboolean–Include case law results (default: true)
include_preparatory_worksboolean–Include preparatory works results (default: true)
limitnumber–Max results per category
querystringyesLegal question or topic to research

No output schema declared.

No examples provided.

check_currency ~155

Check if a Finnish statute or provision is in force (current or historical). Returns the document's status (in_force, amended, repealed, not_yet_in_force), dates, and warnings. Provide as_of_date for historical evaluation. When NOT to use: If you need the actual text of a provision, use get_provision. This tool only checks status.

NameTypeReqDescription
as_of_datestring–Optional historical date (YYYY-MM-DD). Computes in-force status as of that date.
document_idstringyesstatute number (e.g., "1050/2018" or "2018:218")
provision_refstring–Optional provision reference to check (e.g., "3:5")

No output schema declared.

No examples provided.

format_citation ~117

Format a Finnish legal citation per standard conventions. Formats: - full: "Laki 1050/2018 3 luku 5 §" - short: "1050/2018 3:5" - pinpoint: "3 luku 5 §" When NOT to use: If you want to check whether a citation exists in the database, use validate_citation instead.

NameTypeReqDescription
citationstringyesCitation string to format
formatstring–Output format (default: "full")

No output schema declared.

No examples provided.

get_eu_basis ~172

Get EU legal basis (directives and regulations) for a Finnish statute. Returns all EU directives and regulations that this statute implements, supplements, or references. Includes reference types, article citations, and whether each EU document is a primary implementation. Essential for understanding which EU law a Finnish statute is based on. When NOT to use: For provision-level EU references, use get_provision_eu_basis. To find Finnish laws implementing EU law, use get_finnish_implementations.

NameTypeReqDescription
include_articlesboolean–Include specific EU article references (default: false)
reference_typesarray–Filter by reference type (implements, supplements, applies, etc.)
sfs_numberstringyesstatute number (e.g., "1050/2018" or "2018:218")

No output schema declared.

No examples provided.

get_finnish_implementations ~170

Find Finnish statutes implementing a specific EU directive or regulation. Given an EU document ID (e.g., "regulation:2016/679" for GDPR), returns all Finnish statutes that implement, supplement, or reference it. Shows implementation status and which articles are referenced. Essential for finding Finnish law corresponding to EU requirements. When NOT to use: If you have a Finnish statute and want its EU basis, use get_eu_basis (opposite direction).

NameTypeReqDescription
eu_document_idstringyesEU document ID (e.g., "regulation:2016/679", "directive:95/46")
in_force_onlyboolean–Return only in-force statutes (default: false)
primary_onlyboolean–Return only primary implementing statutes (default: false)

No output schema declared.

No examples provided.

get_preparatory_works ~106

Get preparatory works (esityöt) for a Finnish statute. Returns linked government proposals (HE), committee reports, and related documents with summaries. Essential for understanding legislative intent behind statutory provisions. When NOT to use: If you need the statute text itself, use get_provision. Preparatory works explain legislative intent, not current law.

NameTypeReqDescription
document_idstringyesstatute number (e.g., "1050/2018" or "2018:218")

No output schema declared.

No examples provided.

get_provision ~268

Retrieve a specific provision from a Finnish statute. Specify the statute number and either chapter+section or provision_ref directly. Examples: - document_id="1050/2018", chapter="1", section="1" → 1 luku 1 § - document_id="1050/2018", provision_ref="1:1" → same result - document_id="434/2003", section="6" → 6 § (flat lookup) Omit chapter/section/provision_ref to get all provisions in the statute. When NOT to use: If you are searching by keyword and don't know the exact statute/provision, use search_legislation instead.

NameTypeReqDescription
as_of_datestring–Optional historical date (YYYY-MM-DD). Returns the provision text valid on that date.
chapterstring–Chapter number (e.g., "3"). Omit for flat statutes.
document_idstringyesstatute number (e.g., "1050/2018" or "2018:218")
provision_refstring–Direct provision reference (e.g., "3:5" for luku 3 § 5)
sectionstring–Section number (e.g., "5", "5 a")

No output schema declared.

No examples provided.

get_provision_at_date ~258

Retrieve Finnish statute provision text as it read on a specific date (time-travel query). This tool enables historical legal research by showing how a provision was worded at any point in time, accounting for all amendments since original enactment. Use cases: - "What did Tietosuojalaki 1:3 say in 2019?" - "Show me Rikoslaki 3:1 before the 2019 amendment" - "Was this provision in force on 2020-06-15?" Supports: - Historical versions (any date in the past) - Current version (today's date) - Future provisions (enacted but not yet in force) Returns the complete provision text, validity dates, and optionally the amendment history showing what changed after the queried date.

NameTypeReqDescription
datestringyesISO date (YYYY-MM-DD) to query
include_amendmentsboolean–Include amendment history after this date (default: false)
provision_refstringyesProvision reference (e.g., "1:3" or "5")
sfsstringyesStatute number (e.g., "1050/2018" for Tietosuojalaki)

No output schema declared.

No examples provided.

get_provision_eu_basis ~147

Get EU legal basis for a specific provision within a Finnish statute. Returns EU directives/regulations that a specific provision implements or references, with article-level precision. For example, DSL 2:1 references GDPR Article 6.1.c. Use this for pinpoint EU compliance checks at the provision level. When NOT to use: For statute-level EU references (not a specific provision), use get_eu_basis instead.

NameTypeReqDescription
provision_refstringyesProvision reference (e.g., "1:1" or "3:5")
sfs_numberstringyesstatute number (e.g., "1050/2018" or "2018:218")

No output schema declared.

No examples provided.

list_sources ~39

List all authoritative data sources used by this server, including provider, license, coverage, and freshness metadata. Call this to understand where the data comes from.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_case_law ~166

Search Finnish court decisions (oikeustapaukset). Searches case summaries and keywords. Filter by court (KKO, KHO, hovioikeus, etc.) and date range. When NOT to use: If you need statute text, use search_legislation. Case law searches only cover court decisions.

NameTypeReqDescription
courtstring–Filter by court (e.g., "KKO", "KHO", "hovioikeus")
date_fromstring–Start date filter (ISO 8601, e.g., "2020-01-01")
date_tostring–End date filter (ISO 8601)
limitnumber–Maximum results
querystringyesSearch query for case law summaries

No output schema declared.

No examples provided.

search_eu_implementations ~185

Search for EU directives and regulations with Finnish implementation information. Search by keyword, type, year range, or community. Returns matching EU documents with counts of Finnish statutes referencing them. Use this for exploratory searches like "data protection" or "privacy" to find relevant EU law. When NOT to use: If you already know the EU document ID, use get_finnish_implementations for direct lookup.

NameTypeReqDescription
communitystring–Filter by community
has_finnish_implementationboolean–Filter by Finnish implementation existence
limitnumber–Maximum results
querystring–Keyword search (title, short name, CELEX, description)
typestring–Filter by document type
year_fromnumber–Filter by year (from)
year_tonumber–Filter by year (to)

No output schema declared.

No examples provided.

search_legislation ~200

Search Finnish statutes and regulations by keyword. Searches provision text using FTS5 with BM25 ranking. Supports boolean operators (AND, OR, NOT), phrase search ("exact phrase"), and prefix matching (term*). Returns matched provisions with snippets, relevance scores, and document metadata. When NOT to use: If you already know the exact statute number and provision, use get_provision instead. If you need a comprehensive multi-source answer, use build_legal_stance.

NameTypeReqDescription
as_of_datestring–Optional historical date filter (YYYY-MM-DD). Returns versions valid on that date.
document_idstring–Filter to a specific statute by statute number (e.g., "1050/2018" or "2018:218")
limitnumber–Maximum results
querystringyesSearch query in Finnish or English. Supports FTS5 syntax.
statusstring–Filter by document status

No output schema declared.

No examples provided.

validate_citation ~186

Validate a Finnish legal citation against the database. Parses the citation, checks that the document and provision exist, and returns warnings about status (repealed, amended). This is the zero-hallucination enforcer. Supported formats: - "Laki 1050/2018 1 luku 1 §" - "1050/2018 1:1" - "SFS 2018:218 1 kap. 1 §" (legacy compatibility) - "Prop. 2017/18:105" - "SOU 2017:39" - "NJA 2020 s. 45" When NOT to use: If you want to format a citation string, use format_citation. This tool checks existence in the database.

NameTypeReqDescription
citationstringyesCitation string to validate

No output schema declared.

No examples provided.

validate_eu_compliance ~185

Validate EU compliance status for a Finnish statute or provision. Checks for: - References to repealed EU directives (e.g., Data Protection Directive 95/46/EC) - Missing implementation status - Outdated references Returns compliance status (compliant, partial, unclear, not_applicable) with warnings and recommendations. Note: This is Phase 1 validation. Full compliance checking against EU requirements will be added in future phases. When NOT to use: For basic EU reference lookup, use get_eu_basis. This tool assesses compliance status.

NameTypeReqDescription
eu_document_idstring–Optional: check compliance with specific EU document
provision_refstring–Optional provision reference (e.g., "1:1")
sfs_numberstringyesstatute number (e.g., "1050/2018" or "2018:218")

No output schema declared.

No examples provided.

Common questions

What is the eu.ansvar/finnish-law-mcp server?

eu.ansvar/finnish-law-mcp is listed in the public MCP registry as eu.ansvar/finnish-law-mcp. Query Finnish statutes from Finlex, EU cross-references, case law, and preparatory works. This page covers its npm package (@ansvar/finnish-law-mcp).

Is the eu.ansvar/finnish-law-mcp server safe to use?

eu.ansvar/finnish-law-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 3 October 2026. 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 eu.ansvar/finnish-law-mcp server expose?

eu.ansvar/finnish-law-mcp exposes 16 tools: search_legislation, get_provision, search_case_law, get_preparatory_works, validate_citation, and 11 more. Their descriptions and schemas cost roughly 2,562 tokens of context every time the server is loaded.

Is the eu.ansvar/finnish-law-mcp server still maintained?

eu.ansvar/finnish-law-mcp is marked deprecated in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the eu.ansvar/finnish-law-mcp server under?

eu.ansvar/finnish-law-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.