Payments Law — EU payments legislation
EU payments legislation: PSD2, RTS-SCA, PSD3/PSR, DORA; provisions, definitions and text changes.
| Endpoint | https://mcp.paymentslaw.eu/mcp/v1 (streamable-http) |
|---|---|
| Registry version | 1.9.1 |
| Now | 15 tools · grade A (95) · pin ts_02f53b641cdfed4861b03eaf8c9069eb · protocol 2025-06-18 |
| First / last listed | 2026-10-25 04:27 UTC / 2026-10-25 04:27 UTC |
| Grade over time | 2026-10-25: A (95), 15 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: get_provision get_instrument list_instruments get_source_notes list_provisions search_legislation resolve_citation search_defined_terms get_defined_term compare_versions list_version_changes show_changes search fetch get_orientation
get_provision | 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; a long provision paginates by structural block. version_id is optional, and a pinned version id is refused with the URL where that text is published. include_correspondences adds th params: instrument_id*, version_id, locator*, on_date, cursor, include_correspondences |
get_instrument | 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, a Council compromise text or the act published in the Official Journal. Metadata, dates, lifecycle and application events, and curated relationships, each naming the operative amending or repealing article where curated. No article index: use li params: instrument_id*, on_date |
list_instruments | 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. params: status, category, in_force_on_date, is_core, limit, cursor |
get_source_notes | 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. params: instrument_id*, version_id, note_key, limit, cursor |
list_provisions | 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. params: instrument_id*, kind, chapter, topic, limit, cursor |
search_legislation | Use this to find EU legislative provisions on payment-services questions: strong customer authentication (SCA), dynamic linking, open banking, safeguarding and payment liability. For exact wording use get_provision; for defined-term wording use get_defined_term. Full-text search across articles, annexes and recitals, ranked in that order; a citation-shaped query resolves through the citation gramm params: query*, instrument_id, kind, topic, in_force_on_date, limit, cursor |
resolve_citation | 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 citatio params: citation*, limit, cursor |
search_defined_terms | 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 params: query, only_divergent, instrument, limit, cursor |
get_defined_term | 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, ne params: term*, instrument, view, on_date, comparison |
compare_versions | Use this to compare an article between the Commission proposal and the Council compromise text 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 is refused, including any with a text published in the Official params: instrument_id*, from_version_id*, to_version_id*, from_locator, to_locator, limit, cursor |
list_version_changes | Use this to browse which articles changed between the Commission proposal and the Council compromise text of PSR or PSD3; no comparison with a text published in the Official Journal is held. For one article's wording changes use compare_versions. Across those two texts, lists every aligned article with its classification, filterable by status, editor's note and article range. Editor's notes travel params: instrument_id*, from_version_id, to_version_id, status, material_only, articles, limit, cursor |
show_changes | Shows the reader what changed: presents a comparison or a change inventory to the reader as an interactive card, this service's intended way of showing what changed between the two texts of a served pair. With article, the card is that article's word-level comparison, side by side with every change marked, as compare_versions serves it. With articles, one card holds those articles as a filtered in params: instrument_id*, article, articles, from_version_id, to_version_id |
search | 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. Simple search returning 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. params: query* |
fetch | Use this to open and cite an EU legislative provision found by search. Simple retrieval of one provision's text by its cite anchor id (e.g. "psd-2 Art 97"), with citation metadata. A provision longer than the response ceiling arrives in part, with metadata.complete false and a metadata.next_cursor that get_provision continues. Accepts only ids this service minted — free-text citations belong to re params: id* |
get_orientation | 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 lega params: pathway, limit, cursor |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.