# emendrix (remote · emendrix.eu)

Verified changes to watched EU acts, read-only, with each fact's source.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `emendrix.eu`: 81/100 (this document), [markdown](https://verifymcp.io/servers/eu-emendrix-emendrix/emendrix.md), [page](https://verifymcp.io/servers/eu-emendrix-emendrix/emendrix)

## Channel facts

- Endpoint: `https://emendrix.eu/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2601 tokens (~260/item across 10 items; 8 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the emendrix MCP server?

emendrix is a hosted endpoint at https://emendrix.eu/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http eu-emendrix-emendrix 'https://emendrix.eu/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "eu-emendrix-emendrix": {
      "url": "https://emendrix.eu/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "eu-emendrix-emendrix": {
      "type": "http",
      "url": "https://emendrix.eu/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.eu-emendrix-emendrix]
url = "https://emendrix.eu/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "eu-emendrix-emendrix": {
      "type": "remote",
      "url": "https://emendrix.eu/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add eu-emendrix-emendrix --url 'https://emendrix.eu/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  eu-emendrix-emendrix:
    url: "https://emendrix.eu/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "eu-emendrix-emendrix": {
      "Transport": "http",
      "Url": "https://emendrix.eu/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add eu-emendrix-emendrix -t streamable-http -u 'https://emendrix.eu/mcp'
```

### Other

```json
{
  "mcpServers": {
    "eu-emendrix-emendrix": {
      "type": "http",
      "url": "https://emendrix.eu/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (8)

### `list_acts` (~264 tokens)

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.

Input parameters:

- `domain`: A catalogue sector.
- `query`: Part of a key, title or alias.

Output parameters:

- `acts` (array): Matching acts, sorted by corpus and key.
- `disclaimer` (string): Not legal advice.
- `unavailable` (array): What could not be read, in words.

### `find_provisions` (~269 tokens)

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.

Input parameters:

- `act` (string, required): The act's key, or `corpus/key`, as `list_acts` gives it.
- `query` (string, required): Part of a location (`AR 5`) or a heading.

Output parameters:

- `disclaimer` (string): Not legal advice.
- `provisions` (array): Matches, by canonical location.
- `unavailable` (array): What could not be read, in words.

### `changes_since` (~340 tokens)

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.

Input parameters:

- `acts`: Act keys; all when omitted.
- `basis` (string): Which stored date to compare.
- `include_disputed` (boolean): Keep disputed rows.
- `limit` (integer): At most this many rows, 1 to 500.
- `since` (string, required): The earliest date, YYYY-MM-DD.

Output parameters:

- `basis` (string): Which stored date was compared with `since`.
- `disclaimer` (string): Not legal advice.
- `omitted` (integer): Matching rows left out because of `limit`.
- `rows` (array): Matching rows, newest first.
- `since` (string): The earliest date a row's basis date may carry.
- `unavailable` (array): What could not be read, in words.

### `provision_history` (~270 tokens)

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.

Input parameters:

- `act` (string, required): The act's key, or `corpus/key`, as `list_acts` gives it.
- `location` (string, required): A canonical location string such as `AR 50`, as the record stores it.

Output parameters:

- `disclaimer` (string): Not legal advice.
- `location` (string): The canonical top-level location asked for.
- `rows` (array): The provision's rows, newest first.
- `sentence` (string): What the rows, or their absence, mean, in words.
- `unavailable` (array): What could not be read, in words.
- `window`: What the record covers; null if unreadable.

### `get_change` (~410 tokens)

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.

Input parameters:

- `act` (string, required): The act's key, or `corpus/key`, as `list_acts` gives it.
- `location` (string, required): A canonical location string such as `AR 50`, as the record stores it.
- `max_chars` (integer): Characters per side, 1 to 50000.
- `occurrence` (integer): Which repeat, from 1.
- `offset` (integer): Where each side's page starts.
- `version` (string, required): The version an event produced, or its entry key, as stored.

Output parameters:

- `change`: The change; null when it could not be read.
- `disclaimer` (string): Not legal advice.
- `unavailable` (array): What could not be read, in words.

### `get_event` (~269 tokens)

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.

Input parameters:

- `act` (string, required): The act's key, or `corpus/key`, as `list_acts` gives it.
- `version` (string, required): The version an event produced, or its entry key, as stored.

Output parameters:

- `disclaimer` (string): Not legal advice.
- `event`: The event; null when it could not be read.
- `unavailable` (array): What could not be read, in words.

### `list_disputed` (~272 tokens)

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.

Input parameters:

- `act`: One act's key; all when omitted.
- `limit` (integer): At most this many rows, 1 to 2000.
- `reason`: One `dispute_reason` code.

Output parameters:

- `disclaimer` (string): Not legal advice.
- `groups` (array): One group per reason code, by code.
- `omitted` (integer): Disputed rows left out because of `limit`.
- `unavailable` (array): What could not be read, in words.

### `find_substance` (~279 tokens)

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.

Input parameters:

- `identifier` (string, required): A CAS, EC or CLP Index number, hyphens optional.

Output parameters:

- `disclaimer` (string): Not legal advice.
- `query` (string): The value as typed.
- `readings` (array): One answer per reading whose check digit passes; empty when none does.
- `sentence` (string): The answer, or the reason the value is no number.
- `unavailable` (array): What could not be read, in words.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/eu-emendrix-emendrix/emendrix#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78
- 2026-10-28: 77
- 2026-10-27: 77
- 2026-10-26: 76
- 2026-10-25: 76
- 2026-10-24: 76
- 2026-10-23: 75
- 2026-10-22: 75
- 2026-10-21: 74
- 2026-10-20: 74
- 2026-10-19: 73

## Common questions

### What is the emendrix MCP server?

emendrix is an MCP server listed in the public MCP registry as eu.emendrix/emendrix. Verified changes to watched EU acts, read-only, with each fact's source. This page covers its hosted endpoint (https://emendrix.eu/mcp).

### Is the emendrix MCP server safe to use?

emendrix scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the emendrix MCP server expose?

emendrix exposes 8 tools: list_acts, find_provisions, changes_since, provision_history, get_change, and 3 more. Their descriptions and schemas cost roughly 2,373 tokens of context every time the server is loaded.

### Does the emendrix MCP server require authentication?

No. We connected to emendrix without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the emendrix MCP server still maintained?

emendrix is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://emendrix.eu/mcp
- Website: https://emendrix.eu/
- Changelog RSS feed: https://verifymcp.io/servers/eu-emendrix-emendrix/emendrix.xml
- Changelog JSON feed: https://verifymcp.io/servers/eu-emendrix-emendrix/emendrix.json
- HTML version of this page: https://verifymcp.io/servers/eu-emendrix-emendrix/emendrix