Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Payments Law EU is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
15
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
EU payments legislation: PSD2, RTS-SCA, PSD3/PSR, DORA; provisions, definitions and text changes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http payments-law-eu-mcp https://mcp.paymentslaw.eu/mcp/v1
# 2 — ask your agent for something these tools do
# get_provision, get_instrument, list_instruments and 12 more
Payments Law EU costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PAAll 1 server
paymentslaw1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http payments-law-eu-mcp https://mcp.paymentslaw.eu/mcp/v1Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 (a sub- or superscript with no Unicode form as inline <sub>/<sup>), with its cite anchor, provenance and text-state disclosure. Large provisions paginate by structural block — never truncated silently. version_id is optional: the s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instrument_id | string | yes | Registry id of the instrument, e.g. "psd-2". |
| version_id | no | Omit, or pass "current", for the served text. A pinned version id returns version_not_served with the URL where that text is published. | |
| locator | object | yes | — |
| on_date | no | ISO date; returns the provision-level applicability view. | |
| cursor | no | Continue a paginated provision. Bound to the release. | |
| include_correspondences | boolean/null | no | Off by default. When true, an article carries correspondences[]: the cross-instrument article equivalences the corpus publishes — which PSD2 article a PSR article is amended from, and, from the othe |
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 relationship names the operative amending or repealing article where curated (openable wit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instrument_id | string | yes | — |
| on_date | no | ISO date; returns the full applicability record. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | no | Legal status at the release, e.g. "in_force". | |
| category | no | — | |
| in_force_on_date | no | ISO date; keeps instruments in force on that date. | |
| is_core | boolean/null | no | — |
| limit | no | — | |
| cursor | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instrument_id | string | yes | Registry instrument id. |
| version_id | no | Omit or use current for the served version; pinned versions return an explicit version_not_served link. | |
| note_key | no | Exact key returned by this tool. Omit to list notes. Printed markers may be reused and are not necessarily unique keys. | |
| limit | no | Notes per page, default 10; complete bodies are never truncated. | |
| cursor | no | Continue with the same arguments; bound to this corpus release. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instrument_id | string | yes | — |
| kind | no | — | |
| chapter | no | — | |
| topic | no | — | |
| limit | no | — | |
| cursor | no | — |
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-t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | EU legislative search terms, e.g. "strong customer authentication", "dynamic linking", "safeguarding" or "DORA ICT risk". Use words expected in the legal text, not an entire advice request. Quoted phr |
| instrument_id | no | Restrict to one instrument, e.g. "rts-sca". | |
| kind | no | Restrict to one source type. Articles, annexes and recitals are all searched by default, ranked in that order of authority. | |
| topic | no | Keep only provisions carrying this topic. | |
| in_force_on_date | no | ISO date; keeps hits from instruments in force on that date, on the same semantics list_instruments uses. | |
| limit | no | — | |
| cursor | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| citation | string | yes | A citation in any form a reader would write: "Article 97(1) PSD2", "Art. 5a of Regulation (EU) No 910/2014", a CELEX number, an ELI path, or a bare acronym. |
| limit | no | — | |
| cursor | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | no | Term text to match. Matching is over the TERM only, never the definition body. Omit for the full alphabetical listing of every term the corpus defines. | |
| only_divergent | boolean/null | no | Keep only terms whose definers disagree — on the resolved text, the verbatim text, or both. |
| instrument | no | Keep only terms defined in this instrument, e.g. "psd-2". | |
| limit | no | — | |
| cursor | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| term | string | yes | The defined term, as written in the legislation ("payment account"). Matched exactly after normalisation; a term the corpus does not define is refused with suggestions, never answered with a neighbour |
| instrument | no | Narrow the definitions listed to one definer. The clusters, views and comparisons stay corpus-wide: what the term means elsewhere does not change because you asked about one instrument. | |
| view | no | Which text clusters and comparisons run on. "resolved" (default) follows each definition's pointers to its root; "verbatim" uses the text as each instrument prints it. | |
| on_date | no | ISO date. Adds operative_on_date and temporal_state_on_date per definer, and makes the concurrent view that date's rather than the release's. | |
| comparison | no | Which comparisons to compute. "adjacent" (default) compares consecutive distinct clusters in chronological order; {baseline: cluster_id} compares one cluster against every other; {pair: [cite, cite]} |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instrument_id | string | yes | Registry id of the instrument, e.g. "psr". |
| from_version_id | string | yes | Version id one side of the pair. |
| to_version_id | string | yes | Version id the other side. |
| from_locator | no | The article on the from side. Alignment is identity on the article number, so naming either side names both. | |
| to_locator | no | The article on the to side. | |
| limit | no | — | |
| cursor | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instrument_id | string | yes | — |
| from_version_id | no | Optional; where given, must name the published pair. | |
| to_version_id | no | — | |
| status | no | One of the classification statuses, e.g. "amended_substantial". | |
| material_only | boolean/null | no | Keep only articles that carry an editor's note. |
| articles | no | Article-number range, in legal order. | |
| limit | no | — | |
| cursor | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instrument_id | string | yes | Registry id of the instrument, e.g. "psr". |
| article | no | An article number. With it, the card is that article's comparison; without it and without articles, the instrument's change inventory. | |
| articles | no | Several article numbers: one card holding those articles as a filtered inventory, each opening its comparison in place. Not with article. | |
| from_version_id | no | Optional; both ids or neither. Where the instrument has one published pair, that pair is shown. A version id, or an alias the instrument defines: proposal, compromise, council, published. | |
| to_version_id | no | With from_version_id, the later text of the pair: both ids or neither. The same ids and aliases. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | EU payments legislative terms or citation, e.g. "strong customer authentication", "safeguarding" or "Article 97 PSD2". |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | An id from search, or a cite anchor such as "psd-2 Art 97" or "psd-2 Recital 12", or an instrument id such as "psd-2". An optional version qualifier, e.g. "psr (com-2023-367) Art 105", retains its edi |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pathway | no | Pathway id from the catalogue. Omit for the catalogue. | |
| limit | no | Maximum catalogue entries or pathway waypoints per page; whole-item byte bounds may return fewer. | |
| cursor | no | pagination.next_cursor from this tool; repeat the same pathway and limit. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Payments Law EU or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.9.1.
1.9.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Payments Law EU can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.