Skip to main content
Glama
synjan

mcp-lovdata

by synjan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-lovdata

No user-submitted related servers found.

    Related Servers

    • dk-lov-mcp

      mikkelmanniche-dk
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to look up Danish legislation by name or free text from Retsinformation, retrieve verbatim section text with official ELI links, and inspect status and later amendments. It also flags historical documents and unconsolidated amendments so returned legal text can be verified.
      Apache 2.0

    • Icelandic Law MCP

      Ansvar-Systems
      A
      license
      A
      quality
      F
      maintenance
      Provides 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.
      11
      37 npm
      1
      Apache 2.0

    • Türk Hukuk AI MCP

      ahmetaliunaall-prog
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables local, privacy-conscious research across Turkish case law and legislation by searching precedent and statutes, retrieving decisions and article trees/content, and assembling sourced research drafts with verified quotations.
      -

    • mcp-las

      jaggeman
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 12 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources