mcpbeat Sign in

Payments Law — EU payments legislation MCP Server

by paymentslaw Your server? Claim it
answering

Payments Law — EU payments legislation is answering right now. Last checked 3 min ago. It exposes 15 tools.

EU payments legislation: PSD2, RTS-SCA, PSD3/PSR, DORA; provisions, definitions and text changes.

Uptime history 71 days of history · worst day 95%
71 days agonow
100.0%
Uptime 24h
92 of 92 checks
15
Tools
read from the server
271 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 115

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 31 August 2026. No other catalogue keeps this.

5 Nov a tool changed version3 times that day
5 Nov a tool changed the parameters it asks for list_provisions
3 Nov 3 tools changed the parameters they ask for compare_versions, list_version_changes, show_changes
3 Nov 2 tool descriptions were rewritten compare_versions, list_version_changes
3 Nov a tool changed version
25 Oct a tool changed version
24 Oct 4 tool descriptions were rewritten compare_versions, get_instrument, get_provision and 1 more
24 Oct a tool changed the parameters it asks for get_provision
24 Oct a tool changed version
21 Oct a tool changed version
and 99 more, back to 31 August 2026

Nothing serious here today

Today is the operative word: we check Payments Law — EU payments legislation every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add legislation --transport http https://mcp.paymentslaw.eu/mcp/v1
Settings → Connectors → Add custom connector, then paste this address
https://mcp.paymentslaw.eu/mcp/v1
~/.codex/config.toml
[mcp_servers.legislation]
url = "https://mcp.paymentslaw.eu/mcp/v1"
.cursor/mcp.json
{
  "mcpServers": {
    "legislation": {
      "url": "https://mcp.paymentslaw.eu/mcp/v1"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "legislation": {
      "type": "http",
      "url": "https://mcp.paymentslaw.eu/mcp/v1"
    }
  }
}

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

defined
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, 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.
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 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.
compare
compare_versions
Compare an article between consecutive versions of PSR or PSD3: the 2023 Commission proposal and the April 2026 Council compromise, or the April compromise and the October 2026 Council position at first reading. Returns the word-level comparison, identifying each version, its article number and source. Either comparison direction is supported. Where numbering changed, use the article number belonging to each version; a mismatched pairing is refused with the corresponding mapping. Comparisons with Official Journal texts are not currently available. Unsupported requests return the available pairs and links to pinned texts where available. The `changes` field summarises the types of textual change.
fetch
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 resolve_citation. get_provision returns more: paging, applicability and typed warnings.
instrument
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 list_provisions. Pass on_date for the applicability record on that date.
instruments
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.
legislation
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 grammar first. Every hit carries the locator get_provision accepts, its cite anchor and the matched passage. topic narrows hits rather than widening them, so for a coverage question ('everything on X') pick the instruments with list_instruments, enumerate each with list_provisions filtered by topic, then open them with get_provision.
orientation
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 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.
provision
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 the cross-instrument article equivalences.
provisions
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.
resolve
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 citation of an instrument this corpus does not hold is named, with its CELEX and ELI, rather than guessed at.
search
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.
show
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 inventory, each opening its comparison in place. Without either, the card is the instrument's inventory of changed articles grouped by kind of change, with the editors' notes, as list_version_changes serves it. The result is a one-line summary with the site link; the card loads its own data. compare_versions and list_version_changes return the same comparison as data, for an answer that quotes or reasons over the wording.
source
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.
version
list_version_changes
Browse article-level changes between consecutive versions of PSR or PSD3. Without version IDs, returns the latest available comparison: the April 2026 Council compromise and the October 2026 Council position at first reading. Lists aligned articles with mechanical change classifications, both article numbers where numbering changed, and any editor's notes. Filter by status, editor's note or article range; editor's notes remain included regardless of filters. For an article's word-level comparison, use `compare_versions`. Comparisons with Official Journal texts are not currently available.

Endpoints

URLTransportStateLatencyChecked
https://mcp.paymentslaw.eu/mcp/v1 streamable-http answering 273 ms 3 min ago

Alternatives to Payments Law — EU payments legislation

same job, measured the same way
Aml
by oceanalt

Pre-payment checks for AI agents: sanctions and AML screening of payees, payment pages and requests.

126 installs/wk 13 tools answering
NexPay
by com-nexpay

Connect your AI assistant to NexPay to view payments, contacts, commissions, and exchange rates.

answering
Roraima for hosts
by roraima

Hosts: read and record bookings, change prices, draft listings, rename devices. No payments.

answering
ExoticCar.Loans: exotic and classic car loan calculator
by exoticcar

Exotic and classic car loan payments with balloons, equity by year, depreciation and lender terms.

4 tools answering
MCP Stripe Acp
by codespar

Stripe ACP — AI agent checkout, payment delegation, products, invoices

65 installs/wk local only
X402 Data Gateway
by epistemedeus

Agent tools for discovery, payment safety, data extraction, and DeFi.

30 tools answering
HowToRomania
by howtoromania

Romanian company data, e-Factura and legislation: CUI lookup, courts, risk, invoices, laws

20 tools answering
Stripe MCP Server
by friendlygeorge

MCP server for Stripe API — customers, charges, payments, subscriptions, products, and invoices

43 installs/wk local only

Payments Law — EU payments legislation — questions

Answers built from our own checks of this server.

What can Payments Law — EU payments legislation do?
It exposes 15 tools, read directly from the server on our last check. Among them: compare_versions, fetch, get_defined_term, get_instrument, get_orientation, get_provision and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Payments Law — EU payments legislation working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 271 ms. The bar chart above shows every period we have measured.
How do I connect Payments Law — EU payments legislation?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Payments Law — EU payments legislation need an API key?
No. Payments Law — EU payments legislation completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Payments Law — EU payments legislation?
It answers our handshake in 271 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.