au-eli-mcp
Related Servers
Alternatives to au-eli-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for the Federal Register of Legislation, enabling point-in-time searches, retrieval, and verification of Australian Commonwealth law, including citation checking.863 npm2MIT
- AlicenseAqualityBmaintenanceAn 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.435 PyPI3Apache 2.0
- AlicenseAqualityAmaintenanceAn MCP server for accessing Turkish legislation (laws, regulations, decrees) via the Adalet Bakanligi API, providing search, full-text retrieval, and structured citations.5147 PyPI1Apache 2.0

Vaquill-AI/vaquill-mcpofficial
AlicenseAqualityBmaintenanceMCP server for Vaquill legal research API. Covers US federal + 50-state law (USC, CFR, state legislation, CourtListener case law)257MIT- AlicenseAqualityAmaintenanceMCP server for the Laws of Malaysia Online portal, fetching and citing Malaysian principal Acts with verifiable citations.358 PyPIApache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes Austrian federal law (Bundesrecht) to LLMs, enabling full-text search, paragraph retrieval, historical versions, statute lookup, BGBl lookups, amendment timelines, and citation searches via the public RIS OGD API.-
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: searching by title, fetching full text by FRLI identifier, and reporting coverage/gaps. There is no functional overlap between the tools.
The au_ prefix is consistent, and two tools follow the verb_noun pattern (search_acts, get_text). However, au_coverage breaks the pattern by being a bare noun rather than an action-oriented name, creating a minor inconsistency.
Three tools is on the lean side but appropriate for a narrowly scoped legal research connector: search, retrieve, and coverage awareness. The count feels intentional rather than sparse.
The core workflow of searching and retrieving Act text is covered, and the explicit coverage tool acknowledges known gaps with fallbacks. Missing features like browsing all acts or version history are not clearly required for the stated purpose.