STRIDE

What this MCP server is, what each access tier includes, and how to obtain access. Call this first if you are unsure what the server offers, or after any tool refuses you — the refusal names a tier, and this tool explains what that tier costs and what it adds. Requires no credentials.

What changes the law across the whole corpus in a window of dates: what has entered into force, started applying, been replaced by a new version or reached a deadline in the last months, and what will in the next ones. Each event says whether it is an entry into force or an application, and its act's position on as_at. Window with since/until or last_months/next_months (left out: the last 6 and the next 12 months, echoed); filter by kind, jurisdiction (eu, uk), subject_matter or instrument (regulation, directive, decision). Paged by cursor, with the total and the coverage: how many acts have no resolved date, are held, or are not indexed yet. `answerable` is false when too much of the scope is not indexed yet for the list to be read as complete: an empty list is then not "nothing changes". A uk-only query is read on London's legal day. Answers "what starts applying in the next 12 months" and "what changed in the last 6".

Retrieve one act by CELEX ID, Lex-Ray ID, nickname, or uk-/eu- prefix. 'meta' is the bibliographic record (titles, dates, Official Journal reference, EuroVoc concepts, amendments and relationships to other acts) and needs no credentials. 'data' adds the parsed legal content — recitals, articles, annexes, definitions — and 'full' adds the rendered HTML. Every level carries web_url, the act's Lex-Ray page, and a currency block: the day the answer was computed for, the commencement state on that day, and which version of the act is in force. Every answer also carries `pending_amendments`: proposals that propose to amend this act, each labelled in_flight / concluded / unknown, stamped with the reading date it was resolved against. These are PROPOSED, not enacted — never quote one as law.

Every dated event of one act, past and future, each classified: entry_into_force and application (kept apart, with their scope: the whole act, a staged tranche or a set of provisions), deadline (an obligation due date inside the act, never a state of any provision), transposition_deadline (directives; the subject is member_states), new_version (a change in the words, with the consolidated version), end_of_validity, and proposal (labelled proposed, never law). Each event states its date, kind, axis, subject and reach, scope, source, whether its date is held, and when it falls relative to as_at. The act's position (status and whom it is about) on as_at comes with it, with the coverage of what we hold. Answers "what is the full dated history and future of this act".

Find EU legislation and UK legislation by keyword, acronym (GDPR, DORA, AIA), the common name practitioners use ('Market Abuse Regulation', 'MLRs', 'UK GDPR'), CELEX ID or Lex-Ray id. Matching is case-insensitive and an exact name ranks ahead of partial title matches. Returns an envelope whose 'matches' array carries the bibliographic record for each match — titles, id, jurisdiction (eu/uk), Official Journal reference, dates — plus a currency block giving the commencement state as at today, so a match that is expired or not yet applying says so rather than reading as current law, and web_url, the act's Lex-Ray page. When several instruments share the exact name searched, 'ambiguous' is true and 'disambiguation' lists them: choose by jurisdiction and title rather than taking the first. When a curated common name settles it, 'preferred' names that act and 'alternatives' the others sharing the name. Use this to resolve a name to an id before calling the other tools. Requires no credentials.