hr-eli-mcp
Related Servers
Alternatives to hr-eli-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables access to Slovak legislation from the Collection of Laws via static.slov-lex.sk. Supports listing consolidated versions, retrieving act metadata, and fetching full text with verifiable citations.41Apache 2.0
- AlicenseAqualityAmaintenanceEnables querying Luxembourg legislation metadata and full Akoma Ntoso text via ELI identifiers from Legilux open data.366 PyPI1Apache 2.0
- AlicenseNot gradedqualityFmaintenanceProvides access to Croatian law via MCP, enabling full-text search across 4,531 statutes and 157,667 provisions, citation validation, and EU directive cross-references from official sources.28 npmApache 2.0
- AlicenseAqualityAmaintenanceProvides access to Maltese legislation via ELI coordinates, fetching metadata and full text from the official legislation.mt portal.3141 PyPIApache 2.0
- AlicenseAqualityAmaintenanceEnables AI agents to query Hungary's official legislation database (NJT) using native ELI identifiers, retrieving metadata and full text with verifiable citations.661 PyPIApache 2.0
- AlicenseAqualityBmaintenanceEnables retrieval of Belgian legislation metadata and full text by ELI coordinates from the official gazette (Moniteur Belge), supporting French, Dutch, and German languages.346 PyPIApache 2.0
TDQS
Scored across 4 tools
hr_get_act and hr_get_text are clearly separated as metadata versus full HTML text, and hr_list_issue handles discovery by gazette issue. hr_coverage is distinct as a meta-tool for gaps. The only minor risk is that hr_get_act and hr_get_text both accept ELI coordinates, but their descriptions resolve the boundary.
Tools share a consistent hr_ prefix and mostly follow a verb_noun pattern: hr_list_issue, hr_get_act, hr_get_text. hr_coverage breaks the pattern by using a noun-only name, though it is still understandable and consistent in style.
Four tools is an appropriate, focused scope for an ELI legal document connector. Each tool performs a distinct retrieval or coverage function, and none feel redundant or missing as a core operation.
The server covers the core workflow: discovering documents by issue, fetching metadata, and retrieving full text. A full-text or title search is absent, but hr_coverage explicitly documents known gaps and fallback sources, which mitigates the limitation.