Skip to main content
Glama
smridhiwho

open-india-law-mcp

by smridhiwho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to open-india-law-mcp

No user-submitted related servers found.

    Related Servers

    • LegalSearch

      Roop-World
      A
      license
      Not graded
      quality
      D
      maintenance
      Grounds external agents in public Indian judgments and statutes through MCP, enabling legal search and bounded document packets without requiring the full Roop platform.
      1
      MIT

    • legal_mcp

      barwojcik
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables semantic search over Polish court judgments and legislative acts via MCP. Allows LLMs to retrieve legal documents using natural language queries.
      Apache 2.0

    • 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

    • ecourts-mcp-server

      rithik-cmyk
      A
      license
      A
      quality
      D
      maintenance
      Connects LLMs to the EcourtsIndia Partner API for searching Indian court cases, retrieving orders, reading cause lists, and accessing AI summaries.
      9
      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.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a clearly distinct function: catalog discovery, schema inspection, raw SQL, legislation search, act retrieval, regulation search, judgment search, and judgment reassembly. The search_* and get_* pairs are cleanly separated, and run_sql is explicitly framed as a lower-level alternative rather than a competing high-level search tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: list_catalog, get_schema, run_sql, search_legislation, get_act, search_regulations, search_judgments, get_judgment. The naming convention is uniform and predictable.

    Tool Count5/5

    Eight tools is well-scoped for a legal research server: three low-level data-access tools and five domain-specific search/retrieval tools. Each tool earns its place and the count is neither thin nor bloated.

    Completeness4/5

    Legislation has both search and full-act retrieval, judgments have search and full-judgment reassembly, and regulations have search but no dedicated get_regulation tool analogous to get_act. That is a minor gap, though an agent can work around it using run_sql.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources