API Tools
emendrix.eu
Provides tools to query legislative acts, provisions, and recorded change histories from a legal data catalogue.
ENDPOINT 1
https://emendrix.eu/mcp
MCP server metadata
- Name
- emendrix
- Version
- 0.1.0
A reader of verified change records: what changed in which provision of a watched EU act, between which consolidated versions, whether three independent signals agree about it, and the file every fact was read from. Every fact was computed by a deterministic pipeline and is returned as stored. It gives no legal advice, does not read or interpret law, and decides nothing: it never works out whether, where or how something changed, and it cannot search law text or resolve a free reference such as 'Art. 50(2)'. Name an act by its key, a provision by its canonical location string (`AR 50`, `AN I`) as `list_acts` and `find_provisions` give them, and hand a CAS or EC number to `find_substance`. Say the provenance you relied on. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.
Known tools 8
list_actsList the acts the record holds, with each act's label, aliases and sector from the site catalogue, its newest version, `updated_on` and the counts its index carries.
Inferred read-onlyfind_provisionsFind touched provisions of one act whose canonical location string or stored heading contains `query`, each with its newest row.
Inferred read-onlychanges_sinceList recorded changes whose `basis` date is on or after `since`, newest first, with each row's event and provision pages: `updated_on` (the event or its latest repair), `detected_on` (when the run saw the event) or `in_force` (the change's in-force date; rows without one are left out).
Inferred read-onlyprovision_historyEvery recorded change to one top-level provision, newest first, with the window the record covers for the act.
Inferred read-onlyget_changeOne change in full: the verbatim text before and after, each side cut at `max_chars` (1 to 50000) with a marker '[… N characters omitted, continue with offset=M]' and paged by `offset`; the cited sentences with their URLs; `changed_within`; the three signals with their detail; `dispute_reason` and its sentence; `in_force`; `applies_from` with its reason; amending acts; the gate outcome or why it is unexplained.
Inferred read-onlyget_eventOne event of one act: its counts, repairs and stored corroboration (each signal's units, the pairwise agreements and disagreements), the units only the metadata or only the instruction parse names, and every row of the event.
Inferred read-onlylist_disputedDisputed rows grouped by their stored `dispute_reason`, each group with the sentence the site prints for that code.
Inferred read-onlyfind_substanceFind the entries that print a CAS or EC number, given with or without hyphens, in the newest version of each act the record holds, and every recorded change to them, each with its date, the amending act the change names and the file it was read from.
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.emendrix]
url = "https://emendrix.eu/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"emendrix": {
"type": "http",
"url": "https://emendrix.eu/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: emendrix
Remote MCP URL: https://emendrix.eu/mcp
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": {
"emendrix": {
"url": "https://emendrix.eu/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"emendrix": {
"type": "http",
"url": "https://emendrix.eu/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "emendrix",
"transport": "streamable-http",
"url": "https://emendrix.eu/mcp"
}
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.