Skip to main content
Glama
matematicsolutions

ch-eli-mcp

by matematicsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ch-eli-mcp

No user-submitted related servers found.

    Related Servers

    • i14y-mcp

      malkreide
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Switzerland's national metadata catalogue, enabling AI agents to discover datasets, APIs, public services, and publishers through free-text search and structured queries.
      13
      MIT

    • swiss-courts-mcp

      malkreide
      A
      license
      A
      quality
      A
      maintenance
      MCP server for searching Swiss court decisions from federal and cantonal courts via entscheidsuche.ch. Enables full-text search, law reference lookup, and filtering by canton, court level, and date without API keys.
      8
      47 PyPI
      1
      MIT

    • termdat-mcp

      malkreide
      A
      license
      A
      quality
      A
      maintenance
      MCP server for TERMDAT, the terminology database of the Swiss Federal Administration, giving AI agents officially validated designations of Swiss authorities, departments, and legal acts across DE/FR/IT/EN with source references and validation status.
      7
      125 PyPI
      1
      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 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: searching act titles, fetching an act by ELI URI, and declaring coverage/gaps. There is no meaningful overlap between them.

    Naming Consistency4/5

    The ch_ prefix is consistent and data operations follow a verb_noun pattern: ch_search_acts and ch_get_act. ch_coverage deviates slightly by being a noun-only name, but the pattern is still readable and predictable.

    Tool Count4/5

    Three tools is lean but reasonable for a narrowly scoped legal retrieval connector. The count is slightly small, but each tool contributes a distinct capability rather than padding the surface.

    Completeness3/5

    The connector covers the essential search-and-fetch workflow for Swiss federal acts, and the explicit coverage tool helps surface gaps. However, the surface is minimal and lacks obvious conveniences such as browsing by family or fetching act versions, so some workflows will still require fallback to external sources.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources