Finnish Law MCP Server
Related Servers
Alternatives to Finnish Law MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceAn MCP server providing direct, citable access to Finnish legislation by retrieving statute text from Finlex open data, enabling AI assistants to answer legal queries with accurate citations.-
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to search, retrieve, validate, and cross-reference Hungarian statutes and EU law, including full-text provisions, citation checks, and compliance status via MCP.58 npmApache 2.0
- AlicenseAqualityAmaintenanceEnables accessing Finnish legislation from the Finlex open-data API, listing statutes by year and retrieving their full texts with ELI identifiers and Finnish citations.4Apache 2.0
- AlicenseAqualityFmaintenanceEnables querying and analyzing Danish legislation, including search, citation validation, currency checks, and EU law integration, directly from AI assistants.1540 npm1Apache 2.0
- AlicenseAqualityAmaintenanceEnables AI agents to search and retrieve consolidated Swedish statutes (SFS) from the Riksdagen open data API, with verifiable citations and persistent identifiers.4Apache 2.0
- AlicenseAqualityFmaintenanceEnables querying over 3,200 Dutch statutes (AVG, Wetboek van Strafrecht, Burgerlijk Wetboek, etc.) with verbatim, citation-grounded text from official sources, directly from MCP-compatible AI assistants.1848 npm13Apache 2.0
TDQS
Scored across 16 tools
Each tool targets a distinct resource and action: validation, searching, retrieval, formatting, status checks, EU lookups, and metadata. Potential overlaps like validate_citation vs check_currency are clearly differentiated by input and purpose, and get_eu_basis vs get_provision_eu_basis are scoped by statute vs provision.
The vast majority of tools follow a consistent snake_case verb_noun pattern (search_legislation, get_provision, validate_eu_compliance). The single exception is 'about', which breaks the pattern, and get_provision_at_date has an extra preposition, though still clear.
16 tools is on the higher end of reasonable for a legal research server that spans statutes, case law, preparatory works, EU implementations, citation handling, and compliance. Each tool serves a distinct purpose, so the count feels justified rather than bloated.
The server covers core workflows comprehensively: searching, retrieving, validating, formatting, historical versions, and EU compliance. A notable gap is the lack of a direct tool to fetch a full court decision text (only search_case_law with summaries and keywords), which agents may need for deep case analysis.