emendrix MCP server
eu.emendrix/emendrixemendrix.eustreamable-httpv0.1.0Scanned
Verified changes to watched EU acts, read-only, with each fact's source.
8 tools: 1 change things and 7 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the emendrix MCP server can do
The emendrix MCP server is published by emendrix.eu, a domain the MCP Registry verified. It has 8 tools. It can create or change data (1 tool: provision_history), but cannot delete data. 7 tools only read.
1 tool reads private data (find_substance).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 1Claude Code: ask
provision_historyEvery recorded change to one top-level provision, newest first, with the window the record covers for the act.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Every recorded change to one top-level provision, newest first, with the window the record covers for the act. An empty list means no recorded change to that provision in the window, and the result says so in words. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.
Annotations the server declares
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
Only reads 7Show 7 read-only tools
changes_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_o…No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List 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). `omitted` counts rows past `limit`. An empty list means no recorded change in the window has that date. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.
Annotations the server declares
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
find_provisionsFind touched provisions of one act whose canonical location string or stored heading contains `query`, each with its newest row.No findings
Why it is in this group
- The name "find_provisions" says "find": a word for reading.
Description, as the server wrote it Find touched provisions of one act whose canonical location string or stored heading contains `query`, each with its newest row. It never reads law text; an empty list means no touched provision of the act has that name in the window. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.
Annotations the server declares
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
find_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 …Reads private dataNo findings
Why it is in this group
- The name "find_substance" says "find": a word for reading.
What it can reach
- private-dataThe description's first sentence says "find" and "file": it reads files.
Description, as the server wrote it Find 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. It reports where a number appears and decides nothing about legal status; many entries name a group and print no number. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.
Annotations the server declares
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_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 `off…No findings
Why it is in this group
- The name "get_change" says "get": a word for reading.
Description, as the server wrote it One 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. `occurrence` counts repeats of one location in one event from 1. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.
Annotations the server declares
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_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 instruc…No findings
Why it is in this group
- The name "get_event" says "get": a word for reading.
Description, as the server wrote it One 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. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.
Annotations the server declares
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
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.No findings
Why it is in this group
- The name "list_acts" says "list": a word for reading.
Description, as the server wrote it List 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. `query` matches names case-insensitively; `domain` matches the catalogue's sector. An empty list means no held act matches. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.
Annotations the server declares
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
list_disputedDisputed rows grouped by their stored `dispute_reason`, each group with the sentence the site prints for that code.No findings
Why it is in this group
- The name "list_disputed" says "list": a word for reading.
Description, as the server wrote it Disputed rows grouped by their stored `dispute_reason`, each group with the sentence the site prints for that code. `omitted` counts rows past `limit`. An empty list means no recorded change in the window is disputed for that filter. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.
Annotations the server declares
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:53 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://emendrix.eu/mcp: tools/list returned 8 tools to an anonymous client, including provision_history (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http emendrix https://emendrix.eu/mcpclaude mcp add --transport http emendrix https://emendrix.eu/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__emendrix__list_acts",
"mcp__emendrix__find_provisions",
"mcp__emendrix__changes_since",
"mcp__emendrix__get_change",
"mcp__emendrix__get_event",
"mcp__emendrix__list_disputed",
"mcp__emendrix__find_substance"
],
"ask": [
"mcp__emendrix__provision_history"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as emendrix. Review it before you use it.
Capability tags behind 1 rule
- mcp__emendrix__find_substance private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/eu.emendrix/emendrix/verify?hash=94fed2dc065caae3ded0fb366efd841be267af03c72be9f516f52f766b0e3190" | jq -e '.changed == false'Pinned hash 94fed2dc065c, from Nov 15, 2026, 08:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/eu.emendrix/emendrix/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/eu.emendrix/emendrix)Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.
emendrix MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the emendrix MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the emendrix MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the emendrix MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the emendrix MCP server have?
- 8 tools: 1 write, 7 read. provision_history, list_acts, find_provisions, changes_since, get_change, get_event, list_disputed and find_substance.
Does the emendrix MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the emendrix MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the emendrix MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.