mcp-lovdata
Related Servers
Alternatives to mcp-lovdata
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides offline full-text search across 35,000+ Swiss laws from all cantons and federal level using SQLite FTS5 indexing. Enables querying laws, articles, and metadata through natural language.1MIT
- AlicenseAqualityFmaintenanceProvides access to 1,709 Icelandic statutes and 19,026 provisions with full-text search, citation validation, and EU/EEA law integration, enabling legal research and compliance checks through natural language queries.1138 npm1Apache 2.0
- AlicenseAqualityFmaintenanceEnables querying and analyzing Danish legislation, including search, citation validation, currency checks, and EU law integration, directly from AI assistants.1532 npm1Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables Swedish labor law research and analysis by providing exact statute lookup, hybrid semantic and lexical search, Arbetsdomstolen case law retrieval, and collective agreement comparisons.2-
- AlicenseAqualityAmaintenanceProvides access to Danish legislation from Retsinformation.dk, enabling retrieval of act metadata, full text, and recent changes with verifiable citations.452 PyPIApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI clients to research official Turkish legal sources locally by searching judicial decisions, legislation, and Constitutional Court decisions, and by retrieving legal documents, individual articles, and legislation structures.MIT
TDQS
Scored across 12 tools
Each corpus has its own clearly namespaced search/get pair (caselaw_, preparatory_, ombudsman_), and the generic search tool is explicitly scoped to statute paragraphs. get_document vs get_article are also clearly separated by document-level vs article-level retrieval, so there is no real overlap.
The dominant pattern is clear: `domain_search` and `domain_get` for the three secondary legal sources. However, the main corpus uses get_document and get_article rather than law_document/law_get, and status/sync are bare words that don't follow the verb_noun or domain_action pattern. Still, all names are readable and predictable once the pattern is understood.
Twelve tools is well within the ideal range for a legal research server with four distinct source types. Each tool covers a necessary retrieval or maintenance need, and none feel redundant.
The surface is comprehensive for its stated domain: statute search and retrieval, document listing, article-level detail with history, ECHR case law retrieval, preparatory works, and ombudsman opinions all have search and get coverage. The only notable absence is Norwegian court caselaw, but the tool descriptions explicitly explain that no free machine-readable source exists, so it is a data-availability limitation rather than a design gap.