Databases
paymentslaw.eu
Provides access to a corpus of legislation, allowing users to search, retrieve, and explore instruments and provisions.
ENDPOINT 1
https://mcp.paymentslaw.eu/mcp/v1
MCP server metadata
- Name
- paymentslaw
- Version
- 1.3.0
Query service for EU payments legislation: 50 curated instruments at provision granularity, from paymentslaw.eu. Not legal advice. EUR-Lex is authoritative. The corpus is curated and non-exhaustive: absence of a result is not evidence that no relevant law exists. Council compromise texts are agreed but not yet law. Texts are as adopted or, where stated, consolidated — where an as-adopted text is amended by another instrument in this corpus, the response says so and the amendments are not incorporated. Every provision-bearing result carries a `cite` anchor naming exactly what was served. Echo it rather than composing citations of your own. A search snippet is served text but is not the provision: open a hit with `get_provision` before citing it. National implementing law is out of scope, so a directive's applicability is refused in place rather than guessed. `search` and `fetch` exist for clients that expect those names; `fetch` ids are cite anchors. Every other tool returns more — warnings, provenance, paging — and should be preferred where the client can call it. get_orientation returns curated reading pathways into the corpus for a stated audience; its prose is editorial and labelled as such.
Known tools 13
compare_versionsWhat changed in this article between two texts of the same instrument?
Inferred read-onlylist_version_changesWhat changed across the whole instrument between its two published texts?
Inferred read-onlysearchOpenAI-compatible search over the corpus: the top hits as {id, title, url}, where id is the cite anchor fetch accepts.
Inferred read-onlyfetchOpenAI-compatible retrieval: the full text of one provision by its cite anchor id (e.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.paymentslaw]
url = "https://mcp.paymentslaw.eu/mcp/v1"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"paymentslaw": {
"type": "http",
"url": "https://mcp.paymentslaw.eu/mcp/v1"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: paymentslaw
Remote MCP URL: https://mcp.paymentslaw.eu/mcp/v1
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"paymentslaw": {
"url": "https://mcp.paymentslaw.eu/mcp/v1"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"paymentslaw": {
"type": "http",
"url": "https://mcp.paymentslaw.eu/mcp/v1"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "paymentslaw",
"transport": "streamable-http",
"url": "https://mcp.paymentslaw.eu/mcp/v1"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.