Skip to main content
Glama
matematicsolutions

fi-eli-mcp

by matematicsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to fi-eli-mcp

No user-submitted related servers found.

    Related Servers

    • sk-eli-mcp

      matematicsolutions
      A
      license
      A
      quality
      B
      maintenance
      Enables access to Slovak legislation from the Collection of Laws via static.slov-lex.sk. Supports listing consolidated versions, retrieving act metadata, and fetching full text with verifiable citations.
      4
      1
      Apache 2.0

    • helmet

      zeriaxdev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching the HelMet library catalogue, retrieving full metadata for records, and locating which branches own a title with format and availability-of-collection information via the open Finna API.
      11,164,946 npm
      MIT

    • se-eli-mcp

      matematicsolutions
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to search and retrieve consolidated Swedish statutes (SFS) from the Riksdagen open data API, with verifiable citations and persistent identifiers.
      4
      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.
      -
    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

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing statutes by year, fetching metadata, fetching full text, and declaring coverage gaps. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    Three tools follow a consistent verb_noun pattern (fi_list_acts, fi_get_act, fi_get_text), but fi_coverage is a noun-only name that breaks the pattern. The inconsistency is minor and doesn't cause confusion.

    Tool Count4/5

    With 4 tools, the server is small but well-scoped for a focused legal data connector. The count is slightly below the typical range but each tool serves a necessary function in retrieval and transparent coverage reporting.

    Completeness4/5

    The tool surface covers core read operations (list, get metadata, get text) plus explicit coverage handling, which is a thoughtful safeguard. A keyword search or version history would be a natural addition but its absence is not a critical gap for the apparent purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources