arlis-mcp
Related Servers
Alternatives to arlis-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search Turkish legislation by natural-language query or citation, retrieve full article text including ranges and paragraphs, and return results with official citations, Official Gazette details, and source links.1Apache 2.0
- AlicenseAqualityBmaintenanceEnables read-only search and retrieval of Latvia's legislation and multi-tier court decisions, with citation verification against official registries. Supports filtering case law by judicial instance and retrieving full texts as Markdown for legal research.6MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to search, retrieve, validate, and cross-reference Hungarian statutes and EU law, including full-text provisions, citation checks, and compliance status via MCP.55 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides AI assistants with up-to-date legal documents from official sources, enabling accurate legal information retrieval and analysis.21AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceProvides programmatic access to Turkey's Ministry of Justice Legislation Information System (mevzuat.gov.tr), enabling users to search legislation, retrieve article hierarchies, and fetch article contents in Markdown format through natural language.1MIT
- AlicenseNot gradedqualityFmaintenanceEnables querying and searching Romanian legislation, including statutes, provisions, and EU law integration, directly from AI clients.57 npm5Apache 2.0
TDQS
Scored across 2 tools
The two tools have clearly distinct roles: search_acts discovers acts and returns metadata/URLs, while get_act retrieves and saves the full text for a specific act URL. There is no realistic ambiguity about which tool to use for discovery versus retrieval.
Both names follow the same snake_case verb_noun convention: search_acts and get_act. The pattern is predictable and directly reflects each tool's action.
Two tools are slightly thin for the generic 3–15 range, but they map cleanly to the server's narrow search-and-retrieve purpose. Neither tool feels redundant or extraneous.
The surface covers the core workflow of finding an act and fetching its text, with metadata and local file output. Minor gaps exist around pagination, version handling, or more structured retrieval, but the main use case is supported.