hu-eli-mcp
Related Servers
Alternatives to hu-eli-mcp
No user-submitted related servers found.
Related Servers
- 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.41 npmApache 2.0
- AlicenseNot gradedqualityFmaintenanceQuery 4,326 Hungarian laws (Ptk., Mt., Btk., etc.) from MCP-compatible clients. Includes full-text search, citation validation, and EU law mapping.41 npm25Apache 2.0
- AlicenseAqualityAmaintenanceProvides access to Maltese legislation via ELI coordinates, fetching metadata and full text from the official legislation.mt portal.366 PyPIApache 2.0
- AlicenseAqualityAmaintenanceEnables AI agents to search and retrieve consolidated Swedish statutes (SFS) from the Riksdagen open data API, with verifiable citations and persistent identifiers.4Apache 2.0
- AlicenseNot gradedqualityFmaintenanceEnables querying and searching Romanian legislation, including statutes, provisions, and EU law integration, directly from AI clients.45 npm5Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides AI assistants with up-to-date legal documents from official sources, enabling accurate legal information retrieval and analysis.18AGPL 3.0
TDQS
Scored across 6 tools
The tools mostly partition cleanly: hu_get_act and hu_get_legislation both fetch metadata, and for Acts there is potential overlap, but the descriptions clearly route Acts to hu_get_act and everything else to hu_get_legislation. The remaining tools are distinct, covering text retrieval, code lookups, and coverage declarations.
All tools share the hu_ prefix and mostly follow a get/list verb pattern, which makes the set predictable. hu_coverage is the one naming outlier since it uses a bare noun rather than a verb_noun form, but the inconsistency is minor.
Six tools is well-scoped for a focused read-only legal connector: metadata retrieval for Acts, metadata retrieval for other legislation, full-text retrieval, two code-list helpers, and a coverage declaration. Each tool has a clear role with no obvious redundancy.
The set covers the core identifier-driven workflows: resolve document types and issuers, fetch metadata by ELI, and retrieve full text. The main gap is the absence of a search or browse capability, but the server explicitly frames itself around known ELI identifiers and documents its coverage gaps through hu_coverage.