Payments Law EU MCP Server

Use this to read and compare the held legislative definitions of a term, such as payment transaction in PSD2 and PSR. These are source definitions, not a general dictionary or a legal opinion. Every definition verbatim and resolved, clustered by what the text actually says, with the chronological and concurrent views and word-level comparisons between them. Resolution follows the CITED version, never legislative succession: a definition citing a repealed act resolves to that act and is labelled repealed, not silently replaced by its successor's wording. A term the corpus does not define is refused with suggestions — nothing is substituted. references_in gives the reverse edges: which definitions lean on this one.

Use this to find which EU instruments define a legal term, such as payment transaction or payment account, and where their definitions differ. For definition wording use get_defined_term. A listing: term, definers and divergence flags, with no definition text. Matching is over the term itself, never the definition body. Divergence is judged on the RESOLVED text as well as the verbatim one, because several instruments defining a term by pointing at the same root agree, however differently their pointers read. Pass only_divergent to find where the corpus does not agree with itself.

Use this to compare an article between the held Commission proposal and Council compromise versions of PSR or PSD3, within the same instrument. Serves the word-level comparison the build published: a pair is servable if and only if a diff artefact exists for it — the PSR and PSD3 proposal↔compromise pairs and nothing else. Every other pair, including every consolidated instrument's pinned as-adopted text, is refused with the URL where that text is published; this service never recomputes a comparison. Pairs match in either direction, and a reversed request is the same artefact with the ops inverted. `changes` reads that artefact structurally — paragraphs added or deleted, figures and durations moved, a heading rewritten — for a caller that needs what KIND of change this was without parsing the word-level ops. It is scoped to the article, not to the page of ops, and locates each entry no more precisely than the served text allows.

Use this to open and cite an EU legislative provision found by search. OpenAI-compatible retrieval: the full text of one provision by its cite anchor id (e.g. "psd-2 Art 97"), with citation metadata. Accepts only ids this service minted — free-text citations belong to resolve_citation. get_provision returns more: paging, applicability and typed warnings.

Use this to check an EU instrument's recorded legal status, source version, dates and amendments, including whether a held PSR or PSD3 text is a proposal or compromise. Metadata, dates, lifecycle and application events, and curated relationships. Each relationship names the operative amending or repealing article where curated (openable with get_provision) and the counterpart's legal status at the release. An operative_cite can arrive without an operative_locator: the article is real but the served text has dropped it, and operative_locator_unavailable says so. An amender outside the corpus is named under source_external, whose via_article carries its article. No article index — use list_provisions. Pass on_date for the multi-axis applicability record on that date.

Use this to discover which EU instruments are held before a coverage question, or find their registry ids and legal status. Paginated, filterable by status, category, core/supplementary, and by whether an instrument was in force on a given date. For corpus-coverage questions, filter by category here, enumerate each instrument with list_provisions, then open what you need with get_provision.

Use this to find EU legislative provisions on payment-services questions: strong customer authentication (SCA), dynamic linking, open banking, safeguarding and payment liability. The held corpus includes PSD2, RTS-SCA, PSD3/PSR and DORA. For exact wording use get_provision; for defined-term wording use get_defined_term. This searches held legislation, not national law or regulator guidance. Full-text search across articles, annexes and recitals, ranked in that order of authority. Every hit carries the exact locator get_provision accepts, its cite anchor, the matched passage and why it matched. A citation-shaped query resolves through the citation grammar first; instrument acronyms become ranking hints; initialisms of the corpus's defined terms are expanded. Absence of a result is not evidence that no relevant law exists. The matched passage is a snippet of at most 320 characters, not the provision: open the hit with get_provision before citing it, and echo the cite it serves. topic narrows these hits rather than widening them: a topic-tagged provision whose words the query misses is never reached, so a page of hits is not a sweep. For coverage questions ('everything on X', 'which instruments deal with Y') pick the instruments with list_instruments by category, enumerate each with list_provisions filtered by topic, then open them with get_provision.

Use this for a starting reading order in EU payments legislation when a relevant curated pathway exists. For other subjects use search_legislation. Curated reading pathways into the corpus for a stated audience: ordered waypoints with cite anchors every other tool can open, related defined terms and known pitfalls. The prose is editorial and labelled as such — it maps the reading order, never legal weight. Omit the pathway argument for the catalogue; an unknown id is refused with the catalogue, nothing substituted. Catalogue entries and pathway waypoints paginate whole: follow pagination.next_cursor with the same pathway and limit until complete.

Use this to read or quote an EU legislative provision, such as PSD2 Article 97 or RTS-SCA Article 5. Returns the source text of an article, annex or recital as markdown, with its cite anchor, provenance and text-state disclosure. Large provisions paginate by structural block — never truncated silently. version_id is optional: the service serves one text per instrument, and a pinned version id is refused with the URL where it is published. include_correspondences adds the cross-instrument article equivalences — what a PSR article is amended from, or which PSR articles carry a PSD2 article's obligation — each openable by a second call.

Use this to browse an EU instrument's article, annex or recital index, or enumerate its topic-tagged provisions for a coverage question. Metadata only: each item carries the exact locator get_provision accepts. Articles and annexes by default; pass kind=recital for recitals.

Use this to resolve a written EU legal citation, such as Article 97(1) PSD2, into an instrument and provision locator. For a topic rather than a citation, use search_legislation. Ranked candidates with ambiguity flagged and confidence stated: exact (instrument certain, provision found), strong (instrument certain, provision not verified or not named) or ambiguous (more than one reading). A citation of an instrument this corpus does not hold is named, with its CELEX and ELI, rather than guessed at.

Use this to find EU payments legislation on topics such as SCA, open banking and safeguarding in the held PSD2, RTS-SCA, PSD3/PSR and related instruments. OpenAI-compatible search: the top hits as {id, title, url}, where id is the cite anchor fetch accepts. For filters, snippets, scores and paging use search_legislation, which returns more.

Use this to read the original legislative footnotes and source-note bodies for a held instrument, including preamble and annex notes. Omit note_key for the paginated inventory; supply an exact returned key to retrieve one. Keys retain source scope because printed markers may repeat. This tool does not infer ownership by a provision. Historical versions return an explicit version_not_served link.

Use this to browse which articles changed between the held proposal and Council compromise versions of PSR or PSD3. For one article's wording changes use compare_versions. Across the instrument's two published texts, lists every aligned article with its classification, filterable by status, materiality and article range. The editorial materiality markers travel on every response whatever the filters, because they exist precisely where the mechanical classification does not show what matters — a re-scoped defined term changes articles whose text did not change at all. Classifications are mechanical, and the response says on what basis.