Skip to main content
Glama
matematicsolutions

nl-eli-mcp

by matematicsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to nl-eli-mcp

No user-submitted related servers found.

    Related Servers

    • Dutch-law-mcp

      Ansvar-Systems
      A
      license
      A
      quality
      F
      maintenance
      Enables 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.
      18
      48 npm
      13
      Apache 2.0

    • finlex-mcp

      annasebedash-creator
      F
      license
      Not graded
      quality
      C
      maintenance
      An 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.
      -

    • dutch-gov-mcp

      Alishark14
      A
      license
      B
      quality
      D
      maintenance
      An unofficial MCP server providing access to Dutch government open data from data.overheid.nl, CBS statistics, and KVK business registry. Enables natural language queries for discovering datasets, inspecting metadata, and querying data without API keys or authentication.
      14
      MIT

    • lawyer-mcp

      pugafran
      F
      license
      A
      quality
      D
      maintenance
      MCP server for Legalize.dev, enabling AI to query and understand legal frameworks across countries via a structured legislation API.
      13
      1
      -

    • au-eli-mcp

      matematicsolutions
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Australia's Federal Register of Legislation. Enables searching and fetching Commonwealth Acts with verifiable citations.
      3
      Apache 2.0
    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.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: searching acts, fetching act metadata, fetching act text, searching cases, fetching a specific decision, and describing coverage. There is no realistic overlap that could lead an agent to pick the wrong tool.

    Naming Consistency4/5

    All tools share the nl_ prefix, which creates a recognizable namespace, but the internal pattern is not uniform: nl_get_* uses verb-first naming, while nl_case_search is object-first and nl_coverage is a bare noun. This is a minor inconsistency rather than a confusing mix.

    Tool Count5/5

    Six tools is well-scoped for a legal information connector covering both legislation and case law. Each tool serves a necessary retrieval or orientation purpose, and none feels redundant.

    Completeness5/5

    The set covers search, metadata retrieval, and full-text retrieval for acts, plus metadata-based search and full-decision retrieval for case law. The dedicated coverage tool explicitly documents limitations and fallbacks, which closes the main practical gap in legal data connectors.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources