Categories › Knowledge & Everyday › Government & public data
Temporal search and comparison for official Luxembourg and reviewed EU law, with provenance.
Remote server: your requests and data go to law.soufien.lu. Claude Code: claude mcp add --transport http lex-temporal-luxembourg-and-eu-law https://law.soufien.lu/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
resolve — Resolve a Luxembourg legal-act identifier or a hash-pinned permalink to the work and expression it names.as_of — The state of a Luxembourg act applicable on a date (publisher), with its articles; for an EU act, the wording dated at or before the date (atimeline — Every state of a Luxembourg act the index holds, in publisher applicability order; for an EU act, every wording its census discovered, in woarticle_history — The history of one article of a Luxembourg act across its states.diff — The article-level difference between the states of a Luxembourg act on two dates.changes_in_period — The Luxembourg states that began in a period, for a work or across the index.in_force_on — The Luxembourg works with a state applicable on a date.search — With no work named, first read the query as an exact reference (an ELI, a CELEX, an EU act's name, a Memorial citation, a historical identifcoverage — What this mount holds and serves, named, and what it does not.provenance — The retained sources, rule profiles and digests behind a Luxembourg state.dossier — The work record of a Luxembourg act as the index holds it; for an EU work named by identifier, its held expressions from the EU index.citation — The references the publisher wrote in the text of a Luxembourg state's articles.cited_by — The references, in any held Luxembourg state, whose target is exactly this work.verify — Verify a hash-pinned permalink against the state digest the index holds, or read the current digests to pin.relations — The reference edges of a Luxembourg work in both directions, as one ordered, paged list.evidence_bundle — What a quote of a Luxembourg state needs, one bounded page at a time (at most 50 articles and 96 KiB of text; page or article chooses the paclassification — The publisher's typed facts about a Luxembourg work, verbatim: document type, RDF types, legal value, responsible body, historical identifiemanifestation — The publisher's manifestations of a Luxembourg work's expressions with their formats and items, the retained one marked with its body digeststatus_on — The publisher's force assertions about a Luxembourg work (its inForceStatus, dateEntryInForce and dateNoLongerInForce facts), verbatim, besibrowse — The Luxembourg works this mount holds, one ordered and paged list with their identifiers, languages, state dates and the publisher's documenask — The assistant, switched on as a labelled preview: the question, with obvious identifiers masked by code, is sent to the configured processorevents — The Luxembourg event log, polled by cursor, at least once: a genesis log holds one first_sighting per held state; a chained log adds each laanswer_drift — The past dated answers a publisher revision invalidated, enumerated from the log's revising events; a genesis log holds none, and the answeras_observed — The state of a Luxembourg act applicable on a date (publisher) as one build of the mounted log held it, named by that build's index digest, concepts — Not served: the EuroVoc descriptors, directory codes and subject matters of EU works, which no index holds; every call answers the typed refknowable_on — Not served: what a reader could have known on a date, from publication and observation times, which no build records; every call answers thetransposition — Not served: the transposition links between EU directives and Luxembourg measures, which are not acquired; every call answers the typed refuNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.