Skip to main content
Glama
tomilashy

canlii-mcp

by tomilashy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to canlii-mcp

No user-submitted related servers found.

    Related Servers

    • canlii-mcp

      Vaquill-AI
      A
      license
      A
      quality
      B
      maintenance
      An MCP server providing AI assistants access to Canadian case law and legislation metadata from CanLII across all jurisdictions, supporting search and citation relationships.
      7
      6 npm
      5
      MIT

    • cl-eli-mcp

      matematicsolutions
      A
      license
      A
      quality
      A
      maintenance
      MCP server for searching and fetching metadata of Chilean laws, decrees, and resolutions via the BCN Linked Open Data SPARQL endpoint.
      3
      Apache 2.0

    • 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
      1
      MIT

    • lex-scholar-api

      beerbottle90
      A
      license
      Not graded
      quality
      B
      maintenance
      Single-endpoint MCP server federating nine open-access legal scholarship indexes, enabling federated search, multi-jurisdiction comparison, and full-text retrieval via tools like search_legal_scholarship and compare_jurisdictions.
      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/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource: getting specific items (legislation, case, citations) versus listing collections (databases, legislation, cases). No overlap or ambiguity exists.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using lowercase with underscores, using either 'get_' for specific resources or 'list_' for collections. The convention is uniform and predictable.

    Tool Count5/5

    Seven tools is well-scoped for a legal document retrieval server. Each tool covers an essential operation without redundancy or bloat.

    Completeness4/5

    The tool set covers metadata retrieval, database listings, and citation graphs, but lacks any search functionality for cases or legislation. This is a notable gap for a legal research API, though the core lookup workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources