Skip to main content
Glama
matematicsolutions

my-eli-mcp

by matematicsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to my-eli-mcp

No user-submitted related servers found.

    Related Servers

    • sg-eli-mcp

      matematicsolutions
      A
      license
      A
      quality
      B
      maintenance
      An MCP server for Singapore Statutes Online (SSO), the official portal for Singapore legislation. It browses, fetches, and cites Acts, with a verifiable citation on every response.
      4
      35 PyPI
      3
      Apache 2.0

    • 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
      54 PyPI
      Apache 2.0

    • pk-eli-mcp

      matematicsolutions
      A
      license
      A
      quality
      A
      maintenance
      MCP server for searching and retrieving Pakistani federal statutes and Supreme Court judgments with structured citations, using static HuggingFace datasets.
      6
      47 PyPI
      Apache 2.0

    • ie-eli-mcp

      matematicsolutions
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that provides access to the Irish Statute Book, enabling retrieval of metadata and full enacted text for Irish acts and statutory instruments by year, number, and type, with verifiable ELI identifiers and citations.
      3
      68 PyPI
      Apache 2.0

    • us-law-mcp

      seelpeed-debug
      A
      license
      A
      quality
      B
      maintenance
      MCP server for U.S. federal law that enables searching the U.S. Code, CFR, Federal Register, case law, and bills, with citation verification against primary sources to prevent hallucinations.
      11
      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

    A3.6/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools are largely distinct: one fetches metadata, one fetches full text, and one declares coverage/gaps. The only potential confusion is between my_get_act and my_get_text, but their descriptions clearly separate metadata from full text.

    Naming Consistency3/5

    Two tools follow a get_<object> pattern (my_get_act, my_get_text), but my_coverage uses a noun instead of a verb, breaking the pattern. The my_ prefix is consistent, but the mixed verb/noun structure is a minor inconsistency.

    Tool Count4/5

    Three tools is on the lower end but reasonable for a narrowly scoped connector that serves act metadata, act text, and coverage declarations. It feels slightly thin but not inadequate for its stated purpose.

    Completeness3/5

    The connector covers fetching individual acts and declaring coverage gaps, but lacks obvious operations like listing all acts or searching across acts. The coverage tool helps mitigate the absence, but the surface remains somewhat incomplete for a legal research tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources