Lex-Ray

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.

{
  "type": "object",
  "properties": {},
  "required": []
}

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. 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.

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Search term - can be a keyword (e.g., 'artificial intelligence'), acronym (e.g., 'GDPR', 'AIA'), or CELEX ID (e.g., '32016R0679')"
    },
    "limit": {
      "type": "integer",
      "description": "Maximum number of results (1-50, default 10)",
      "default": 10
    }
  },
  "required": [
    "query"
  ]
}

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 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.

{
  "type": "object",
  "properties": {
    "celex_id": {
      "type": "string",
      "description": "The CELEX ID, Lex-Ray ID, nickname, or jurisdiction-prefixed nickname (e.g., '32016R0679', 'FCA-TS-s140', 'gdpr', 'uk-gdpr')"
    },
    "detail": {
      "type": "string",
      "enum": [
        "meta"
      ],
      "description": "Level of detail: 'meta' (titles, dates, OJ reference, classifications)",
      "default": "meta"
    },
    "fetch_if_missing": {
      "type": "boolean",
      "description": "Live fetch fallback: false only for this caller; unknown acts return structured not_found without an outbound EUR-Lex fetch",
      "default": false,
      "enum": [
        false
      ]
    }
  },
  "required": [
    "celex_id"
  ]
}