Skip to main content
Glama
matematicsolutions

tr-eli-mcp

by matematicsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to tr-eli-mcp

No user-submitted related servers found.

    Related Servers

    • Mevzuat MCP

      saidsurucu
      A
      license
      A
      quality
      B
      maintenance
      A FastMCP server providing access to the Turkish Ministry of Justice's Legislative Information System, allowing LLM applications to search legislation, retrieve article lists, and get article contents in Markdown format.
      3
      26
      101 PyPI
      234
      MIT

    • MutalaaMCP

      hburaktasyurek
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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

    • fr-eli-mcp

      matematicsolutions
      A
      license
      A
      quality
      A
      maintenance
      MCP server for querying French legislation and case law via the Legifrance API, enabling search and retrieval of laws, codes, and court decisions with verifiable citations.
      8
      50 PyPI
      2
      Apache 2.0

    • eqanun-api

      beerbottle90
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Azerbaijan's official legal-acts database (e-qanun.az), enabling search, metadata retrieval, and full-text access to legislative and judicial documents.
      MIT
    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.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of Turkish legislation: searching, listing types, fetching full text, fetching table of contents, and declaring coverage gaps. There is no meaningful overlap; even get_legislation_content and get_legislation_toc are clearly separated by the type of content returned.

    Naming Consistency4/5

    Most tools follow a consistent tr_<verb>_<object> pattern (tr_search_legislation, tr_list_legislation_types, tr_get_legislation_content, tr_get_legislation_toc). The lone exception is tr_coverage, which uses a noun instead of a verb, creating a minor but noticeable deviation.

    Tool Count5/5

    Five tools is well-scoped for a legal research connector: two for discovery, two for retrieval, and one for coverage metadata. Each tool serves a clear purpose and none feel redundant or extraneous.

    Completeness5/5

    The surface covers the core workflow of searching, enumerating types, fetching full text, and navigating structure via TOC, plus a dedicated gap-awareness tool. For a read-only legislation domain, this is complete; there are no obvious missing operations that would block typical agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources