A
licenseA
qualityB
maintenanceEnables retrieval of Belgian legislation metadata and full text by ELI coordinates from the official gazette (Moniteur Belge), supporting French, Dutch, and German languages.
3
Apache 2.0
lu-eli-mcp
Related Servers
Alternatives to lu-eli-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceProvides access to Maltese legislation via ELI coordinates, fetching metadata and full text from the official legislation.mt portal.3Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables querying and retrieving legal texts and decisions from French public APIs Légifrance and JudiLibre for legal research.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to query Hungary's official legislation database (NJT) using native ELI identifiers, retrieving metadata and full text with verifiable citations.6Apache 2.0
- AlicenseAqualityAmaintenanceEnables accessing Finnish legislation from the Finlex open-data API, listing statutes by year and retrieving their full texts with ELI identifiers and Finnish citations.4Apache 2.0
- AlicenseAqualityAmaintenanceFetches Croatian legislation from the Narodne novine official gazette with European ELI identifiers and verifiable citations. Provides tools to list issues, get act metadata, and fetch full text.4Apache 2.0
TDQS
A3.9/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: fetching metadata, fetching verbatim text, and declaring coverage/gaps. There is no overlap or ambiguity between them, so an agent can easily select the right tool for the task.
Naming Consistency4/5
All tools share the 'lu_' prefix, and two use the verb_noun pattern (get_act, get_text). However, 'lu_coverage' uses a noun directly rather than a verb, creating a minor deviation. The pattern is still readable and predictable overall.
Tool Count4/5
At 3 tools, the set is small but well-scoped for a read-only Luxembourg legislation connector. Each tool fills a necessary role, though a search/browse tool could be expected; the coverage tool partially compensates by documenting gaps.
Completeness4/5
The connector covers core operations: fetching metadata and full text, plus an explicit gaps/coverage tool to prevent false negatives. Missing a search or listing capability is a minor gap, but the coverage tool's fallbacks mitigate this.
Maintenance
ActivityMaintained
ResponsivenessNo issues